[jbosstools-issues] [JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer
[
https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin....
]
Denis Golovin edited comment on JBDS-2943 at 3/13/14 7:55 PM:
--------------------------------------------------------------
There is only one problem with this tool. It works only for repositories cloned using
egit, if you add existing git repo and then try to use Import Maven project it imports
projects but they are not shared.
was (Author: dgolovin):
There is only one problem with this tool. It works only for repositories cloned using
egit, if you add existing git repo and then try to use Import Maven project it imports
projects but they are not shared project.
Add m2eclipse-egit to JBDS installer
------------------------------------
Key: JBDS-2943
URL: https://issues.jboss.org/browse/JBDS-2943
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: installer, maven
Affects Versions: 7.1.0.GA
Reporter: Fred Bricon
Assignee: Nick Boldt
Priority: Critical
Fix For: 8.0.0.Beta1
Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM
connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see
JBIDE-16574)
I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit
in there, so the use case described in JBIDE-16574 can work OOTB.
Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that
would add little value over the existing m2e discovery mechanism.
Latest m2eclipse-egit build is available from
http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.1...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira