Question

Is there way to optionally compile dependency from source (svn) instead of using the remote jar?

Background:
I have a very very large j2ee project and we do not want the developer to have to download the entire project on to there system. Specially under a IDE where 20+ project can cause performance problem when compiling… debugging… eclipse crash causing weird phantom dependency problem… etc.

So we are setting up maven to download all dependency from a private repository, which works great. But I still want to be able to work on the dependency that it is downloading.

my solution:
My solution to this at the moment is the following…

1. download module I want to work on from svn
2. work on code
3. mvn install to local repository
4. create ear package
5. deploy and test

problems with my solution:

If I’m done with the development of the specific module, I am not sure how to tell maven to start downloading from remote repository again. Do I just uninstall and let it download next time it need to sync up?

Is there other solution to this?

Thanks!!!

Answer 1

So we are setting up maven to download all dependency from a private repository, which works great. But I still want to be able to work on the dependency that it is downloading.

Whether you’re using eclipse:eclipse or m2eclipse, you can configure projects to use “workspace resolution” (resolve dependencies from the workspace) or binary dependencies. In other words, it just supports your scenario.