David Ojeda wrote:
So my question is: what can I do if I want to deliver give the source code and the dependencies jars?Here are some of my ideas: - Maintain a private repository with dependencies and use the deploy:deploy- file goal to add dependencies to it.Problem: in the love/hate relationship of client/developer companies, I think that the clients might argue that they do not want to depend on the developer company repository. Could be a repository in the client company. - Deliver all jars and scripts to install them in the local repository. Seems very 'hackish' and not so 'mavenish'.What is your experience with this situation?
Keep it simple: Deliver a copy of the local repository (stored in ~/.m2/repository) along with the source code. Job done.
In the worst case scenario where dependencies are missing, you just drop the saved repository into ~/.m2/repository, and build.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
