Niclas Hedhman a écrit :
I think just go ahead.
This is now merged into develop.
I see that you have added back Checkstyle. It takes quite a lot of execution time, and there are too much violations to be useful. Need some strategy to deal with.
I removed Checkstyle before merging. On Mon, Sep 10, 2012 at 7:02 PM, Paul Merlin <[email protected]> wrote:
Gang, In the branch feature/BetterArtifactsUpload I made an attempt at adding some features to the Build System. I need to upload SNAPSHOT artifacts of the develop branch to a maven repository so I added the following behavior to the uploadArchives task : By default, RELEASES are signed, SNAPSHOTS are not Signing can be turned on or off by setting the uploadSigned property By default, RELEASES must satisfy ReleaseSpecification, SNAPSHOT don't ReleaseSpecification usage can be turned on or off by setting the uploadReleaseSpec property By default, RELEASES are uploaded using SSH, SNAPSHOTS using WEBDAV Used Wagon can be overriden by setting the uploadWagon property By default, RELEASES are uploaded to OPS4J, SNAPSHOTS to Cloudbees (Used by the CI) Target repository can be overriden by setting the uploadRepository property No username/password is provided by default If needed set them using the uploadUsername and uploadPassword properties So. The default behavior remain untouched. Added SNAPSHOT handling which defaults to our CI setup. And every aspect is overridable using gradle properties. Needed changes can be reviewed at: https://github.com/Qi4j/qi4j-sdk/commit/58bfadf1d72d5f3b131421b279ae4874b973f8d4 For example here is how to deploy all artifacts as SNAPSHOTs to a given repository: ./gradlew uploadArchives -Dversion=2.0-SNAPSHOT -PuploadReleaseSpec=false -PuploadWagon=what:ever:wagon -PuploadRepository=http://what.ever.repository/url -PuploadUsername=foo -PuploadPassword=bar I'd like to merge this to develop but as it's my first real change on the build system I call for a groovy code review. Once reviewed I'll update the docs accordingly. /Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
