[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Problem with aspectJ Maven plugin (was: Compiler problem when building with Maven)
|
Hermann,
If I remember correctly it was similar problems that led me to abandon
using Maven for the compile step altogether. If I'm remembering right
it is actually impossible to tell Maven not to build what is included
in src/main/java, what you end up doing when adding the AJ plugin is
just having that compile step occur first and then running a
completely redundant one afterwards. So what I ended up doing is
moving all of my source to src/main/aspectj and then configuring the
AJ plugin accordingly... unfortunately I can't remember how to do that
off the top of my head. At this point I've taken it a step further
and I let Eclipse compile my Java/AJ code directly to target/classes
and since Maven ignores the src/main/aspectj folder it both speeds up
my builds greatly and allows me to upgrade AJ as necessary by just
grabbing the latest version of AJDT. Of course you can't build
outside of Eclipse that way, so if you are doing any type of
continuous integration or other external build process it might not be
appropriate for you.
On Nov 10, 2009, at 1:00 PM, prg@xxxxxxxxxxxxxxx wrote:
Hi Dave,
just a second before I've found your post to the mojo users list in
the archives.... :)
Dave Whittaker schrieb:
I think this will do it. I haven't used the Maven AJ plugin for a
while, but in the past I've used specific dependencies for the plugin
itself to override the version of the compiler it used.
.....
While we're at this topic, maybe you (or someone else) know how to
deal
with the following problem:
We are forced to use the current snapshot version of the plugin,
because
we need support for the "hasMember" toggle.
Now, frequently, we're running into the situation that the standard
Java
compiler plugin kicks in instead of the aspectj-compiler. Of course,
then the build fails immediately.
In most of the cases, this happens on aspectj:test-compile
(instead of which we suddenly get compiler:testCompile)
Do you think this might be a bug in the current snapshot, or has
anyone
experienced similar behaviour on the release versions? Unfortionately
we have no way to try this out on a realistic setup (because of
"XhasMember") -- and a simple dummy project doesn't reproduce this.
Maybe there is a better place where we could ask such questions?
Any ideas?
and thanks for the hint with the aspecttools-jar version...
Hermann V.
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
