[
https://jira.jboss.org/jira/browse/JBAOP-673?page=com.atlassian.jira.plug...
]
Kabir Khan commented on JBAOP-673:
----------------------------------
I did not understand what you meant at first :-), but having built the release I see what
you mean
$unzip -l jboss-aop-single.jar
Archive: jboss-aop-single.jar
Length Date Time Name
-------- ---- ---- ----
0 11-05-08 19:33 META-INF/
572 11-05-08 19:33 META-INF/MANIFEST.MF
597476 10-13-08 23:03 javassist-3.9.0.GA.jar
204802 10-21-08 11:02 jboss-reflect-2.0.0.GA.jar
11924 06-13-08 11:15 jboss-logging-spi-2.0.5.GA.jar
448025 08-27-08 12:48 jboss-common-core-2.2.8.GA.jar
174536 10-21-08 10:58 jboss-mdr-2.0.0.GA.jar
361155 06-25-08 09:18 trove-2.1.1.jar
367444 06-13-08 11:15 log4j-1.2.14.jar
24500 06-13-08 11:17 jboss-logging-log4j-2.0.5.GA.jar
1311921 11-05-08 19:33 jboss-aop-2.0.0-SNAPSHOT.jar
-------- -------
3502355 11 files
The jar should contain the contents of the other jars, not the other jars themselves. In
other words all the contained jars should be unzipped to a location and then zipped up
into the single jar. I am convinced that is the way it used to work, maybe something went
wrong in the mavenisation of the project?
jboss-aop-single.jar structure is wrong
---------------------------------------
Key: JBAOP-673
URL:
https://jira.jboss.org/jira/browse/JBAOP-673
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.GA
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: 2.0.1.GA
If this jar is going to contain the other jars, it is important to add those jars to the
classpath.
However, I am not sure if the new structure of the single.jar will allow people to easily
rename packge names to avoid different versions of dependency crashing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira