[
https://jira.jboss.org/browse/JBIDE-6214?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-6214:
--------------------------------------
The project example ext. point serves to define a project example. The implementation of
the ext.point (downloading projects, importing project, building projects, quick fixes,
fixing requirements) has been done within the plugin and has to include necessary
dependencies.
Importing a Maven project would also have to be implemented within the plugin. What is
possible to do is the following:
- creating an ext. point/service (org.jboss.tools.project.examples.importMavenProject, for
instance), in a separate plugin (org.jboss.tools.project.examples.maven, for instance).
The implementation of the ext. point (importing an existing Maven project) has to depend
on m2eclipse.
- in a project example xml file, a developer would define a pure Maven project by adding
the "type" element with the "maven" value to the "project"
element. If the org.jboss.tools.project.examples.importMavenProject ext. point doesn't
exist, such projects would be ignored. If exists, the project would be created using the
m2eclipse API.
WDYT ?
Support project example with no Eclipse metadata, only pom.xml, in
zip
----------------------------------------------------------------------
Key: JBIDE-6214
URL:
https://jira.jboss.org/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.x
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/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira