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

Migrate eclipse-plugin build to tycho and make use of updatesite

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

    XMLWordPrintable

Details

    Attachments

      Issue Links

        duplicates

        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
        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

        Bug - A problem that impairs or prevents the functions of the product. JBRULES-2805 Problem getting and using drools-api SNAPSHOT version from jboss maven repo

        • 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

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved:
              Archived:

              PagerDuty