[jboss-jira] [JBoss JIRA] Commented: (JBRULES-2508) Drools Spring POM file should use parent's/client's POM property for Spring Version
[
https://jira.jboss.org/browse/JBRULES-2508?page=com.atlassian.jira.plugin...
]
Anatoly Just Anatoly commented on JBRULES-2508:
-----------------------------------------------
The problem is actually a bit deeper than that, and Drools brings in 2.5.6 as well as
2.5.5..
In case anybody else is having this problem, one solution is to strip Spring dependency
form Drools all together by:
{code}
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-spring</artifactId>
<version>${drools.version}</version>
<optional>false</optional>
<!--
Brings Spring 2.5.5 and 2.5.6, which is not what we need
-->
<exclusions>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
</exclusion>
</exclusions>
</dependency>
{code}
Otherwise you might / will experience weird reflection exceptions that are coming from
Spring, since using incompatible versions.
/Anatoly
Drools Spring POM file should use parent's/client's POM
property for Spring Version
-----------------------------------------------------------------------------------
Key: JBRULES-2508
URL: https://jira.jboss.org/browse/JBRULES-2508
Project: Drools
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 5.1.0.M1
Environment: N/A
Reporter: Anatoly Just Anatoly
Assignee: Mark Proctor
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
First, I think it makes sense to depend on the latest spring release:
<spring.version>3.0.2.RELEASE</spring.version>
and not on the 2.5.6 one, which it presently depends on
Secondly this property is hard coded in a "drools-spring.pom", and while we are
using 3.0.2.RELEASE, the only way to get around the problem is tweak
"drools-spring.pom", which is highly inconvenient, since we a pulling snapshots
from repo every time .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira