Sorry for the late reply, I was on vacation. > b) Why was this behavior changed and when?
Recently class path handling needed a lot of work in AspectJ because of module support (so supporting Java9). We had to start embracing more of the JDT processing of class path entries rather than doing our own simplistic thing. This disturbed quite a few things but I fixed up what I found as problems. Looks like you've found another issue though. The bug you found is 15years old so I don't think it is that. I would raise an issue against AspectJ. > PDE Build with AspectJ is not really in use that much I could imagine that is true. If there were a JDT setting for that, I wonder if using that will now 'turn off' those warnings for JDT as we are using the JDT code more for class path processing. cheers, Andy On Sat, 11 Aug 2018 at 10:13, thofmann <em...@thomashofmann.com> wrote: > Hi everyone, > > I am trying to migrate an old PDE Build to a newer version of Eclipse, AJDT > and thus AJC. Up until now the build used AJDT 1.6.x and the Java Source > and > Target Level was set to 1.6. > The project should now be switched to used Java 8. > > I upgraded Eclipse to 4.6.3 and AJDT to 2.2.4.201703272045. When the PDE > build now tries to build a project with aspects it errors out with errors > like this: > > Sat Aug 11 18:51:49 CEST 2018 > [error] incorrect classpath: > D:\SomeProject\build-output\rcs\plugins\antlr_2.7.6\antlr-2.7.6.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\org.apache.commons.lang_2.2.0\commons-lang.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.fwk_1.13.2.20160726-1434\@dot > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.fwk.common.spec.error_1.13.2.20160726-1434\@dot > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.fwk.common.spec.trace_1.13.2.20160726-1434\@dot > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.fwk.ass.perflog.internal.websphereadminservice_1.13.2.20160726-1434\@dot > incorrect classpath: > D:\SomeProject\build-output\rcs\plugins\com.somename.container.plugin\res > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\bin > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\@dot > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\res > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\somename.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\login.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\jndiprovider.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\transport.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\httpsupport.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\datamodel.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\context.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\logging.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\util.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\ejb.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\plugins\com.somename.application.rcs.standalone.logging\lib\support.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\nestedJars\org.eclipse.equinox.registry_3.5.101.R37x_v20110810-1611\runtime_registry_compatibility.jar > incorrect classpath: > > D:\SomeProject\build-output\rcs\nestedJars\com.ibm.icu_4.4.2.v20110823\icu-data.jar > > These classpath entries really do not exist. The problem is that they are > set in the build.xml file for the project that gets generated from the PDE > build. > > I already debugged the PDE build build file generation. There are no > options > that I can use to not generate these classpath entries. > > This was no problem before. So my question now is > a) is there some way that I can tell AJC not to complain about missing > classpath entries? > b) Why was this behavior changed and when? > c) Is this a bug in AJC? > > I found this bug but no further information: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=37383 > > I find it strange that I cannot find more information about this issue but > it might well be that PDE Build with AspectJ is not really in use that > much... > > Thanks you in advance, > > Thomas > > > > > > -- > Sent from: > http://aspectj.2085585.n4.nabble.com/AspectJ-users-f2077686.html > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/aspectj-users >
_______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/aspectj-users
