[
http://jira.codehaus.org/browse/MNG-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-4323.
-----------------------------
Assignee: Brett Porter
Resolution: Won't Fix
profiles.xml as a separate file has been deprecated. You should work to
incorporate the profiles in your POM and select them based on configuration
options (-P can also be used).
> flexibility in profiles.xml
> ---------------------------
>
> Key: MNG-4323
> URL: http://jira.codehaus.org/browse/MNG-4323
> Project: Maven 2
> Issue Type: Improvement
> Components: Settings
> Affects Versions: 2.1.0
> Reporter: Lakshmanan Venkatachalam
> Assignee: Brett Porter
> Priority: Minor
>
> It looks like maven is hardcoded to support only the profiles under
> profiles.xml. Suppose if I have profiles_<env>.xml, its just ignores.
> I agree we can always activates different profiles based on the -D
> parameters. But in my situation I could not do it that way.
> In my environment, bamboo is running in a separate server for nightly build
> for all the different projects. This server is using maven 2.1.0 version.
> production, Accepatance and development for this project runs on maven
> 2.0.9. Maven 2.1.0 not supporting the maven 2.0.9 schema for profiles.xml. So
> my build breaks in the nightly build. So now i moved the content of
> profiles.xml into parent pom and passing -D parameter to activiate the
> profile respectively.
> I believe If we have flexibility in choosing the profiles.xml filename using
> parameters as we have for pom files using -f parameter.
> This is not the major issue and not very common in every environment. But
> haveint it, is good for scenarios like the one mentioned above.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
