[jbosstools-issues] [JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer
Max Rydahl Andersen (JIRA)
issues at jboss.org
Tue Mar 18 03:30:10 EDT 2014
[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12953705#comment-12953705 ]
Max Rydahl Andersen commented on JBDS-2943:
-------------------------------------------
Agree/confirm what [~fbricon] is stating and afaik egit automatically listen on project imports and add egit if .git folder is present.
[~dgolovin] can you reproduce the issue or just basing it on how it was pre-kepler where this auto-git on import was not there?
> 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.14.0.201401060023/
--
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
More information about the jbosstools-issues
mailing list