[jbosstools-issues] [JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer
Fred Bricon (JIRA)
issues at jboss.org
Wed Mar 5 09:49:38 EST 2014
[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950254#comment-12950254 ]
Fred Bricon commented on JBDS-2943:
-----------------------------------
I updated the m2e discovery catalog last night, so can now install (https://bugs.eclipse.org/bugs/show_bug.cgi?id=429360). When did you try it?
Not sure about BYOE, I don't see where the problem is actually. If the JBDS feature we install from BYOE depends on the m2eclipse-egit one, then what's the issue?
> 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: Burr Sutter
> Priority: Critical
>
> 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