[JBoss JIRA] (ISPN-1531) Classes refactored from -commons to -api still showing up (duplicates) in binary JARs of -commons
1:58 p.m.
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
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 p.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Tristan Tarrant commented on ISPN-1531:
---------------------------------------
This is probably due to the OSGi bundle plugin which injects the -api classes into the
-commons jar. I'll look into it.
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Tristan Tarrant reassigned ISPN-1531:
-------------------------------------
Assignee: Tristan Tarrant (was: Manik Surtani)
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: Tristan Tarrant
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:01 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1531:
----------------------------------------
Hmmm, I don't see a problem between commons and api, but rather between commons and
core:
[g@z:~/Go/test/infinispan.git]% jar tf core/target/infinispan-core.jar
org/infinispan/marshall/AbstractExternalizer.class
[g@z:~/Go/test/infinispan.git]% jar tf commons/target/infinispan-commons.jar
org/infinispan/marshall/AbstractExternalizer.class
In the Infinispan build however, there's only source and '.class' file
though:
[g@z:~/Go/test/infinispan.git]% fndany AbstractExternalizer.class
./commons/target/classes/org/infinispan/marshall/AbstractExternalizer.class
Smells like some kind of issue (config or bug) with either the bundle or jar Maven plugin
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: Tristan Tarrant
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:01 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Galder Zamarreño edited comment on ISPN-1531 at 11/18/11 3:01 AM:
------------------------------------------------------------------
Hmmm, I don't see a problem between commons and api, but rather between commons and
core:
{code}[g@z:~/Go/test/infinispan.git]% jar tf core/target/infinispan-core.jar
org/infinispan/marshall/AbstractExternalizer.class{code}
{code}[g@z:~/Go/test/infinispan.git]% jar tf commons/target/infinispan-commons.jar
org/infinispan/marshall/AbstractExternalizer.class{code}
In the Infinispan build however, there's only source and '.class' file
though:
{code}[g@z:~/Go/test/infinispan.git]% fndany AbstractExternalizer.class
./commons/target/classes/org/infinispan/marshall/AbstractExternalizer.class{code}
Smells like some kind of issue (config or bug) with either the bundle or jar Maven plugin
was (Author: galder.zamarreno):
Hmmm, I don't see a problem between commons and api, but rather between commons
and core:
[g@z:~/Go/test/infinispan.git]% jar tf core/target/infinispan-core.jar
org/infinispan/marshall/AbstractExternalizer.class
[g@z:~/Go/test/infinispan.git]% jar tf commons/target/infinispan-commons.jar
org/infinispan/marshall/AbstractExternalizer.class
In the Infinispan build however, there's only source and '.class' file
though:
[g@z:~/Go/test/infinispan.git]% fndany AbstractExternalizer.class
./commons/target/classes/org/infinispan/marshall/AbstractExternalizer.class
Smells like some kind of issue (config or bug) with either the bundle or jar Maven plugin
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: Tristan Tarrant
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:03 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1531:
----------------------------------------
Thx Tristan :)
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: Tristan Tarrant
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:17 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1531:
-----------------------------------
Fix Version/s: 5.1.0.BETA5
Priority: Blocker (was: Major)
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: Tristan Tarrant
Priority: Blocker
Fix For: 5.1.0.BETA5
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:27 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Tristan Tarrant updated ISPN-1531:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/658
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: Tristan Tarrant
Priority: Blocker
Fix For: 5.1.0.BETA5
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:53 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Tristan Tarrant commented on ISPN-1531:
---------------------------------------
David Bosschaert has opened an issue against the Felix bundle plugin:
https://issues.apache.org/jira/browse/FELIX-3238
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: Tristan Tarrant
Priority: Blocker
Fix For: 5.1.0.BETA5
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:03 a.m.
[
https://issues.jboss.org/browse/ISPN-1531?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1531:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
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: Tristan Tarrant
Priority: Blocker
Fix For: 5.1.0.BETA5
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4563
days inactive
4567
days old
infinispan-issues@lists.jboss.org
10 comments
8 participants
participants (8)
-
Galder Zamarreño (Commented) (JIRA) -
Galder Zamarreño (Issue Comment Edited) (JIRA)
-
Galder Zamarreño (Updated) (JIRA)
-
Glen Taylor (Created) (JIRA)
-
Glen Taylor (Updated) (JIRA)
-
Tristan Tarrant (Assigned) (JIRA)
-
Tristan Tarrant (Commented) (JIRA)
-
Tristan Tarrant (Updated) (JIRA)