[jira] Closed: (MECLIPSE-265) profiles are not taken into account
[
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-default
>
> true
>
>
> myproject
> target
>
>
> This sets the properties ${finalName} and ${build.directory}. Later in
> pom.xml:
>
> ${finalName}
> ${build.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
[jira] Commented: (MECLIPSE-265) profiles are not taken into account
[
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-default
true
name
directory
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-default
>
> true
>
>
> myproject
> target
>
>
> This sets the properties ${finalName} and ${build.directory}. Later in
> pom.xml:
>
> ${finalName}
> ${build.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
[jira] Created: (MRESOURCES-55) filter file location does not expand ${project.build.directory}
filter file location does not expand ${project.build.directory}
---
Key: MRESOURCES-55
URL: http://jira.codehaus.org/browse/MRESOURCES-55
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Reporter: Matthijs Wensveen
When specifying a propeties file with
..
${project.build.directory}/build.properties
..
${project.build.directory} is not expanded to the defined build directory.
Usually this is 'target' but this may be overridden in the pom or settings.xml,
possibly using profiles.
--
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
[jira] Commented: (MNG-1832) built-in property containing current timestamp
[ http://jira.codehaus.org/browse/MNG-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124455 ] Matthijs Wensveen commented on MNG-1832: How is this issue fixed? It doesn't work for me. I suspect this issue is closed because there are alternatives, albeit inferior IMO. In that case the resolution should not be 'fixed' but 'wontfix', otherwise people will expect this to work when it doesn't. > built-in property containing current timestamp > -- > > Key: MNG-1832 > URL: http://jira.codehaus.org/browse/MNG-1832 > Project: Maven 2 > Issue Type: New Feature >Affects Versions: 2.0.1 >Reporter: Michal Stochmialek > Attachments: maven-archiver_pomDelete.patch, > maven-core_defaultExpressions.patch > > > Current timestamp (time or date) is often used while filtering resources or > creating manifest in ant builds. There is no equivalent in maven. -- 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
[jira] Created: (MNG-3310) JAVACMD set incorrectly when JAVA_HOME is not set
JAVACMD set incorrectly when JAVA_HOME is not set - Key: MNG-3310 URL: http://jira.codehaus.org/browse/MNG-3310 Project: Maven 2 Issue Type: Bug Components: Command Line Affects Versions: 2.0.8 Reporter: Matthijs Wensveen Attachments: mvn.patch In the mvn shell script, when the JAVA_HOME environment variable is not set, the script sets JAVACMD to java, probably as a best effort, hoping it is on the user's PATH. 4 lines beneath that, the JAVACMD is tested for executability, but since it is not a path to the java executable, but just the java command, this fails. The relevant part of the script (lines 122-139): if [ -z "$JAVACMD" ] ; then if [ -n "$JAVA_HOME" ] ; then if [ -x "$JAVA_HOME/jre/sh/java" ] ; then # IBM's JDK on AIX uses strange locations for the executables JAVACMD="$JAVA_HOME/jre/sh/java" else JAVACMD="$JAVA_HOME/bin/java" fi else JAVACMD=java fi fi if [ ! -x "$JAVACMD" ] ; then echo "Error: JAVA_HOME is not defined correctly." echo " We cannot execute $JAVACMD" exit 1 fi Line 131 should be changed to: JAVACMD="`which java`" -- 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
[jira] Commented: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102460 ] Matthijs Wensveen commented on MECLIPSE-264: I've just solved all the issues with WTP 2.0 for a project in my workspace. It involved a lot of clicking around in J2EE module dependencies and something with jaxb-2.0.api. Next time I encounter this, I'll try to document all the issues in detail. > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Reporter: Geir Pettersen > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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
[jira] Created: (MECLIPSE-265) profiles are not taken into account
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-default
true
myproject
target
This sets the properties ${finalName} and ${build.directory}. Later in pom.xml:
${finalName}
${build.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
[jira] Commented: (MNGECLIPSE-124) Unable to view use Maven2 using Eclipse 3.2RC4
[ http://jira.codehaus.org/browse/MNGECLIPSE-124?page=comments#action_67178 ] Matthijs Wensveen commented on MNGECLIPSE-124: -- Same problem here on linux using eclipse 3.1.2 with m2eclipse version 0.0.9. Weird thing is that it worked after I installed 0.0.5 first and then 0.0.9. Probably loads the pref page from a cache or something. Looking in the jar I found that the .class file looks to be a text file. Could this be the problem? > Unable to view use Maven2 using Eclipse 3.2RC4 > -- > > Key: MNGECLIPSE-124 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-124 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.7 > Environment: Windows XP Professional SP2 > JSE v1.5.0-06 > Eclipse 3.2RC4 > Reporter: Douglas WF Acheson > Assignee: Eugene Kuleshov > Attachments: .log > > > This is this error when I try to go to the Maven2 preferences : > Plug-in org.maven.ide.eclipse was unable to load class > org.maven.ide.eclipse.preferences.Maven2PreferencePage. > As well, I an not able to associate a project with maven2 when using the RMB > context menu for a project . I get a popup window with the following > The chosen operation is not currently available -- 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
