[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3874) Maven integration

[Eugene Kuleshov (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12461485#action_12461485 ] 

Eugene Kuleshov commented on JBIDE-3874:
----------------------------------------

As for "materializing maven projects" feature, it is intended for importing projects that been released and not for creating new projects. The sequence is like this:

* developer creates project and provides a correct scm information (i.e. location in the version control system)
* developer makes a release and deploys the release artifact into a maven repository
* repository is indexed with the nexus indexer
* user downloads index into the ide to allow local search of artifacts
* user selects some jars (e.g. one of the dependencies in his own project) and call "materialize maven project"
* the ide then resolves the pom.xml for selected jars, reads the scm information for each of them and then it does chechout and import maven projects into Eclipse workspace
* jar dependencies are replaced with links to the imported project, so it is ready for modification and debugging

If you need to create a new project you should use the "New Maven Project" wizard and can select between creating a simple project of use one of the available archetypes. You can also add your own archetypes and even package them in your Eclipse plugin [1].

[1] http://docs.codehaus.org/display/M2ECLIPSE/Extension+Points+and+API#ExtensionPointsandAPI-MavenArchetypeCatalogs(since0.9.3)

> Maven integration
> -----------------
>
>                 Key: JBIDE-3874
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3874
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: common
>    Affects Versions: 3.0.0.GA
>            Reporter: Max Rydahl Andersen
>            Priority: Critical
>             Fix For: 3.1.0
>
>
> It is time to make sure our stuff works well with Maven, at least to the extent that the underline runtimes support it.
> First shot would be to add an adapter that allows m2eclipse controlled projects to activate the seam features.
> That would allow us still to bundle JBoss Tools without any dependencies to m2eclipse which still seem to drag in non-compatible plugins which we need to look into before tying us to m2eclipse.

-- 
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