Uploaded image for project: 'JBoss Enterprise Application Platform 6'
  1. JBoss Enterprise Application Platform 6
  2. JBPAPP6-154

Require method to differentiate EAP 6 from AS 7 in NON-RUNNING server


    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: EAP 6.0.0 DR 8
    • Fix Version/s: EAP 6.0.0 DR 9
    • Component/s: Build
    • Labels:


      JBDS obviously needs some way to tell different server installation types apart. Previous versions of EAP have, in their primary jar (and often, other jars as well), a manifest entry designating that the jar is an EAP jar, to distinguish it from the community versions. For example, EAP 5.1's run.jar's manifest.mf has the following:

      Implementation-Title: JBoss [EAP]

      I believe Implementation-Title has been the standard location for several versions where this has been declared. However, EAP 6's "jboss-modules.jar" contains no similar entry in manifest.mf. In fact, doing a full grep for "EAP" on the entire EAP 6.0 installation comes up with very few results, most of which (that I can see) are only matching because a zipped file happens to somehow match it, but upon unzipping, no match. (This is using the alpha 1 release)

      Suggested locations for the implementation title are:
      1) jboss-modules.jar
      2) modules/org/jboss/as/server/main/jboss-as-server-7.0.0.Final.jar

      [2] already has an implementation title, but it is not EAP-distinctive, and says:
      Implementation-Title: JBoss Application Server: Server

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  rob.stryker Rob Stryker
                  rob.stryker Rob Stryker
                • Votes:
                  0 Vote for this issue
                  5 Start watching this issue


                  • Created: