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

MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 4.4.2.AM3
    • None
    • build
    • None
    • devex #122 October 2016
    • 5

    Description

      At a minimum, the mojo should:
      foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all.

      However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm.

      So... we may wish to check transitive dependencies only in the same repo. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail.

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. JBIDE-23397 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [server]

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBIDE-23391 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]

          • 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-23393 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [cdi, batch, seam]

          • 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-23410 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [integration-tests]

          • 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-23394 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [visual-page-editor-core]

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

          Task - Represents a small unit of work that is not end-user facing. JBIDE-23395 UI dependencies from Core plugins [hibernate]

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBIDE-23396 UI dependencies from Core plugins [webservices]

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBIDE-23392 For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [common]

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

          Activity

            People

              nickboldt Nick Boldt
              rob.stryker Rob Stryker (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: