Uploaded image for project: 'JBRULES'
  1. JBRULES
  2. 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

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

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 5.2.0.M2
    • None
    • None
    • None

    Description

      still use a parent pom. Learn from seam 3.

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2920 Build: Rewrite assemblies to deal with split-up, include javadocs and are run by simply doing "mvn -Dfull install" (no need for javadocs:javadocs or assembly:assembly goals)

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2895 Strip all author tags from java 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2855 Dos2unix all source files (except .bat)

          • 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-2899 Rewrite documentation Section-Checkout.xml after the git migration and the split-up

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

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2504 Maven: clean up the maven build and prepare for maven 3 (multi-issue)

          • 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
          relates to

          Task - Represents a small unit of work that is not end-user facing. JBRULES-2897 Clean up eclipse plugin names (for example the jbpm eclipse plugin should contain jbpm)

          • 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

          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