[jira] Closed: (MECLIPSE-265) profiles are not taken into account

["Matthijs Wensveen (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MECLIPSE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthijs Wensveen closed MECLIPSE-265.
--------------------------------------

    Resolution: Not A Bug

See above

> 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