glassfish
  1. glassfish
  2. GLASSFISH-19604

add packager changes for JSR236 related modules

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0_b82_EE7MS7
    • Component/s: packaging
    • Labels:
      None

      Description

      Romain asked me to file this issue to track the requested packager changes for concurrent related modules.

      1. For JSR 236 API jar (external binary defined in appserver/pom.xml and also referenced in main/appserver/javaee-api/javax.javaee-api/pom.xml)
      <dependency>
      <groupId>javax.enterprise.concurrent</groupId>
      <artifactId>javax.enterprise.concurrent-api</artifactId>
      <version>$

      {concurrent-api.version}

      </version>
      </dependency>

      2. For JSR236 RI jar (external binary defined in appserver/pom.xml and will be referenced in appserver/concurrent module)
      <dependency>
      <groupId>org.glassfish</groupId>
      <artifactId>javax.enterprise.concurrent</artifactId>
      <version>$

      {concurrent.version}

      </version>
      </dependency>

      3. The appserver/concurrent modules
      a. appserver/concurrent/config module
      b. appserver/concurrent/admin module
      c. appserver/concurrent/runtime module (this module is not in the workspace yet and will be added soon, will add a note to this issue when this module is added).

        Activity

        Hide
        Romain Grécourt added a comment -

        Issue can be marked as fixed. concurrent modules are part of glassfish-common-full for GFv4.

        Show
        Romain Grécourt added a comment - Issue can be marked as fixed. concurrent modules are part of glassfish-common-full for GFv4.
        Hide
        Hong Zhang added a comment -

        Anthony just checked in the appserv/concurrent/runtime module. So all the modules are now in the workspace and ready for packager changes.

        Show
        Hong Zhang added a comment - Anthony just checked in the appserv/concurrent/runtime module. So all the modules are now in the workspace and ready for packager changes.
        Hide
        Anissa Lam added a comment -

        Console needs to know if the concurrent resources pages can be added to existing console plugin, or need to create a new plugin module for it.
        I am aware that concurrent is available only in the glassfish (full) profile, how about IPS packages ?
        If there is a separate IPS package for concurrent for its CLI and config module, then I probably need to create a new plugin for this.
        JavaMail is only available in full profile also, if concurrent is the same, then i can add that to the same module where java mail is supported, ie, console-common-full-plugin , which is part of glassfish-common-full.

        Show
        Anissa Lam added a comment - Console needs to know if the concurrent resources pages can be added to existing console plugin, or need to create a new plugin module for it. I am aware that concurrent is available only in the glassfish (full) profile, how about IPS packages ? If there is a separate IPS package for concurrent for its CLI and config module, then I probably need to create a new plugin for this. JavaMail is only available in full profile also, if concurrent is the same, then i can add that to the same module where java mail is supported, ie, console-common-full-plugin , which is part of glassfish-common-full.

          People

          • Assignee:
            Romain Grécourt
            Reporter:
            Hong Zhang
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: