metro
  1. metro
  2. METRO-5

webservices-api POM is missing dependencies

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: current
    • Fix Version/s: not determined
    • Component/s: www
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      5

      Description

      See
      http://maven.dyndns.org/2/javax/xml/webservices-api/1.4-SNAPSHOT/webservices-api-1.4-SNAPSHOT.pom
      for example.

      It's missing dependencies to API jars that are presumably in GF. This prevents
      the stand-alone use of Metro from Maven.

      If having this kind of dependency in POM is problematic for GFv3 builds, then
      that probably means we need two sets of groupId/artifactId, one for stand-alone
      Metro use and the other for GFv3 use.

      The missing dependency below:

      <dependency>
      <groupId>javax.activation</groupId>
      <artifactId>activation</artifactId>
      <version>1.1</version>
      </dependency>

        Activity

        Hide
        ritzmann added a comment -

        We already have a separate set specifically for GF V3 builds that contains only
        OSGi bundles. This is a genuine bug.

        Show
        ritzmann added a comment - We already have a separate set specifically for GF V3 builds that contains only OSGi bundles. This is a genuine bug.
        Hide
        ritzmann added a comment -

        Fixed on 1.4 branch and trunk.

        Show
        ritzmann added a comment - Fixed on 1.4 branch and trunk.

          People

          • Assignee:
            ritzmann
            Reporter:
            kohsuke
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: