New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shipkit pom customizations #831
Conversation
Scm section currently:
With shipkit:
Do we need these additional properties? |
BTW why is http://github.com/mockito/mockito ? |
There is a really subtle difference about ( is "GitHub issues" instead of "GitHub") so I'm removing this section from "publish-maven.gradle". |
Hey guys. If needed I think we can keep the existing withXml() section in powermock's build.gradle file. withXml() can be used to register multiple actions, each action will manipulate the xml. If shipikit .gradle does not have developers, it does not add this section to the xml at all. So the withXml() from powermockito can simply fill it out. |
Yes, of course we can do it, I only wanted to show @thekingnothing what the difference would be if he used it the shipkit way. |
|
I'm oaky with
|
@wwilk could you check last changes. After them build have started fail with compile error:
|
addb75d
to
8986fbb
Compare
Fixes #826 * Initial configuration of Shipkit * Introduced shipkit format of developers section in pom #826 * Issues section removed from publish-maven.gradle #826 * Removed redundant packaging and description #826 * Shipkit version bumped and prefix 'powermock-' used instead of 'v' #826 * Disabled redundant tasks for unpublishable modules #826 * MIT licence replaced with Apache one #826 * Publishing separately fullJars/zips and jars #826 * Compilation fixed #826 * Finished pom configuration #826
I will make further pom customizations, to keep the same format as it was before introducing shipkit.
I'm travelling right now so these will be probably small changes, you can wait with merging this PR before all is done.
Starting with . Before you had sth like that:
Shipkit currently supports format:
@thekingnothing What do you think about it? Is it acceptable or you would like to keep this email for developers? We may think of supporting it in shipkit or customize it here. As you can see I removed code that modified from powermock code.
Additionally shipkit generates section, that looks like that:
I hope you are ok with that.