[
https://jira.codehaus.org/browse/MNG-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-4366:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> profile activation based on presence of a dependency
> ----------------------------------------------------
>
> Key: MNG-4366
> URL: https://jira.codehaus.org/browse/MNG-4366
> Project: Maven
> Issue Type: Wish
> Components: Profiles
> Reporter: jieryn
>
> It would be handy to have profile activation based on a dependency being
> present. For example, I would like to be able to have a profile in my
> corporate super-pom which gets activated when any of the projects at my
> corporation (which use a parent of the super-pom) include log4j as a
> dependency. The profile would automatically add a dependency on our custom
> Log4j appenders.
> There are other uses as well, like if log4j is detected to be in the
> dependency list, then unpack a maven-remote-resources-plugin bundle with a
> log4j.xml.vm which gets velocity-processed for a default corporate-wide
> configuration. This would best be chained with negative-file exist profile
> activation for an existing log4j.xml.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
