Jul 26th, 2010, 12:02 PM
1.1.0.M2 "dep add" on project already imported into Eclipse doesn't update build path
I downloaded 1.1.0.M2 and created a new project, setup persistence and then imported it into Eclipse. I added a dependency to an artifact that only exists in my local repository. For some reason, the project in Eclipse doesn't seem to pick it up even after refreshing, although the new dependency resolved successfully. I've attempted closing the project in Eclipse and even removing it from my workspace, both followed by running "perform eclipse" back in the stand alone roo shell or simply "perform command --mavenCommand dependency:resolve". Upon reopening or reimporting the project, the build path still wasn't updated to include the artifact I added a dependency for. If I look in my pom.xml, the dependency is indeed listed there.
Anybody else experience this?
In previous testing, I had a similar issue. If I first completed the persistence setup say using provider DATANUCLEUS, after performing various other commands, if I then reran the persistence setup and changed the provider to HIBERNATE, the build path in Eclipse still referenced Data Nucleus artifacts, even the Data Nucleus repository remained in my pom.xml.