You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org> on 2005/11/08 18:44:06 UTC
[jira] Moved: (MPECLIPSE-106) Eclipse loses Sysdeo "Is Tomcat Project" setting after mvn eclipse:eclipse
[ http://jira.codehaus.org/browse/MPECLIPSE-106?page=all ]
Eugene Kuleshov moved MNGECLIPSE-5 to MPECLIPSE-106:
----------------------------------------------------
Key: MPECLIPSE-106 (was: MNGECLIPSE-5)
Project: maven-eclipse-plugin (was: Maven 2.x Plug-in for Eclipse)
> Eclipse loses Sysdeo "Is Tomcat Project" setting after mvn eclipse:eclipse
> --------------------------------------------------------------------------
>
> Key: MPECLIPSE-106
> URL: http://jira.codehaus.org/browse/MPECLIPSE-106
> Project: maven-eclipse-plugin
> Type: Bug
> Environment: Windows XP
> Reporter: K.C. Baltz
> Assignee: Eugene Kuleshov
>
>
> I have a web project that uses the Sysdeo Tomcat plugin for deployment. When I run the mvn eclipse:eclipse target to update my project, I lose the Sysdeo setting that tells Eclipse my project is a Tomcat project. I've tracked it down to the .project file losing an entry in the list of "natures". Before I run the eclipse plugin, I have the following nature:
> <nature>com.sysdeo.eclipse.tomcat.tomcatnature</nature>
> Afterwards it's gone.
> The workaround is easy in that I only have to change one checkbox in the settings, but i shouldn't have to do it every time.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [jira] Moved: (MPECLIPSE-106) Eclipse loses Sysdeo "Is Tomcat
Project" setting after mvn eclipse:eclipse
Posted by Lukas Theussl <lt...@apache.org>.
Is this correct? This is obviously an m2 plugin issue, so why did you
move it to MPECLIPSE?
-Lukas
Eugene Kuleshov (JIRA) wrote:
> [ http://jira.codehaus.org/browse/MPECLIPSE-106?page=all ]
>
> Eugene Kuleshov moved MNGECLIPSE-5 to MPECLIPSE-106:
> ----------------------------------------------------
>
> Key: MPECLIPSE-106 (was: MNGECLIPSE-5)
> Project: maven-eclipse-plugin (was: Maven 2.x Plug-in for Eclipse)
>
>
>>Eclipse loses Sysdeo "Is Tomcat Project" setting after mvn eclipse:eclipse
>>--------------------------------------------------------------------------
>>
>> Key: MPECLIPSE-106
>> URL: http://jira.codehaus.org/browse/MPECLIPSE-106
>> Project: maven-eclipse-plugin
>> Type: Bug
>> Environment: Windows XP
>> Reporter: K.C. Baltz
>> Assignee: Eugene Kuleshov
>
>
>>
>>I have a web project that uses the Sysdeo Tomcat plugin for deployment. When I run the mvn eclipse:eclipse target to update my project, I lose the Sysdeo setting that tells Eclipse my project is a Tomcat project. I've tracked it down to the .project file losing an entry in the list of "natures". Before I run the eclipse plugin, I have the following nature:
>> <nature>com.sysdeo.eclipse.tomcat.tomcatnature</nature>
>>Afterwards it's gone.
>>The workaround is easy in that I only have to change one checkbox in the settings, but i shouldn't have to do it every time.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org