[jbosstools-issues] [JBoss JIRA] (JBIDE-16574) File->Maven->Checkout Maven Project from SCM - results in error unless scm URL has "scm:null:" prefix

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-16574:
----------------------------------------

About TestNG in TP, I don't say it should be in JBT Target-Platform, but in JBDS one. If JBDS depends on something, it should have to be in target-platform. That's why we've done target-platforms. If we start re-adding repositories in pom.xml, let's just get rid of target-platform and get back to some unpredictable behaviours.
Having p2 repositories in pom files is a bad practice.

{quote}Also these should be in users settings.xml not in our pom's IMO.{quote}
Those could indeed be removed in favour of settings.xml.
                
> 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
>            Priority: Blocker
>             Fix For: 4.2.0.Beta2
>
>         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