Michael Isvy created MECLIPSE-734:
-------------------------------------
Summary: improve the attribute <additionalProjectnatures>
Key: MECLIPSE-734
URL: https://jira.codehaus.org/browse/MECLIPSE-734
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: Core : .project
Reporter: Michael Isvy
Hi,
in .project file, project natures are declared as follows:
{code}
<projectnatures>
<projectnature>org.eclipse.jdt.core.javanature</projectnature>
<projectnature>org.eclipse.wst.common.project.facet.core.nature</projectnature>
<projectnature>org.eclipse.wst.common.modulecore.ModuleCoreNature</projectnature>
<projectnature>org.eclipse.jem.workbench.JavaEMFNature</projectnature>
<projectnature>org.springframework.ide.eclipse.core.springnature</projectnature>
</projectnatures>
{code}
Inside my POM file, when configuring maven-eclipse-plugin, I can use the
attribute <additionalProjectnatures> as follows:
{code}
<additionalProjectnatures>
<projectnature>org.springframework.ide.eclipse.core.springnature</projectnature>
</additionalProjectnatures>
{code}
It works well, but it always adds the item at the end of all <projectnature>
elements. It would be nice to provide the possibility to insert this project
nature at the beginning. For instance, we could add an insert attribute like
this:
{code}
<additionalProjectnatures insert="start">
{code}
or a subtag:
{code}
<additionalProjectnatures>
<insertAtFirst />
...
</additionalProjectnatures>
{code}
Having the additional nature at first is only way to work with some of the
Eclipse decorators (see this issue for instance:
https://issuetracker.springsource.com/browse/STS-2938 )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
