[
https://jira.jboss.org/jira/browse/JBAOP-673?page=com.atlassian.jira.plug...
]
Flavia Rainone commented on JBAOP-673:
--------------------------------------
Exactly. Plus, the jar is not working. It is useless the way it is, I tried using it in a
project at Eclipse for the tutorial and it didn't work. AFAIK, we could keep the jar
the way it is, as long as we updated the manifest classpath attribute to add the internal
jars to the classpath. But I need to check if this is going to allow people to rename
package names to avoid incompatibility with other versions of the same libraries we use,
which was initial idea when we created this jar.
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