If you run 'mvn eclipse:eclipse' from the top level of your project (as
opposed to running it individually for each module), the maven eclipse
plugin will create "project dependencies" rather than dependencies on
the jar files in the repository.
I would start by checking to see if you currently have "project
dependencies" or if you have dependencies on jars.
-Max
Douglas Ferguson wrote:
When using eclipse for multi-module projects:
If I am working on 2 modules at the same time, is there anyway to have
eclipse resolve dependencies without having to install them to the maven
repository?
When using the m2 plugin, is there an easy way to add a local
dependency/parent/or submodule?
When using the m2 plugin, do I have to configure all the goals I need to run
per module? Since the basedir has to be set it seems like you have to
configure all your modules and all the goals you want to run.
__________________________________________
Douglas W. Ferguson
EPSIIA - Another Fiserv Connection
Development
Office Phone: 512-329-0081 ext. 3309
Dial Toll Free: 800-415-5946
Mobile Phone: 512-293-7279
Fax: 512-329-0086
[EMAIL PROTECTED]
www.epsiia.com <http://www.epsiia.com/>
__________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
