[ https://issues.apache.org/jira/browse/MPOM-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163587#comment-16163587 ]
Christopher Tubbs commented on MPOM-134: ---------------------------------------- Instructions to add {{-Pincubator}} would work. A more complicated, but more automatic, approach would be to create a small Maven plugin to be included in the parent POM which adds the resource bundle when it detects a version number with the {{-incubator}} pattern. > Add profile to use a different resource bundle for incubator projects > --------------------------------------------------------------------- > > Key: MPOM-134 > URL: https://issues.apache.org/jira/browse/MPOM-134 > Project: Maven POMs > Issue Type: Improvement > Affects Versions: ASF-18 > Reporter: Christopher Tubbs > Fix For: ASF-19 > > > The {{org.apache:apache-jar-resource-bundle:1.4}} resourceBundle currently > specified in the parent POM does not handle the DISCLAIMER file for incubator > projects. > It would be nice if there were an incubation profile, which could be > activated for incubating projects, to use an incubating resource bundle which > did handle this DISCLAIMER file. > This could be done in several ways: > # An optional second execution of the {{maven-remote-resources-plugin}} could > run when the profile is activated, which handles a second resource bundle for > the DISCLAIMER file. > # The current resourceBundle could be turned into a property, which is > overridden when the profile is activated, using a resourceBundle which > handles everything the current one does, plus the DISCLAIMER file. > # The current {{maven-remote-resources-plugin}} execution could have the > {{<resourceBundles>}} element changed to {{<resourceBundles > combine.children="append">}}, and the profile could specify an additional > {{<resourceBundle>}} to handle the DISCLAIMER file, for the same execution id > of {{maven-remote-resources-plugin}}. -- This message was sent by Atlassian JIRA (v6.4.14#64029)