You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ole Ersoy (JIRA)" <ji...@codehaus.org> on 2009/07/06 20:29:22 UTC
[jira] Created: (MECLIPSE-584) No eclipse classpath entries
generated for aspectj dependencies
No eclipse classpath entries generated for aspectj dependencies
---------------------------------------------------------------
Key: MECLIPSE-584
URL: http://jira.codehaus.org/browse/MECLIPSE-584
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path (.classpath)
Environment: Fedora 11
Sun Java
Reporter: Ole Ersoy
Priority: Minor
When I run eclipse:eclipse .classpath entries for the following elements don't get added:
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjrt</artifactId>
<version>1.5.4</version>
</dependency>
<dependency>
<groupId>org.aspectj</groupId>
<artifactId>aspectjweaver</artifactId>
<version>1.5.4</version>
</dependency>
The dependencies are in the repository and I can add them manually myself like this:
<classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/>
<classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/>
I really thought this had to be a user error, so I tried taking some dependency declarations that work, and just changing the body values to correspond with the bodies of the aspectj dependency declarations. It still does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-584) No eclipse classpath entries
generated for aspectj dependencies
Posted by "Paul Benedict (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194722#action_194722 ]
Paul Benedict commented on MECLIPSE-584:
----------------------------------------
Agreed, this is an annoying bug. I upgrade my AspectJ libraries faster than Eclipse.
> No eclipse classpath entries generated for aspectj dependencies
> ---------------------------------------------------------------
>
> Key: MECLIPSE-584
> URL: http://jira.codehaus.org/browse/MECLIPSE-584
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: AJDT support
> Environment: Fedora 11
> Sun Java
> Reporter: Ole Ersoy
> Priority: Minor
> Fix For: 2.8
>
>
> When I run eclipse:eclipse .classpath entries for the following elements don't get added:
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> <version>1.5.4</version>
> </dependency>
>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjweaver</artifactId>
> <version>1.5.4</version>
> </dependency>
> The dependencies are in the repository and I can add them manually myself like this:
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/>
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/>
> I really thought this had to be a user error, so I tried taking some dependency declarations that work, and just changing the body values to correspond with the bodies of the aspectj dependency declarations. It still does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-584) No eclipse classpath entries
generated for aspectj dependencies
Posted by "nicolas de loof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nicolas de loof closed MECLIPSE-584.
------------------------------------
Resolution: Fixed
fixed by MECLIPSE-594
> No eclipse classpath entries generated for aspectj dependencies
> ---------------------------------------------------------------
>
> Key: MECLIPSE-584
> URL: http://jira.codehaus.org/browse/MECLIPSE-584
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: AJDT support
> Environment: Fedora 11
> Sun Java
> Reporter: Ole Ersoy
> Priority: Minor
> Fix For: 2.8
>
>
> When I run eclipse:eclipse .classpath entries for the following elements don't get added:
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> <version>1.5.4</version>
> </dependency>
>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjweaver</artifactId>
> <version>1.5.4</version>
> </dependency>
> The dependencies are in the repository and I can add them manually myself like this:
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/>
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/>
> I really thought this had to be a user error, so I tried taking some dependency declarations that work, and just changing the body values to correspond with the bodies of the aspectj dependency declarations. It still does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-584) No eclipse classpath entries
generated for aspectj dependencies
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-584:
-------------------------------------
Fix Version/s: 2.8
Component/s: (was: Core : Dependencies resolution and build path (.classpath))
AJDT support
> No eclipse classpath entries generated for aspectj dependencies
> ---------------------------------------------------------------
>
> Key: MECLIPSE-584
> URL: http://jira.codehaus.org/browse/MECLIPSE-584
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: AJDT support
> Environment: Fedora 11
> Sun Java
> Reporter: Ole Ersoy
> Priority: Minor
> Fix For: 2.8
>
>
> When I run eclipse:eclipse .classpath entries for the following elements don't get added:
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> <version>1.5.4</version>
> </dependency>
>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjweaver</artifactId>
> <version>1.5.4</version>
> </dependency>
> The dependencies are in the repository and I can add them manually myself like this:
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/>
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/>
> I really thought this had to be a user error, so I tried taking some dependency declarations that work, and just changing the body values to correspond with the bodies of the aspectj dependency declarations. It still does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-584) No eclipse classpath entries
generated for aspectj dependencies
Posted by "Joost den Boer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185468#action_185468 ]
Joost den Boer commented on MECLIPSE-584:
-----------------------------------------
This is caused by these lines in EclipseClasspathWriter:
{code:java}
// Skip aspectj libraries since they are in the container.
if ( ( config.getAjdtVersion() != 0 ) && dep.getArtifactId().toLowerCase().indexOf( "aspectj" ) >= 0 )
{
return;
}
{code}
It is very annoying it's not possible to add aspectj libraries to the classpath. Somehow my JUnit-Spring tests work fine with Maven but in Rad they don't run because the aspectj-weaver classes are not found. And these lines prevent my from adding the required dependencies to the Eclipse classpath.
Any ideas how to workaround this? What do they mean by "Skip aspectj libraries since they are in the container." ? In which container? We're using the WebSphere JRE and WebSphere Application Service libraries for our projects, but these don't have aspectj in them.
> No eclipse classpath entries generated for aspectj dependencies
> ---------------------------------------------------------------
>
> Key: MECLIPSE-584
> URL: http://jira.codehaus.org/browse/MECLIPSE-584
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Environment: Fedora 11
> Sun Java
> Reporter: Ole Ersoy
> Priority: Minor
>
> When I run eclipse:eclipse .classpath entries for the following elements don't get added:
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> <version>1.5.4</version>
> </dependency>
>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjweaver</artifactId>
> <version>1.5.4</version>
> </dependency>
> The dependencies are in the repository and I can add them manually myself like this:
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/>
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/>
> I really thought this had to be a user error, so I tried taking some dependency declarations that work, and just changing the body values to correspond with the bodies of the aspectj dependency declarations. It still does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-584) No eclipse classpath entries
generated for aspectj dependencies
Posted by "Krzysztof Krason (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184236#action_184236 ]
Krzysztof Krason commented on MECLIPSE-584:
-------------------------------------------
Same problem here, maven 2.1.0, aspectj 1.6.1
(I've had this problem since almost a year, when I started using aspectj and maven)
> No eclipse classpath entries generated for aspectj dependencies
> ---------------------------------------------------------------
>
> Key: MECLIPSE-584
> URL: http://jira.codehaus.org/browse/MECLIPSE-584
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Environment: Fedora 11
> Sun Java
> Reporter: Ole Ersoy
> Priority: Minor
>
> When I run eclipse:eclipse .classpath entries for the following elements don't get added:
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> <version>1.5.4</version>
> </dependency>
>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjweaver</artifactId>
> <version>1.5.4</version>
> </dependency>
> The dependencies are in the repository and I can add them manually myself like this:
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/>
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/>
> I really thought this had to be a user error, so I tried taking some dependency declarations that work, and just changing the body values to correspond with the bodies of the aspectj dependency declarations. It still does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-584) No eclipse classpath entries
generated for aspectj dependencies
Posted by "Nicolas Toublanc (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182874#action_182874 ]
Nicolas Toublanc commented on MECLIPSE-584:
-------------------------------------------
I have the same issue using maven 2.2 and eclipse-maven-plugin 2.6 or 2.7 (no problem with 2.5).
My aspectj dependency is 1.6.2
> No eclipse classpath entries generated for aspectj dependencies
> ---------------------------------------------------------------
>
> Key: MECLIPSE-584
> URL: http://jira.codehaus.org/browse/MECLIPSE-584
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Environment: Fedora 11
> Sun Java
> Reporter: Ole Ersoy
> Priority: Minor
>
> When I run eclipse:eclipse .classpath entries for the following elements don't get added:
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> <version>1.5.4</version>
> </dependency>
>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjweaver</artifactId>
> <version>1.5.4</version>
> </dependency>
> The dependencies are in the repository and I can add them manually myself like this:
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/>
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/>
> I really thought this had to be a user error, so I tried taking some dependency declarations that work, and just changing the body values to correspond with the bodies of the aspectj dependency declarations. It still does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-584) No eclipse classpath entries
generated for aspectj dependencies
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185472#action_185472 ]
Arnaud Heritier commented on MECLIPSE-584:
------------------------------------------
You can set <ajdtVersion>none</ajdtVersion> in your eclipse plugin config. By default the plugin supposes you have, and you are using AJDT plugin if you aspectj dependencies in your project.
I'll change this behavior to set ajdtVersion to none by default in 2.8
> No eclipse classpath entries generated for aspectj dependencies
> ---------------------------------------------------------------
>
> Key: MECLIPSE-584
> URL: http://jira.codehaus.org/browse/MECLIPSE-584
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Environment: Fedora 11
> Sun Java
> Reporter: Ole Ersoy
> Priority: Minor
>
> When I run eclipse:eclipse .classpath entries for the following elements don't get added:
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> <version>1.5.4</version>
> </dependency>
>
> <dependency>
> <groupId>org.aspectj</groupId>
> <artifactId>aspectjweaver</artifactId>
> <version>1.5.4</version>
> </dependency>
> The dependencies are in the repository and I can add them manually myself like this:
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjrt/1.5.4/aspectjrt-1.5.4.jar"/>
> <classpathentry kind="var" path="M2_REPO/org/aspectj/aspectjweaver/1.5.4/aspectjweaver-1.5.4.jar"/>
> I really thought this had to be a user error, so I tried taking some dependency declarations that work, and just changing the body values to correspond with the bodies of the aspectj dependency declarations. It still does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira