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

Add drools examples to the default build and remove the foxtrot and forms jars from subversion

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

    XMLWordPrintable

Details

    • Task
    • Resolution: Duplicate
    • Major
    • 5.1.0.M2
    • 5.1.0.M1
    • All
    • None

    Description

      drools/drools-examples/drools-examples-drl/lib/foxtrot-2.0.jar shouldn't be in subversion (forms neither)
      the build.xml for ant can also be removed
      check the assembly of the examples too
      add the examples to the default build

      Attachments

        Issue Links

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

          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

          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