FYI - I get the same main error trying to run the application in the dev build. When I delete the dependency, the main project builds though - so that is fixed. --Duncan
-----Original Message----- From: McNaught, Duncan [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 3:53 PM To: [email protected] Subject: RE: [m2eclipse-user] Matching dependencies references as projects automatically? Close/Open project doesn't help - I get the Error: Project Solar Client is missing required Java project: 'DependantProjectName' It doesn't get added back as a Maven2 dependency. -----Original Message----- From: Eugene Kuleshov [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 10:28 AM To: [email protected] Subject: Re: [m2eclipse-user] Matching dependencies references as projects automatically? That could be a bug and it might be fixed in the dev build. Also note that to refresh inter-project dependencies you can also try to close/open projects. Project model cache is flushed on closing and rebuilt on opening. regards, Eugene McNaught, Duncan wrote: > Here are the problems we have with it: > > When running the Java Program through Eclipse, the classpath is used > from the main project for both the main project and the dependent > project (which has it's own dependencies, hence should have it's own > classpath) > > Also - when I tried to revert to having the dependency resolved from the > local repository by deleting the project dependency, it didn't get added > back to the dependencies as a jar, just disappeared from the > dependencies, even though it is in the pom. Clean, and deleting the > project and creating it again didn't help. > > Thanks > --Duncan > > -----Original Message----- > From: Eugene Kuleshov [mailto:[EMAIL PROTECTED] > Sent: Friday, March 23, 2007 10:31 AM > To: [email protected] > Subject: Re: [m2eclipse-user] Matching dependencies references as > projects automatically? > > > Would you please explain what issues you have with dependencies resolved > > from the project workspace? > > regards, > Eugene > > > [EMAIL PROTECTED] wrote: > >> Funny I just posted a question about this myself. Supposedly this is a >> > > >> new "feature" in the 0.0.10 plugin. I'm trying myself to figure out >> how to get around it and why this would even be considered a feature. >> At a minimum this should be optional to do this or not. This one thing >> > > >> alone is stopping me from using the new version and I had to revert >> back to 0.0.9. >> >> --Rudy >> >> *From:* McNaught, Duncan [mailto:[EMAIL PROTECTED] >> *Sent:* Friday, March 23, 2007 11:49 AM >> *To:* [email protected] >> *Subject:* [m2eclipse-user] Matching dependencies references as >> projects automatically? >> >> Here is a description of the problem: The Maven plugin seems to be >> looking through my other Eclipse projects for projects that match the >> Maven2 Dependencies. If it finds matches it creates a link to the >> project rather than using the jar file deployed to our central maven >> repository, and then this doesn't work. >> >> Has anyone got a workaround for this problem? >> >> Thanks >> >> --Duncan >> >> Intuit Eclipse SCM >> >> 303 938 8801x1139 >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
