[
https://jira.jboss.org/jira/browse/JBIDE-6214?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-6214:
---------------------------------------
Fix Version/s: 3.2.next
Affects Version/s: 3.1.0.GA
Snjezana, the use case is that those doing the examples would want to use some automated
way of generating .project/.classpath files and the closest tool for that is mvn
eclipse:eclipse but that is not really what we would like for Maven projects since
m2eclipse would/should be the one generating the proper metadata.
Can we autodetect how the import should be done for a project (i.e. if .project >
import Eclipse project, if no .project and pom.xml import Maven Project, etc.) and
possibly have a flag to control this in the project example xml ?
Still without requiring the user to have Maven plugins installed...in that case these
non-metadata projects would just be treated as normal eclipse projects I would expect.
Thoughts ?
Support project example with no Eclipse metadata, only pom.xml, in
zip
----------------------------------------------------------------------
Key: JBIDE-6214
URL:
https://jira.jboss.org/jira/browse/JBIDE-6214
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: project-examples
Affects Versions: 3.1.0.GA
Reporter: Pete Muir
Assignee: Snjezana Peco
Fix For: 3.2.next
If projects want to incorporate producing project examples into their release process,
they are likely not to have any valid eclipse metadata available for the example when
using Maven.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira