[jbosstools-issues] [JBoss JIRA] (JBIDE-16574) File->Maven->Checkout Maven Project from SCM - results in error unless scm URL has "scm:null:" prefix
[
https://issues.jboss.org/browse/JBIDE-16574?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-16574:
-------------------------------------
m2e doesn't come with SCM connectors by default. They're semi-maintained, outside
of eclipse.org (on [Github|https://github.com/tesla/m2eclipse-egit] actually).
As a workaround, you should click on the "find more SCM connectors in the m2e
marketplace" link, and pick m2e-egit.
I guess we could :
* add a more explicit error message in m2e, pointing at the same link, but that's an
upstream concern
* add m2e-egit to the JBDS installer (as it already depends on m2e and egit)
* maybe add m2e-egit to JBoss Central for JBT users.
[~maxandersen], [~nickboldt], [~burrsutter] WDYT?
File->Maven->Checkout Maven Project from SCM - results in error
unless scm URL has "scm:null:" prefix
-----------------------------------------------------------------------------------------------------
Key: JBIDE-16574
URL: https://issues.jboss.org/browse/JBIDE-16574
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, upstream
Affects Versions: 4.2.0.Alpha2
Environment: RHEL6
OpenJDK 1.7
JBT 4.2.0.alpha2.respin-a
Reporter: Len DiMaggio
Fix For: 4.2.0.Beta1
Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot-3.png,
Screenshot.png
See attached screenshots - if a user attempts to import TicketMonster with this URL:
git://github.com/jboss-jdf/ticket-monster.git
This error is raised: "Select SCM type and URL"
Using this URL clears the error condition:
scm:null:git://github.com/jboss-jdf/ticket-monster.git
--
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