Setting environment variables in surefire configuration overwrite the existing
environment
--
Key: SUREFIRE-308
URL: http://jira.codehaus.org/browse/SUREFIRE-308
Additional webResources are not added to the component list when using WTP
projects generation
--
Key: MECLIPSE-111
URL: http://jira.codehaus.org/browse/MECLIPSE-111
Project: Maven 2
[ http://jira.codehaus.org/browse/MNG-939?page=all ]
Renaud Julienne updated MNG-939:
Attachment: MNG-939-maven-core.patch
> specify maven settings from command line
>
>
> Key: MNG-939
> URL: htt
[ http://jira.codehaus.org/browse/MECLIPSE-89?page=all ]
Renaud Julienne updated MECLIPSE-89:
Attachment: MNG-MECLIPSE-89-maven-eclipse-plugin.patch
> Eclipse plugin should not try to resolve system dependencies paths relatively
> to project locatio
Eclipse plugin should not try to resolve system dependencies paths relatively
to project location.
--
Key: MECLIPSE-89
URL: http://jira.codehaus.org/browse/MECLIPSE-89
Project: M
[ http://jira.codehaus.org/browse/MNG-1983?page=comments#action_62257 ]
Renaud Julienne commented on MNG-1983:
--
I had the same issue, so I looked for the reason. This fails when the parent
class is in another jar because the plugin tools rely on the jav
Eclipse plugin should not try to download sources of system dependencies
Key: MECLIPSE-87
URL: http://jira.codehaus.org/browse/MECLIPSE-87
Project: Maven 2.x Eclipse Plugin
Type: Bug
Versio
[ http://jira.codehaus.org/browse/MNG-2037?page=comments#action_60479 ]
Renaud Julienne commented on MNG-2037:
--
I had the same issue and found a workaround.
In the profile build section, just add an empty pluginManagement section.
>From org.apache.maven