Does anybody have any experience switching between project dependencies and jar dependencies?
I assume that if you are working on multiple modules at the same time the project dependencies would be necessary, but then when you are working on 1 specific module that may use an older version (non trunk) or another module, then jar dependencies would be needed. Do you have to keep using mvn eclipse:eclipse all the time? -----Original Message----- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 16, 2006 5:50 PM To: Maven Users List Subject: Re: [m2] eclipse:eclipse and eclipse 3.2 projects within a project support. On 8/17/06, Max Cooper <[EMAIL PROTECTED]> wrote: > I, too, have been anxiously awaiting hierarchical project support in > Eclipse. And I thought that it was going to be available in Eclipse 3.2. > > But this feature was omitted from the Eclipse 3.2 release. The feature > is not available yet. You can do it, I was able to manually create another project pointing to one that was already in the workspace and a subdirectory of that project. i.e project_root/ - module1 - module2 I was able to have in Eclipse a project for "project_root" as well as create one manually for module1 and module2 so that they appear in the project list. But I can't figure out what Eclipse does under the covers for that, there are no docs that I could find in the help or googling, and I can't see in the source code of the eclipse:eclipse plugin whether it is attempting to do this. --------------------------------------------------------------------- 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]
