Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-697

Support Maven 3 Remove legacy xws-security

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.0.3
    • Component/s: Samples
    • Labels:
      None

      Description

      As a developer, I would like to include my Spring WS in my projects and build with Maven 3.x. The dependency on com.sun.xml.wss which is referenced as a legacy repository, not supported by Maven 3.

      In the "spring-ws-security-2.0.0.RELEASE.pom" file

        <!-- XWSS dependencies -->
        <dependency>
            <groupId>com.sun.xml.wss</groupId>
            <artifactId>xws-security</artifactId>
        </dependency>

      available from the following repository:

              <repository>
                  <id>java.net</id>
                  <name>Java.net Repository for Maven2</name>
                  <url>http://download.java.net/maven/1/</url>
                  <layout>legacy</layout>
                  <snapshots>
                      <enabled>false</enabled>
                  </snapshots>
                  <releases>
                      <enabled>true</enabled>
                  </releases>
              </repository>

      Can this be changed to use the following?

        <properties>
          <geronimo.ws.version>1.1.3</geronimo.ws.version>
          <xws.version>1.3.1</xws.version>
        </properties>
      ...
        <dependency>
          <groupId>org.apache.geronimo.specs</groupId>
          <artifactId>geronimo-ws-metadata_2.0_spec</artifactId>
          <version>${geronimo.ws.version}</version>
        </dependency>
        <dependency>
          <groupId>com.sun.xml.wsit</groupId>
          <artifactId>xws-security</artifactId>
          <version>${xws.version}</version>
        </dependency>

      Where the xws jars are from the following repository?

        <repository>
          <id>jboss.repository.releases.public</id>
          <name>JBoss Repo Public</name> 
          <url>http://repository.jboss.org/nexus/content/groups/public-jboss</url>
        </repository>

      Regards,
      Gordon Dickens
      twitter.com/gdickens
      linkedin.com/in/gordondickens
      Blog: technophile.gordondickens.com

        Activity

        gordonad Gordon Dickens created issue -
        Hide
        david kerwick David Kerwick added a comment -

        I agree, I came across this issue by accident as the Mac I'm using has maven 3 installed by default and STS will use the embedded Maven for dependency resolution which on 2.6.0.release is also Maven 3.
        I was able to get around the problem by running
        ../../springsource/maven-2.2.1.RELEASE/bin/./mvn package
        This downloaded the legacy jars and allowed STS Maven to work again.

        I think more people we start to encounter this problem even though they may have not made the conscious decision to move to Maven 3

        David

        Show
        david kerwick David Kerwick added a comment - I agree, I came across this issue by accident as the Mac I'm using has maven 3 installed by default and STS will use the embedded Maven for dependency resolution which on 2.6.0.release is also Maven 3. I was able to get around the problem by running ../../springsource/maven-2.2.1.RELEASE/bin/./mvn package This downloaded the legacy jars and allowed STS Maven to work again. I think more people we start to encounter this problem even though they may have not made the conscious decision to move to Maven 3 David
        Hide
        gordonad Gordon Dickens added a comment -

        Once people realize that it is not significantly different in configuration, it might get more widely accepted. It is simply more strict in its dependency resolution and the Site plugin requires a bit more configuration. So now, I have been using Maven 3.0.3 all the time and clean up my projects to be more durable.

        IMHO, The embedded Maven in STS is an old beta version and should be updated.

        Show
        gordonad Gordon Dickens added a comment - Once people realize that it is not significantly different in configuration, it might get more widely accepted. It is simply more strict in its dependency resolution and the Site plugin requires a bit more configuration. So now, I have been using Maven 3.0.3 all the time and clean up my projects to be more durable. IMHO, The embedded Maven in STS is an old beta version and should be updated.
        Hide
        jterstiege Jochen Terstiege added a comment -

        Still not fixed in spring-security-2.0.2 release. Right now this blocks the maven 3 compatibility for OpenSAGA 2.0.

        Show
        jterstiege Jochen Terstiege added a comment - Still not fixed in spring-security-2.0.2 release. Right now this blocks the maven 3 compatibility for OpenSAGA 2.0.
        Hide
        beskrowni andre beskrowni added a comment -

        I also ran into this issue when adding an ivy dependency for spring-ws-security, revision 2.0.2.RELEASE.

        Show
        beskrowni andre beskrowni added a comment - I also ran into this issue when adding an ivy dependency for spring-ws-security, revision 2.0.2.RELEASE.
        Hide
        chris_ad Chris added a comment -

        This issue brakes me, too ...

        Show
        chris_ad Chris added a comment - This issue brakes me, too ...
        Hide
        jterstiege Jochen Terstiege added a comment -

        Come on guys, this ticket is now unresolved for over four months. It can't be that difficult to fix.

        Show
        jterstiege Jochen Terstiege added a comment - Come on guys, this ticket is now unresolved for over four months. It can't be that difficult to fix.
        arjen.poutsma Arjen Poutsma made changes -
        Field Original Value New Value
        Affects Version/s 2.0 GA [ 10981 ]
        Component/s Samples [ 10190 ]
        Component/s Security [ 10211 ]
        Affects Version/s 2.0.1 [ 11810 ]
        Assignee Arjen Poutsma [ arjen.poutsma ]
        arjen.poutsma Arjen Poutsma made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Added XML formatting

        Show
        arjen.poutsma Arjen Poutsma added a comment - Added XML formatting
        arjen.poutsma Arjen Poutsma made changes -
        Description As a developer, I would like to include my Spring WS in my projects and build with Maven 3.x. The dependency on com.sun.xml.wss which is referenced as a legacy repository, not supported by Maven 3.

        In the "spring-ws-security-2.0.0.RELEASE.pom" file

          <!-- XWSS dependencies -->
          <dependency>
              <groupId>com.sun.xml.wss</groupId>
              <artifactId>xws-security</artifactId>
          </dependency>

        available from the following repository:
                <repository>
                    <id>java.net</id>
                    <name>Java.net Repository for Maven2</name>
                    <url>http://download.java.net/maven/1/&lt;/url>
                    <layout>legacy</layout>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                </repository>

        Can this be changed to use the following?
          <properties>
            <geronimo.ws.version>1.1.3</geronimo.ws.version>
            <xws.version>1.3.1</xws.version>
          </properties>
        ...
          <dependency>
            <groupId>org.apache.geronimo.specs</groupId>
            <artifactId>geronimo-ws-metadata_2.0_spec</artifactId>
            <version>${geronimo.ws.version}</version>
          </dependency>
          <dependency>
            <groupId>com.sun.xml.wsit</groupId>
            <artifactId>xws-security</artifactId>
            <version>${xws.version}</version>
          </dependency>

        Where the xws jars are from the following repository?
          <repository>
            <id>jboss.repository.releases.public</id>
            <name>JBoss Repo Public</name>
            <url>http://repository.jboss.org/nexus/content/groups/public-jboss&lt;/url>
          </repository>


        Regards,
        Gordon Dickens
        twitter.com/gdickens
        linkedin.com/in/gordondickens
        Blog: technophile.gordondickens.com
        As a developer, I would like to include my Spring WS in my projects and build with Maven 3.x. The dependency on com.sun.xml.wss which is referenced as a legacy repository, not supported by Maven 3.

        In the "spring-ws-security-2.0.0.RELEASE.pom" file

        {code:xml}
          <!-- XWSS dependencies -->
          <dependency>
              <groupId>com.sun.xml.wss</groupId>
              <artifactId>xws-security</artifactId>
          </dependency>
        {code}

        available from the following repository:
        {code:xml}
                <repository>
                    <id>java.net</id>
                    <name>Java.net Repository for Maven2</name>
                    <url>http://download.java.net/maven/1/&lt;/url>
                    <layout>legacy</layout>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                </repository>
        {code}

        Can this be changed to use the following?
        {code:xml}
          <properties>
            <geronimo.ws.version>1.1.3</geronimo.ws.version>
            <xws.version>1.3.1</xws.version>
          </properties>
        ...
          <dependency>
            <groupId>org.apache.geronimo.specs</groupId>
            <artifactId>geronimo-ws-metadata_2.0_spec</artifactId>
            <version>${geronimo.ws.version}</version>
          </dependency>
          <dependency>
            <groupId>com.sun.xml.wsit</groupId>
            <artifactId>xws-security</artifactId>
            <version>${xws.version}</version>
          </dependency>
        {code}

        Where the xws jars are from the following repository?
        {code:xml}
          <repository>
            <id>jboss.repository.releases.public</id>
            <name>JBoss Repo Public</name>
            <url>http://repository.jboss.org/nexus/content/groups/public-jboss&lt;/url>
          </repository>
        {code}


        Regards,
        Gordon Dickens
        twitter.com/gdickens
        linkedin.com/in/gordondickens
        Blog: technophile.gordondickens.com
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        This turned out to be a little more difficult than expected, but it is now fixed in SVN. Let me know if it doesn't work for you.

        Show
        arjen.poutsma Arjen Poutsma added a comment - This turned out to be a little more difficult than expected, but it is now fixed in SVN. Let me know if it doesn't work for you.
        arjen.poutsma Arjen Poutsma made changes -
        Fix Version/s 2.0.3 [ 12197 ]
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Complete [ 8 ]
        Hide
        arjen.poutsma Arjen Poutsma added a comment -

        Closing old issues

        Show
        arjen.poutsma Arjen Poutsma added a comment - Closing old issues
        arjen.poutsma Arjen Poutsma made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        159d 17h 21m 1 Arjen Poutsma 19/Aug/11 3:18 AM
        In Progress In Progress Resolved Resolved
        1h 29m 1 Arjen Poutsma 19/Aug/11 4:47 AM
        Resolved Resolved Closed Closed
        259d 2h 16m 1 Arjen Poutsma 04/May/12 7:03 AM

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            gordonad Gordon Dickens
          • Votes:
            6 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: