Previous attachment in diff format

This has been updated for maven-eclipse-plugin 2.5.1 and also ajdt version 1.5.3. I have also included tests and updates to the site build to show how to use it.

Hopefully one of the commiters will be willing to look at this and incorporate it.

Look at the 122kb maven-eclipse-plugin.zip.

Fixed and snapshot 2.6-20080902.232029-1 deployed. If you can test it ....

Tested. It works as expected. Thanks.

Is the site staged anywhere (to be able to see documentation of new parameters)

It will be in few hours here :
http://maven.apache.org/plugins/maven-eclipse-plugin-2.6-SNAPSHOT/

I can understand the wish for a AJDT-Plugin support, but I cannot understand
why this must have such an impact on projects that do not use that plugin.

As we do not use that plugin we now are having the problem that our projects
do not compile for the reason of the missing jars :-/

In my eyes this AJDT-Plugin Feature MUST be implemented in a more generic way.
Read the eclipse configurations whether that plugin is installed or something else.
But do not force other Projects to use the AJDT Plugin, just because the are workin
with AOP!!!!

Please open an new issue if this one creates a problem for you. A 2.7 is already on rails.

Alexander, In the configuration of the eclipse plugin add <ajdtVersion>none</ajdtVersion>. This should fix the problem.

There is hidden documentation here http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html that describes how to use the ajdt plugin.

I agree with Alexander, and I've created a new issue: http://jira.codehaus.org/browse/MECLIPSE-547

According to the comments on MECLIPSE-270, this jira task replaces/duplicates that task. MECLIPSE-270 is about adding attributes to classpathentries in .classpath.

Can someone please elaborate how this can be accomplished in the pom.xml? This feature lacks documentation on the project website.

Regards

The documentation about ajdt is here : http://maven.apache.org/plugins/maven-eclipse-plugin/examples/ajdt-projects.html
You can find several exemples here : http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/test/resources/projects/
If some docs are missing, do not hesitate to open an issue. We'll try to improve it.
We know there are many lacks in it.

Arnaud: thanks for the link.

After plundering around, I found that adding wtp version 2.0 to the pom automatically added the required attributes to the classpathentries like this:

<classpathentry kind="var" path="M2_REPO/log4j/log4j/1.2.15/log4j-1.2.15.jar" sourcepath="M2_REPO/log4j/log4j/1.2.15/log4j-1.2.15-sources.jar">
<attributes>
<attribute value="/WEB-INF/lib" name="org.eclipse.jst.component.dependency"/>
</attributes>
</classpathentry>

A nice feature was that the attribute was only added if the maven dependency scope was compile or runtime. Small question though: If the scope is provided, the maven eclipse plugin doesn't add any attribute to the corresponding classpathentry. The wtp plugin for eclipse seems to support the following attribute for entries that are not to be deployed:

"org.eclipse.jst.component.nondependency"

Maybe you should add this for scope provided? Just a thought..

Thanks again!