Hi, I just skimmed this so sorry if someone may have answered your original question.
If you run mvn eclipse:clean eclipse:eclipse, it will restore the Maven project to it's original pre-eclipse project state, and then recreate the eclipse project files. This guarantees that the files are up to date. If you do the same on a parent project, it cleans and updates all the child projects. Then if you run mvn clean install on the parent it will update the entire build. You now have to F5 each project to make sure it sees the latest recompiled and deployed dependencies in the maven repository. With Eclipse 3.2 some test files occasionally pretend that they don't see the dependencies after running the eclipse plugin. Then when I run the test in eclipse, the dependencies are resolved. Cheers, - Ole --- Dan Murphy <[EMAIL PROTECTED]> wrote: > Hi, > I think the cause of the problem is both Sebastien > and I are going into > specific component / sub components of Tuscany and > running mvn -Peclipse > from there.... from the sounds of it if you run it > at the top level then you > should get all the subs build such that any > dependecies are resolved to > other compoenents in the same source hierarchy (as > opposed to the > repository). > Seems like this could be a good point to document in > the wiki, 'cos the last > time I read the docs it advised you to go into each > part seperatly and run > mvn -Peclipse > Regards, > Dan > > On 10/01/07, Rick <[EMAIL PROTECTED]> wrote: > > > > Sebastien, > > I don't quite get the issue you are seeing. I'll > just add what I've been > > doing: > > In top folder (java) run mvn -Pall,eclipse > eclipse:eclipse > > I'm still a hold out I guess in that I like > building the whole tuscany > > package. > > For debugging, I add source of projects I know I > need. So far this has > > been > > working for me. Cheers. > > > > Jean-Sebastien Delfino wrote: > > > I'm trying to do some simple refactoring of the > spec APIs to fix JIRA > > > 909, and running into the following issues: > > > > > > I am using Eclipse and running mvn -Peclipse > eclipse:eclipse in the spec > > > and sca folders to generate Eclipse projects. If > I remember correctly > > > this used to generate correct Eclipse project > dependencies, for example > > > the core project had a dependency on the sca-api > project. Now project > > > core depends on the sca-api-r0.95 jar instead. > Code changes that I make > > > in the sca-api project are not seen by core. > Refactoring methods in > > > sca-api does not adjust any of the code in core. > The jars do not have > > > associated source code so this makes debugging > tough (and there's way > > > too many projects for me to associate the source > code to each jar > > > manually). > > > > > > I have probably forgotten to do something or not > run mvn -Peclipse > > > correctly. Could somebody point me to the magic > Maven commands that will > > > generate a usable Eclipse workspace? > > > > > > Thanks > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
