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

Design http://download.jboss.org/jbosstools structure

    XMLWordPrintable

Details

    • Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, Sprint #9 September 2016

    Description

      We have several types of objects which names should be presented in site stucture:

      1. Project: jbosstools
      2. Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
      3. Subproject: core, soatools
      4. Module: base, javaee, central, freemarker and etc.
      5. Distribution Type: updates|builds
      6. Bits Type: stable|development|nightly
      7. Targeted Eclipse: indigo|juno|kepler
      8. You name it ...

      Now we mostly use following patterns to publish nightly bits, but not always and not for every project:

      1. aggregated update sites: ${Project Name}/updates/${Bits Type}/${Subproject Name}/${Targeted Eclipse}
      2. jbosstools modules composite nightly update sites are in ${Project Name}/builds/staging and it has no structure
      3. jbosstools modules builds are published to ${Project Name}/builds/${Bits Type} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits

      Attachments

        Issue Links

          incorporates

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. NEXUS-89 Installing p2 unzip plugin into JBoss Nexus ?

          • 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.
          • Done

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-13283 Use Akamai for Target-Platform, Mirror, releases stuff

          • 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
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. JBIDE-15482 Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

          • 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
          is related to

          Feature Request - Feature requests from customers and/or users JBDS-2623 Create target platform for mirrored parts of Central / 3rd Party Extras

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-14448 Build doesn't detect cycle dependencies between JBossTools modules

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3208 reorg/refactor directories for consistency across JBT/JBDS

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-18236 Produce better doc for project leads for how to build their component in Jenkins

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-19598 Use "Build other project (extended)" to cascade aggregation

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open
          relates to

          Feature Request - Feature requests from customers and/or users JBIDE-15135 Attach metadata during assembly instead of publish time

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-17536 JBoss Tools Core Nightly update site fails to install if a new build is published during install

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-16309 Move inter-JBT dependencies to component poms

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-16128 Publish component sites to Nexus

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Reopened

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: