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

Refactoring: get rid of "fullSite", stick with "repository"

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Minor
    • 4.5.1.AM2
    • 4.3.0.Alpha1
    • build
    • None
    • devex #116 June 2016, devex #128 February 2017, devex #132 May 2017, devex #137 September 2017

    Description

      Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.

      Attachments

        Issue Links

          blocks

          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-18772 Include publish steps in pom files

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Sub-task - The sub-task of the issue JBIDE-20158 migrate devstudio.product to use mojo instead of direct calls to rsync

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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3408 installer is trying to reach download.jboss.org for content

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3423 JBDS update site has blue JBT branding instead of red JBDS branding

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

          Task - Represents a small unit of work that is not end-user facing. JBIDE-16158 Investigate tools/processes to templatize CI jobs

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              nickboldt Nick Boldt
              mistria@redhat.com Mickael Istria
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: