]
Glen Taylor updated ISPN-1531:
------------------------------
Attachment: infinispan-api-5.1.0-20111117.100113-2.jar
infinispan-commons-5.1.0-20111117.100128-2.jar
infinispan-commons-5.1.0-20111117.100128-2-sources.jar
Attaching example snapshot JARs, since the provided links will likely roll off soon.
Classes refactored from -commons to -api still showing up
(duplicates) in binary JARs of -commons
-------------------------------------------------------------------------------------------------
Key: ISPN-1531
URL:
https://issues.jboss.org/browse/ISPN-1531
Project: Infinispan
Issue Type: Bug
Components: Build process
Affects Versions: 5.1.0.BETA4
Reporter: Glen Taylor
Assignee: Manik Surtani
Attachments: infinispan-api-5.1.0-20111117.100113-2.jar,
infinispan-commons-5.1.0-20111117.100128-2-sources.jar,
infinispan-commons-5.1.0-20111117.100128-2.jar
The "binaries" JAR for {{-commons}} still contains some classes that have been
refactored to the {{-api}} JAR, which results in duplicates of the classes in the
classpath, and mismatched source/binary JARs.
Example mismatched JAR pair (which may not exist by the time you read this - attaching in
case):
* {{infinispan-commons-5.1.0-20111117.100128-2}}
**
[
sources|https://repository.jboss.org/nexus/content/groups/public/org/infi...]
**
[
binaries|https://repository.jboss.org/nexus/content/groups/public/org/inf...]
Several packages are affected, including:
* {{org.infinispan.executors}}
* {{org.infinispan.lifecycle}}
* {{org.infinispan.manager}}
This seems to be related to [commit
907621288ee8c84d4db64dbf0e6acfb954a8e12f|https://github.com/infinispan/in...]
in which several of these classes were re-factored from {{-commons}} to {{-api}}. For
whatever reason, the classes are showing up in the binary builds of both {{-commons}}
_AND_ {{-api}}. Problem present in BETA4 and recent SNAPSHOT builds.
Sorry, my Maven skillz are really too weak to suggest a patch/fix, but it's
definitely causing issues trying to trace through stuff in my dev environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: