[ http://issues.apache.org/jira/browse/TUSCANY-949?page=all ]
Simon Nash updated TUSCANY-949:
-------------------------------
Attachment: jira949.diff
The attached pom changes create two maven profiles for the build:
full (the default)
release (only builds projects intended for binary release)
To specify a release build, use the "-P release" option on the mvn command.
Example: mvn deploy -P release
To specify a full build, no special options are needed, as at present.
Example: mvn deploy
mvn install
mvn
> Incorrect set of extensions published to the maven repo
> -------------------------------------------------------
>
> Key: TUSCANY-949
> URL: http://issues.apache.org/jira/browse/TUSCANY-949
> Project: Tuscany
> Issue Type: Bug
> Components: Build System
> Affects Versions: Java-M2
> Environment: all
> Reporter: Simon Nash
> Attachments: jira949.diff
>
>
> mvn deploy publishes a number of extensions to the maven repo that should
> not be published there because they are not fully tested and endorsed parts
> of the Tuscany M2 release. Specifically, the following jars should not be
> published:
> groovy-1.0-incubator-M2.jar
> databinding-castor-1.0-incubator-M2.jar
> databinding-jaxb-1.0-incubator-M2.jar
> databinding-xmlbeans-1.0-incubator-M2.jar
> databinding-test-1.0-incubator-M2.jar
> celtix-1.0-incubator-M2.jar
> binding-jsonrpc-1.0-incubator-M2.jar
> An option should be provided on the build to selectively publish only those
> extensions that have been endorsed as part of the Tuscany M2 release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
