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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-16574:
---------------------------------------------

btw. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L91 is for me perfectly valid - this is exactly documenting how it works.

What is weird to me though is why these that are already in parent pom is there:
https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L67
https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml#L75

same repeats in pluginRepositories ?

Also these should be in users settings.xml not in our pom's IMO.
                
> 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