[SWS-451] Update spring-ws Maven POM to use correct Spring artifactId values Created: 26/Nov/08  Updated: 04/May/12  Resolved: 25/Feb/10

Status: Closed
Project: Spring Web Services
Component/s: None
Affects Version/s: 1.5.5
Fix Version/s: 2.0 M1

Type: Task Priority: Major
Reporter: Chris Beams Assignee: Arjen Poutsma
Resolution: Won't Fix Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SWS-501 Maven dependency for oxm 1.5.5.A non-... Closed

 Description   

From original forum post at http://forum.springframework.org/showthread.php?p=215024#post215024

Spring-WS still points to artifactIds as they sit in the Maven central repository, e.g.:

<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-aop</artifactId>
</dependency>

Whereas other portfolio projects, like JavaConfig, reference artifactIds from the SpringSource Enterprise Bundle Repository:

<dependency>
<groupId>org.springframework</groupId>
<artifactId>org.springframework.aop</artifactId>
<version>2.5.6</version>
<optional>true</optional>
</dependency>

In cases where a user is dependent on both spring-ws and spring-javaconfig, this results in duplicate spring-aop jars on their classpath.

Please update spring-ws to point to the newer artifactIds.



 Comments   
Comment by Arjen Poutsma [ 16/Dec/08 ]

Moving this to the next major release, because changing our deps would break backwards compatibility for maven users. For instance, they might have to change their exclusion patterns, etc.

Comment by Arjen Poutsma [ 25/Feb/10 ]

The main POM will keep having a reference to the maven central artifacts, while the EBR pom will reference EBR artifacts.

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Sun Dec 17 04:03:36 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.