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

[Fred Bricon (JIRA)]

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

Fred Bricon commented on JBIDE-8452:
------------------------------------

Thanks for the heads up Snjeza. I'm starting to have a better understanding of the situation.
So, on one hand we have m2eclipse-egit, which is based on the m2e scm framework and AFAICT offers little room for SCM workflow customization.
On the other hand, Snjeza's plugin is based on the "Import from Git" wizard from eGit, follows the same workflow, but adds the "import maven project" option as the last step. 
In an ideal world, eGit would provide some SPI so we could add the "import maven project" to its list of available options. I have yet to check that.
Either way, if any change is required upstream (m2e or egit), it probably won't happen before a while. I wish Chris Aniszczyk and/or Igor Fedorenko could comment on the matter.


> JBoss Maven Git integration
> ---------------------------
>
>                 Key: JBIDE-8452
>                 URL: https://issues.jboss.org/browse/JBIDE-8452
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: maven
>    Affects Versions: 3.2.0.Final
>            Reporter: Snjezana Peco
>            Assignee: Fred Bricon
>             Fix For: 3.3.0.M2
>
>
> It will enable us to import a maven project from a git repository and create project examples using examples from a git repository directly. As to the seam examples, it will be enough to add an entry to the project examples xml file.
> This feature will require EGit - http://www.eclipse.org/egit

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira