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

Runtimes should be configurable with respect to what jars to return for certain runtimes

    XMLWordPrintable

Details

    Description

      deploy only runtime could have preferences to control which jars they would actually return for various facets etc.

      optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary.

      The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc.

      Attachments

        1. 2011-07-20 13.56.bmml
          7 kB
        2. 2011-07-20 13.56.png
          2011-07-20 13.56.png
          75 kB
        3. 2011-07-20 14.00.bmml
          7 kB
        4. 2011-07-20 14.00.png
          2011-07-20 14.00.png
          75 kB
        5. JBIDE-1354_20110729.png
          JBIDE-1354_20110729.png
          72 kB

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-6798 Missing JSF 2.0. JARs for JBossAS 6.0.0.M4

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

          Feature Request - Feature requests from customers and/or users JBIDE-9291 Extend the classpath for JBoss 7

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-9310 JBoss tools does not take AS 6's jsf.deployer into account

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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-9232 JBoss 7: JSF 2 apps stop working

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-9479 Enhance custom classpath containers for additional support such as as7's modules tag

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

          Activity

            People

              rob.stryker Rob Stryker (Inactive)
              manderse@redhat.com Max Andersen
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: