maven properties are not resolved in .classpath, a bug?

95 views
Skip to first unread message

KangBerlin

unread,
Sep 18, 2012, 11:14:27 AM9/18/12
to ecli...@googlegroups.com
1)  i see my version properties are copied in .classpath ,

2)  some artifactId can not be properly resolved , for example: 

<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-web-6.0</artifactId>
<version>2.0.0.Final</version>
<type>pom</type>
<scope>test</scope>

.classpath :
/.m2/repository/org/jboss/spec/jboss-javaee-web-6/0/2.0.0.Final/jboss-javaee-web-6.0-2.0.0.Final.jar' 


Carlos Torres

unread,
Sep 18, 2012, 11:22:08 AM9/18/12
to ecli...@googlegroups.com

I've seen this happen to me before.  But I doubt it's an eclim issue, I bet eclipse is having trouble too.  I find :ProjectRefresh usually fixes that for me, other wise
mvn eclipse:clean eclipse:eclipse

Note: this removes your .settings dir too.
Then another project refresh. 

--
You received this message because you are subscribed to the Google Groups "eclim-dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/eclim-dev/-/Gp9o3I8cpqwJ.
To post to this group, send email to ecli...@googlegroups.com.
To unsubscribe from this group, send email to eclim-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/eclim-dev?hl=en.

KangBerlin

unread,
Sep 18, 2012, 11:59:17 AM9/18/12
to ecli...@googlegroups.com
I just removed the root Maven Project from Eclim workspace ( my project is multi-module) and then :ProjectRefresh for each module-project,  it works !!

Thank you very much for your help !
Reply all
Reply to author
Forward
0 new messages