Re: [aspectj-users] Why JoinPoint interface present in both aspectjrt an

[Andy Clement <andrew.clement@xxxxxxxxx>]

As Tahir suggests, the jars are supersets of each other. aspectjrt.jar
is the smallest, aspectjweaver is next and aspectjtools after that.
The manifests packaged with each are not really suitable for direct
deployment into an OSGi environment.  I believe the versions hosted in
the SpringSource bundle repo have the correct manifests, see
http://www.springsource.com/repository/app/library/version/detail?name=org.aspectj&version=1.6.5.RELEASE&searchType=librariesByName&searchQuery=aspectj

Andy

2009/10/4 Tahir Akhtar <tahir@xxxxxxxxxxxxxxxxxxx>:
> For usual compile-time weaving you don't need aspectj-weaver.jar in runtime
> class path. You need it only during compile-time i-e when you invoke iajc.
> aspectj-runtime.jar, as the name suggests, contains the runtime classes and
> interfaces.
>
> Regards
> Tahir Akhtar
> Shashikant Kale wrote:
>
> Hi,
>
>
>
> I am currently migrating my application to OSGi environment. I am getting
> linkage error while classloader is trying to load the class JoinPoint.
>
>
>
> Caused by: java.lang.LinkageError: loader constraints violated when linking
> org/aspectj/lang/JoinPoint class
>
>
>
> I find that both aspectj-weaver and aspectj-runtime have this interface
> defined. Is there any specific reason why this interface is included in both
> the jars?
>
>
>
> Regards,
>
> Shashi
>
> ________________________________
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>