Hi, Interesting... maybe there is a difference in the maven (plugin) levels we are using (or the way we run mvn)...
looking at the .classpath file that gets generated by mvn -Peclipse eclipse:eclipse I see entries such as (in the case of DAS): <classpathentry kind="var" path="M2_REPO/org/apache/tuscany/sdo/tuscany-sdo-impl/1.0-incubator-SNAPSHOT/tuscany- sdo-impl-1.0-incubator-SNAPSHOT.jar"/> So for me the dependency is pointing to the installed jar in my repository, not to other projects in my workspace. I can change sdo-impl and install it, then my changes are picked up... but this means I step out of eclipse (since I've not really had much joy with the m2eclipse plugin)... Perhaps it is because you are running mvn -Peclipse profile <- presume profile is one of SCA/SDO etc... I'll give this a bash - thanks Dan On 10/01/07, Francesco Furfari <[EMAIL PROTECTED]> wrote:
Hi, I'm not sure that Dan's solution is the best one, I mean running mvn -Peclipse profile should build eclipse projects already linked between them. If you open the "Configure build path ..." of the core project you should find all the dependencies as connected project in the Projects Tab. I think Eclipse uses that configuration to synchronize the sources with the running task. But running task the JVM uses in the class path the mvn repository. So if you just compile the sources without install the artifact in the mvn repository then the sources will be out of sync. Note that if you change the sources and save them while the task is running, for simple changes the Debugger reloads the compiled class so that you can see soon the changes. Stopping the task the code will be of course out of sync. ( a trick is to press the space bar and save the source to force the reloading at the next execution) So I think one solution could be: remind of runnning "mvn install" each time you have to debug something. I haven't installed the M2 plugin yet, but I guess it helps to compile and install directly the code. let me know if this was the problem. francesco Dan Murphy wrote: > Hi Jean-Sebastien, > > When I have used mvn -Peclipse eclipse:eclipse any dependencies that exist > in a project are located in your maven repository, not other projects in > eclipse. You can rectify this by editing the build path and removing the > library and replacing it with a project dependency... I guess the argument > goes that mvn doesn't know what else is in your workspace so can't place > dependencies on other projects... > Regards, > Dan > > On 10/01/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> 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 >> >> -- >> Jean-Sebastien >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
