Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: build_system
    • Labels:
      None
    • Environment:

      Windows XP

      Description

      After updating the gf/trunk/main, when I attempt to build main/cloud-extra module, the following error happened.

      E:\gfv4\trunk\main\cloud-extra>mvn -DskipTests=true clean install
      [INFO] Scanning for projects...
      [ERROR] The build could not read 1 project -> [Help 1]
      [ERROR]
      [ERROR] The project org.glassfish.main.elasticity:elastic-metrics:4.0-SNAPSHOT (E:\gfv4\trunk\main\cloud-extra\elasticity\elastic-metrics\pom.xml) has 3 errors
      [ERROR] 'dependencies.dependency.version' for com.sun.jersey.contribs:jersey-multipart:jar is missing. @ line 88, column 21
      [ERROR] 'dependencies.dependency.version' for com.sun.jersey:jersey-client:jar is missing. @ line 92, column 21
      [ERROR] 'dependencies.dependency.version' for com.sun.jersey:jersey-json:jar is missing. @ line 96, column 21
      [ERROR]
      [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
      [ERROR]
      [ERROR] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

      The reason is that in elastic-metrics\pom.xml, the following dependency declarings missed versions.

      <dependency>
      <groupId>com.sun.jersey.contribs</groupId>
      <artifactId>jersey-multipart</artifactId>
      </dependency>
      <dependency>
      <groupId>com.sun.jersey</groupId>
      <artifactId>jersey-client</artifactId>
      </dependency>
      <dependency>
      <groupId>com.sun.jersey</groupId>
      <artifactId>jersey-json</artifactId>
      <exclusions>
      <exclusion>
      <groupId>com.sun.xml.bind</groupId>
      <artifactId>jaxb-impl</artifactId>
      </exclusion>
      </exclusions>
      </dependency>

      The declaring of above dependency version should be put in main/pom.xml, however, in main/pom.xml, I also did not find them.

        Activity

        Hide
        Joe Di Pol added a comment -

        cloud-extra has been removed from the trunk, so this bug is no longer valid.

        Show
        Joe Di Pol added a comment - cloud-extra has been removed from the trunk, so this bug is no longer valid.
        Hide
        TangYong added a comment -

        In addition, the following problems also happened in building.

        1 "cloud-extra\tenant-manager\src\main\java\org\glassfish\paas\tenantmanager\cli\impl\TenantDataMutatorAdminCommandContext" needs to implement AdminCommandContext.getProgressStatus().

        maybe http://java.net/jira/browse/GLASSFISH-12032 is related to the this.

        2 In "org\glassfish\paas\tenantmanager\apiTenantManagerTest.java", the following codes

        Assert.assertEquals("Next Id", 1, environments.allocateId());
        Assert.assertEquals("Next Id", 2, environments.allocateId());

        have problems. Should be replaced with the following codes:

        Assert.assertEquals("Next Id", 1, environments.allocateId().longValue());
        Assert.assertEquals("Next Id", 2, environments.allocateId().longValue());

        Show
        TangYong added a comment - In addition, the following problems also happened in building. 1 "cloud-extra\tenant-manager\src\main\java\org\glassfish\paas\tenantmanager\cli\impl\TenantDataMutatorAdminCommandContext" needs to implement AdminCommandContext.getProgressStatus(). maybe http://java.net/jira/browse/GLASSFISH-12032 is related to the this. 2 In "org\glassfish\paas\tenantmanager\apiTenantManagerTest.java", the following codes Assert.assertEquals("Next Id", 1, environments.allocateId()); Assert.assertEquals("Next Id", 2, environments.allocateId()); have problems. Should be replaced with the following codes: Assert.assertEquals("Next Id", 1, environments.allocateId().longValue()); Assert.assertEquals("Next Id", 2, environments.allocateId().longValue());
        Hide
        TangYong added a comment - - edited

        Because the current jersey is 2.0-m05, whether team is considering replacing com.sun.jersey(jersey 1.x) with org.glassfish.jersey(jersey 2.x) or not.After all,
        all the internal Jersey API’s underwent a significant refactoring in Jersey 2.0.

        However, I want to know whether because of jersey 2.x main/cloud-extra's building process
        will be blocked or not.

        Show
        TangYong added a comment - - edited Because the current jersey is 2.0-m05, whether team is considering replacing com.sun.jersey(jersey 1.x) with org.glassfish.jersey(jersey 2.x) or not.After all, all the internal Jersey API’s underwent a significant refactoring in Jersey 2.0. However, I want to know whether because of jersey 2.x main/cloud-extra's building process will be blocked or not.

          People

          • Assignee:
            Unassigned
            Reporter:
            TangYong
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: