Uploaded image for project: 'JBRULES'
  1. JBRULES
  2. JBRULES-2504

Maven: clean up the maven build and prepare for maven 3 (multi-issue)

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Minor
    • 5.2.0.M2
    • 5.1.0.M1
    • All
    • None

    Description

      This is a list of the smaller issues:

      • Don't use compile dependencies for dependencies that should be purely transitive dependencies
      • Don't use <optional> in <dependencyManagement>
      • Don't set <version> of dependencies in child pom's, only in <dependencyManagement> of the drools parent pom
        • might not already be the case
      • All of the generated files should be in the target directory
        • guvnor: version file etc
        • several modules (osgi based?): MANIFEST.MF

      Bigger issues are linked.

      Attachments

        Issue Links

          incorporates

          Feature Request - Feature requests from customers and/or users JBRULES-2909 Build: development setup howto's, tips & tricks in the README.txt file for git, maven, eclipse, intellij, ...

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

          Bug - A problem that impairs or prevents the functions of the product. JBRULES-2806 The OSGi bundles build fails because the osgi manifest contains untransformed SNAPSHOT versions in Require-Bundle

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

          Bug - A problem that impairs or prevents the functions of the product. JBRULES-2901 Eclipse plugins: First build should not fail - Upgrade to tycho 0.11.0

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

          Bug - A problem that impairs or prevents the functions of the product. JBRULES-1800 SNAPSHOT versions should have a version suffix of -SNAPSHOT instead of .SNAPSHOT

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2789 Migrate eclipse-plugin build to tycho and make use of updatesite

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2437 Add drools examples to the default build and remove the foxtrot and forms jars from subversion

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2505 Maven: use Tycho to build the drools eclipse plugin

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2506 Maven: clean up repositories and use new official JBoss repository (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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2815 Simplify build profiles and make the default profile faster

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2869 Split up the build, the repositories and hudson jobs in seperate projects: at least drools, jBPM, guvnor and eclipse so it's easier to fork, checkout and build one project

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2851 Building the documentation should not contact all the repositories constantly for eclipse stuff

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2908 Build: Our parent pom must extend jboss parent pom and do not replicate anything in there

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2816 Many dependencies are tagged scope provided, while the should probably be default scope with optional=true

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

          Patch - An improvement or enhancement to an existing feature or task. Includes patches submitted by community commiters. JBRULES-833 Maven2ize drools-examples (with automatic use of the drools eclipse plugin in eclipse) and add them to the main build

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

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Archiver:
              rhn-support-ceverson Clark Everson

              Dates

                Created:
                Updated:
                Resolved:
                Archived:

                PagerDuty