[jbosstools-issues] [JBoss JIRA] (JBIDE-12937) provide checkout.sh script for pulling jbosstools repos from forks / master

Nick Boldt (JIRA) jira-events at lists.jboss.org
Wed Oct 24 16:23:01 EDT 2012


     [ https://issues.jboss.org/browse/JBIDE-12937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt closed JBIDE-12937.
------------------------------

    Resolution: Done


Closing for now.
                
> provide checkout.sh script for pulling jbosstools repos from forks / master
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-12937
>                 URL: https://issues.jboss.org/browse/JBIDE-12937
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 4.0.0.CR1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.0.0.CR1
>
>
> Initial contribution:
> https://github.com/jbosstools/jbosstools-build/blob/master/scripts/checkout.sh
> Problem:
> Using the script, we should have this on disk:
> {code}
> git remote -v
> origin	git at github.com:nickboldt/jbosstools-base.git (fetch)
> origin	git at github.com:nickboldt/jbosstools-base.git (push)
> upstream	git://github.com/jbosstools/jbosstools-base.git (fetch)
> upstream	git://github.com/jbosstools/jbosstools-base.git (push)
> -------------------------------------------------------------
> git branch -v
> * master          [origin/master]
>   upstream/master 
> {code}
> But instead we have:
> {code}
> git remote -v
> nickboldt	git://github.com/nickboldt/jbosstools-base.git (fetch)
> nickboldt	git://github.com/nickboldt/jbosstools-base.git (push)
> origin	git at github.com:jbosstools/jbosstools-base.git (fetch)
> origin	git at github.com:jbosstools/jbosstools-base.git (push)
> -------------------------------------------------------------
> git branch -v
>   master           [origin/master]
> * nickboldt/master 
> {code}

--
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