Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-12937

provide checkout.sh script for pulling jbosstools repos from forks / master

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.0.0.Beta2
    • 4.0.0.Beta2
    • build
    • None

    Description

      Initial contribution:

      https://github.com/jbosstools/jbosstools-build/blob/master/scripts/checkout.sh

      Problem:

      Using the script, we should have this on disk:

      git remote -v
origin	git@github.com:nickboldt/jbosstools-base.git (fetch)
origin	git@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

      But instead we have:

      git remote -v
nickboldt	git://github.com/nickboldt/jbosstools-base.git (fetch)
nickboldt	git://github.com/nickboldt/jbosstools-base.git (push)
origin	git@github.com:jbosstools/jbosstools-base.git (fetch)
origin	git@github.com:jbosstools/jbosstools-base.git (push)
-------------------------------------------------------------
git branch -v
  master           [origin/master]
* nickboldt/master

      Attachments

        Issue Links

          is duplicated by

          Feature Request - Feature requests from customers and/or users JBIDE-12993 Cleanup/create plain checkout.sh script for jbosstools repos from github

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-12475 Split JBoss Tools into several functional groups of components for migration to Github

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: