You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org> on 2006/08/01 04:12:31 UTC
[jira] Closed: (MNGECLIPSE-125) Using PDE Tools|Update classpath
removes Maven2 nature from project
[ http://jira.codehaus.org/browse/MNGECLIPSE-125?page=all ]
Eugene Kuleshov closed MNGECLIPSE-125.
--------------------------------------
Resolution: Incomplete
Please feel free to reopen when there is more information.
> Using PDE Tools|Update classpath removes Maven2 nature from project
> -------------------------------------------------------------------
>
> Key: MNGECLIPSE-125
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-125
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.7
> Environment: Eclipse 3.1.2
> Reporter: Henrik Mejlgaard
> Assigned To: Eugene Kuleshov
> Priority: Minor
> Attachments: mngeclipse_shared.zip
>
>
> When using the PDE Tools|Update classpath on an Eclipse (plugin) project containing a plugin.xml, the Maven2-nature of the project is consitently removed.
> This is very annoying as the PDE Tools|Update classpath seems to be automatically issued when Eclipse starts up. This means that projects, which have been Maven2-natured in our SCM, when opened does not compile properly before the Maven2-nature is manually enabled.
--
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