[
http://jira.codehaus.org/browse/MECLIPSE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159130#action_159130
]
Matthijs Wensveen commented on MECLIPSE-265:
--------------------------------------------
A better way to do this is to override the build settings directly, instead of
setting properties and later using them.
<profile>
<id>profile-default</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<build>
<finalName>name</finalName>
<directory>directory</directory>
</build>
</profile>
The maven-eclipse-plugin does use the overridden build.directory into account.
So I guess this issue should be closed (marked invalid or whatever).
> profiles are not taken into account
> -----------------------------------
>
> Key: MECLIPSE-265
> URL: http://jira.codehaus.org/browse/MECLIPSE-265
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Linux
> Reporter: Matthijs Wensveen
>
> Profiles described in pom.xml are not taken into account when eclipse:eclipse
> runs. I have a profile in pom.xml like this:
> <profile>
> <id>profile-default</id>
> <activation>
> <activeByDefault>true</activeByDefault>
> </activation>
> <properties>
> <finalName>myproject</finalName>
> <build.directory>target</build.directory>
> </properties>
> </profile>
> This sets the properties ${finalName} and ${build.directory}. Later in
> pom.xml:
> <build>
> <finalName>${finalName}</finalName>
> <directory>${build.directory}</directory>
> This enables me to create different artifacts for different profiles. But
> when I run eclipse:eclipse it puts the mvn-eclipse-cache.properties in a
> directory named "${build.directory}". So apparently it doesn't take my
> default profile into account.
--
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
