-
Notifications
You must be signed in to change notification settings - Fork 317
Closed
Labels
status: declinedA suggestion or change that we don't feel we should currently applyA suggestion or change that we don't feel we should currently applytype: taskA general taskA general task
Milestone
Description
Chris Beams opened SWS-451 and commented
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.
Affects: 1.5.5
Issue Links:
- Maven dependency for oxm 1.5.5.A non-existent version of Spring [SWS-501] #633 Maven dependency for oxm 1.5.5.A non-existent version of Spring
("is duplicated by")
2 votes, 3 watchers
Metadata
Metadata
Assignees
Labels
status: declinedA suggestion or change that we don't feel we should currently applyA suggestion or change that we don't feel we should currently applytype: taskA general taskA general task