You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Andrew Eisenberg <an...@eisenberg.as> on 2009/04/05 18:33:53 UTC

Better AJDT support for maven generated eclipse projects

Hi all,

Some of you might be interested in some new features in AJDT that we
put in to help support maven users who are using the aspectj plugin
and the maven-eclipse-plugin.

1) The maven-eclipse-plugin would include the javabuilder in the
generated .project file.  This is usually fine, except that AJDT is
incompatible with the javabuilder.  It requires the ajbuilder instead.
 This was causing many problems for maven and ajdt users who had their
projects generated without the ajbuilder (or with *both* the
javabuilder and the ajbuilder).

Now, on import of an ajdt project, ajdt ensures that the builders are
properly installed (ie- if necessary, the javabuilder is removed and
the ajbuilder is added).

2) The maven-eclipse-plugin does not recognize jars that should be on
the aspect path (ie- aspect libraries).  Aspect libraries would have
to be added inside of eclipse after the project was imported (note
that m2eclipse already has support for this, but not everyone uses
m2eclipse).

So, now, the ajbuilder recognizes some builder arguments.  These
arguments can add jars to the aspect path.  Here is an example.  Let's
say that you want to add the spring aspects jar and the spring aop jar
to your aspect path, here is what you can add to your pom.xml (this
goes inside your maven-eclipse-plugin configuration section):

                                        <additionalBuildcommands>
                                                <buildCommand>

<name>org.eclipse.ajdt.core.ajbuilder</name>
                                                        <arguments>

<aspectPath>org.springframework.aspects,org.springframework.aop</aspectPath>
                                                        </arguments>
                                                </buildCommand>
                                        </additionalBuildcommands>
                                        <additionalProjectnatures>

<projectnature>org.eclipse.ajdt.ui.ajnature</projectnature>
                                        </additionalProjectnatures>

Please let me know if this is useful for you and if you have any
questions/issues.

For more information, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=270554
https://bugs.eclipse.org/bugs/show_bug.cgi?id=270552

--andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Better AJDT support for maven generated eclipse projects

Posted by Andrew Eisenberg <an...@eisenberg.as>.
I can raise those bugs, but it is less important now that AJDT works
around it.  Some AJDT users required the functionality *now*, and it
was a relatively easy fix on our side, so we did it.

On Sun, Apr 5, 2009 at 3:17 PM, Barrie Treloar <ba...@gmail.com> wrote:
> On Mon, Apr 6, 2009 at 2:03 AM, Andrew Eisenberg <an...@eisenberg.as> wrote:
>> Hi all,
>>
>> Some of you might be interested in some new features in AJDT that we
>> put in to help support maven users who are using the aspectj plugin
>> and the maven-eclipse-plugin.
>
> Do you want to raise bugs (if they dont already exist) against
> maven-eclipse-plugin?
> While its handy for ajdt to work around these issues it probably
> better that m-e-p does the right thing.
> There are a number of test cases already for ajdt so it should be hard
> to fix support properly.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Better AJDT support for maven generated eclipse projects

Posted by Barrie Treloar <ba...@gmail.com>.
On Mon, Apr 6, 2009 at 2:03 AM, Andrew Eisenberg <an...@eisenberg.as> wrote:
> Hi all,
>
> Some of you might be interested in some new features in AJDT that we
> put in to help support maven users who are using the aspectj plugin
> and the maven-eclipse-plugin.

Do you want to raise bugs (if they dont already exist) against
maven-eclipse-plugin?
While its handy for ajdt to work around these issues it probably
better that m-e-p does the right thing.
There are a number of test cases already for ajdt so it should be hard
to fix support properly.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org