I am exploring the possibility of shipping a maven repo as part of a product. The idea is that instead of simply throwing all jars used by my product into a lib directory, these jars would be placed in a mini maven repo that would be shipped with the product. In addition, I would like to ship my demos as maven projects that would use the mini maven repo that ships with the product. This would make if very easy for users to create Eclipse projects for each demo and would allow them to easily debug the demos.
The one requirement for this mini maven repo would be that a user of this repo could use it completely in offline mode. In other words, certain customers have requirements which forbid any network connectivity to run demos and to use the product. This means that the maven repo must contain all artifacts such that a user can run "mvn install" and "mvn eclipse:eclipse" without any network access. Are there any roadblocks to shipping a maven repo with all the artifacts to do this? Are there specific plugins required to run these basic tasks whose licensing would forbid me from shipping them with my product. Regards, Seumas Soltysik
