[
https://issues.apache.org/jira/browse/MPOM-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106878#comment-16106878
]
Hervé Boutemy edited comment on MPOM-134 at 7/31/17 7:00 AM:
-------------------------------------------------------------
yes, option 3 is the way to go to add an additional {{resourceBundle}} value
from a profile
the question is: how to activate this profile?
do you expect to add instructions to activate the profile manually through
{{mvn -Pincubator}}?
Notice: I'm struggling with an equivalent issue after MPOM-96: writing the
profile was a first step, but now I see that the big issue is to make is
automagically activate (and the pom property I documented just does not work...)
was (Author: hboutemy):
yes, option 3 is the way to go to add an additional {{resourceBundle}} value
from a profile
the question is: how to activate this profile?
you expect to add instructions to activate the profile manually through {{mvn
-Pincubator}}?
(I'm struggling with an equivalent issue after MPOM-96: writing the profile was
a first step, but now I see that the big issue is to make is automagically
activate (and the pom property I documented just does not work...)
> 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)
