Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.6, 2.7
-
Fix Version/s: 2.8
-
Component/s: AJDT support
-
Labels:None
-
Number of attachments :
Description
It will be easier for our user if by default AJDT support is off.
Issue Links
| This issue supercedes: | ||||
| MECLIPSE-568 | Some compile dependencies are not added to .classpath since 2.6 |
|
|
|
| MECLIPSE-569 | eclipse:eclipse does not add all libraries to .classpath |
|
|
|
| MECLIPSE-558 | Ignoring listed AspectJ dependencies |
|
|
|
| MECLIPSE-584 | No eclipse classpath entries generated for aspectj dependencies |
|
|
|
Wow this bug is a strange one... I can't imagine why it would be a good idea to exclude all dependencies with aspectj in the name. Caused me four hours of grief... Please fix!
To anyone who wants to know how I worked around this issue, add the following to your pom, aspectj dependencies will be included after making this change.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<ajdtVersion>none</ajdtVersion>
</configuration>
</groupId>
</plugin>