[ 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