[ http://issues.apache.org/jira/browse/TUSCANY-949?page=comments#action_12454069 ] Jeremy Boynes commented on TUSCANY-949: ---------------------------------------
I don't think we should use profiles in this way. We already use profiles (e.g. in SDO) to determine the type of content that gets built (e.g. in SDO we use them to generate aggregated vs. non-aggregated javadoc, in SCA we have a sourcecheck profile that enables checkstyle and pmd) but this is using them to determine which modules get built. I don't think this allows us to do something like run sourcecheck on the release modules for example. This is really just trying to get modularity without doing the modularity work. It would be better to do that by restructuring the build into an appropriately modular tree. > 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]
