maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Bone (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5271) Cannot resolve active profile name at build time
Date Thu, 26 Apr 2012 13:47:02 GMT

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

Richard Bone commented on MNG-5271:
-----------------------------------

Could somebody triage this?
                
> Cannot resolve active profile name at build time
> ------------------------------------------------
>
>                 Key: MNG-5271
>                 URL: https://jira.codehaus.org/browse/MNG-5271
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Profiles
>    Affects Versions: 3.0
>         Environment: Mac OS 10.6
>            Reporter: Richard Bone
>
> I have a maven profile defined in my pom.  It's not active by default, so I run -P <profilename>.
> When the profile is running, I want to construct a path that includes the name of the
profile.  I've looked online  and it appears that
> http://stackoverflow.com/questions/2012198/maven-can-i-reference-profile-id-in-profile-definition
> would have the answer.  Alas, it doesn't work for me at build time.  If I do a mvn help:evaluate
-P <profilename> and use ${projects.activeProfiles[0].id}, I get the value I would expect.
 When I run in the build, though, it doesn't resolve and just uses the literal value in the
path.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message