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]
