You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Topping (JIRA)" <ji...@codehaus.org> on 2011/07/08 04:23:42 UTC

[jira] Commented: (MNG-944) activation of a profile on some Project definition (artifactId/groupId)

    [ https://jira.codehaus.org/browse/MNG-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272621#comment-272621 ] 

Brian Topping commented on MNG-944:
-----------------------------------

I could use this for a current project if it existed.  In my case, I would select off of project.packaging.  Would be very powerful, in my current use case I need to be able to activate a plugin defined in at top-level pom that will install an artifact, but only if the project creates an artifact that matches the packaging it can deal with.

> activation of a profile on some Project definition (artifactId/groupId)
> -----------------------------------------------------------------------
>
>                 Key: MNG-944
>                 URL: https://jira.codehaus.org/browse/MNG-944
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0-beta-1
>            Reporter: Raphaël Piéroni
>            Priority: Minor
>             Fix For: Issues to be reviewed for 3.x
>
>
> It would be helpfull to activate a profile
> using the value of some property of the 
> pom beeing used. Like the project.artifactId.
> In an multi project environement, the 'current' 
> project activate the profile.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira