[SWS-697] Support Maven 3 Remove legacy xws-security Created: 12/Mar/11  Updated: 04/May/12  Resolved: 19/Aug/11

Status: Closed
Project: Spring Web Services
Component/s: Samples
Affects Version/s: 2.0.1
Fix Version/s: 2.0.3

Type: Improvement Priority: Major
Reporter: Gordon Dickens Assignee: Arjen Poutsma
Resolution: Complete Votes: 6
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 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



 Comments   
Comment by David Kerwick [ 08/Apr/11 ]

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

Comment by Gordon Dickens [ 08/Apr/11 ]

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.

Comment by Jochen Terstiege [ 24/May/11 ]

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

Comment by andre beskrowni [ 25/May/11 ]

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

Comment by Chris [ 14/Jul/11 ]

This issue brakes me, too ...

Comment by Jochen Terstiege [ 28/Jul/11 ]

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

Comment by Arjen Poutsma [ 19/Aug/11 ]

Added XML formatting

Comment by Arjen Poutsma [ 19/Aug/11 ]

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.

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Thu Dec 14 14:59:52 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.