Mark, What Eclipse version you are using?
Also, when you don't see dependencies resolved, you can open the project properties and see if Maven Dependencies container is in the buildpath and if it have any jars or projects resolved. There is a bug in Project Explorer in Eclipse 3.3. We have tried to work around it, but maybe you are hitting some corner case we haven't covered.
regards, Eugene Mark Hewett wrote:
When I upgrade from 0.0.11 to 0.0.12, dependencies where the project is in my workspace (and in my local repository) are not being added to the Maven Dependencies classpath container. If I close the project containing the artifact I am depending on then the repository version of the JAR is added to the classpath. I tried messing with the Enable Workspace Resolution option, but that doesn't seem to do anything at all. The only message I am getting (with debug logging enabled) related to the dependency is the following: 11/12/07 11:31:43 AM CST: com.redacted:redacted:jar:1.0-SNAPSHOT in Eclipse Workspace C:\workspaces\redacted\redacted\pom.xml So it seems like it should be adding a project dependency to the classpath container, but no such dependency is being added. If I roll back to 0.0.11 then I get the project dependency in the classpath container as expected. Unfortunately, I tried to recreate this with some test projects and everything seems to work as expected, so this may be environmental. At this point I'm just wondering if anyone has seen anything similar and found a way to get things working correctly, or has any suggestions for additional steps I can take to try and locate the problem? Thanks, Mark
--------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
