Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] AspectJ compiles fail w/ missing dependencies if manifest first builds have extra artifacts on the Bundle-Classpath 
Have you tried recently released Tycho 0.13? There were fixes in this
area ([1] and [2] in particular). Otherwise, we'd need complete
standalone project that demonstrates the problem.

Generally, tycho is expected to inject OSGi bundle dependencies back
into Maven project model (sans classpath access rules, obviously), so
aspectj compiler should have all bundle dependencies on compile classpath.


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=354118
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=348424
--
Regards,
Igor

On 11-09-21 8:58 PM, Clifford James wrote:

In MANIFEST.MF mode with an eclipse-bundle having aspects, the aspectJ
compiler will compile the aspect just fine up until the moment extra
libs are added to the Bundle-Classpath.  An example
pom.xml/build.properties file is here: https://gist.github.com/1233759.
  I am not sure if this falls outside the normal use cases, but given
that non-aspectJ compiles work fine with extra libs on the
Bundle-Classpath, it seems that the aspectJ compiler plugin should have
access to the same classpath as the usual compiler.  AspectJ without
extra bundle-classpath entries also work just fine.

The workaround I've done is use the copy-dependencies goal to setup and
copy select deps into a /lib folder that mirrors the Bundle-Classpath
but this doesn't seem DRY.  I Tested with Tycho 0.12.0, AspectJ
1.3.1/1.4 and several platforms (mac, linux, win) all with the same
result.  Not sure exactly where the bug is but would be happy to help
out with testcases and coding if someone can point me in the right
direction.

==============
Clifford James


_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user

Back to the top