[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] AJDT does not include aop.xml into output JAR
- From: "Alexander Kriegisch" <alexander@xxxxxxxxxxxxxx>
- Date: Thu, 20 Jun 2019 03:23:25 +0200 (CEST)
- Delivered-to: firstname.lastname@example.org
- User-agent: ALL-INKL Webmail 2.11
FYI, I just added https://bugs.eclipse.org/bugs/show_bug.cgi?id=548448.
It contains new findings about how to successfully create an output JAR
via "Export..." menu as well as some open questions about AJDT options
which don't seem to add any value/dunctionality to the default JDT ones.
Please read and comment, even if implementation is low on your priority
list. I really like to understand. Thank you.
> I couldn't honestly tell you if that used to work. Feel free to raise a
> bug, but I can't tell you it'd be at the top of my list ;) PRs welcome!
> Alexander Kriegisch:
>> I just opened one of my old LTW projects in Eclipse with current
>> AJDT. I have src/META-INF/aop.xml and when I build to the default bin
>> folder I see that bin/META-INF/aop.xml exists as expected. But when I
>> activate "output JAR" in the AspectJ build settings, the generated
>> JAR only contains META-INF/MANIFEST.MF with content
>> Manifest-Version: 1.0
>> Created-By: AspectJ Compiler
>> but no aop.xml. This seems to be a bug, unless I am doing something
>> stupid, putting my META-INF directory into the wrong place or so. If
>> it is old or new I cannot remember. Anyway, it is a definite
>> shortcoming, no matter whether it is a regression or has always been
>> that way.