]
Mark Proctor commented on JBRULES-2738:
---------------------------------------
As long as the jar is osgi ready then we can ue that instead of the spring provided ones..
osgi-bundles: the slf4j and the ant version differ from the ones in
the main drools build
-----------------------------------------------------------------------------------------
Key: JBRULES-2738
URL:
https://issues.jboss.org/browse/JBRULES-2738
Project: Drools
Issue Type: Task
Security Level: Public(Everyone can see)
Components: All
Affects Versions: 5.1.1.FINAL
Reporter: Geoffrey De Smet
Assignee: Mark Proctor
Priority: Minor
Fix For: 5.2.0.M1
Since I am upgrading ant from 1.6.5 to 1.8.1 (to get the build working in maven 3),
I noticed that osgi-bundles uses a totally different version: 1.71
<dependency>
<groupId>org.apache.ant</groupId>
<artifactId>com.springsource.org.apache.tools.ant</artifactId>
<version>1.7.1</version>
</dependency>
Also, slf4j is 1.6 in drools, but 1.5.10 for the osgi-bundles.
That could cause an ugly MethotNotFoundError at runtime (if someone on trunk start using
the 1.6 new methods),
or bugs with the osgi users which we can't reproduce in the non-osgi bundles.
Mark, I am not sure how the osgi-bundles build works, but if you explain it's purpose
to me, I can handle this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: