[ http://jira.codehaus.org/browse/MNGECLIPSE-125?page=all ]
Eugene Kuleshov updated MNGECLIPSE-125:
---------------------------------------
Priority: Minor (was: Critical)
Please provide sample project that would allow to reproduce this issue.
Lovering priority untill that.
>From other hand, I am pretty sure that other users also using pde and it is
>strange that nobody reported this before.
> 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
> Type: Bug
> Versions: 0.0.7
> Environment: Eclipse 3.1.2
> Reporter: Henrik Mejlgaard
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> 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
