Basically, I have a project and a Continuous Integration solution which I have no admin access to, that can’t reach out of our network. Consequently, I want to deploy all of the jars for the project to our central maven repository which the CI solution can reach. They are in my local repo but it’s a pretty complicated project. Can’t I just set a flag or something and deploy both a jar and what ever else I have in the local repo that the jar depends on?
OK, I’ve had an idea of my own since I first wrote this. What about this:
- Move my local maven repo off to a new name.
- Perform a build with -U flag so that a new repo is created with only the things I need for this project.
- Perform a merge from the newly created local repo to the remote repo.
What dborba said. I’d write a (bash/ruby) script to run the Maven Dependency Plugin, and then run deploy-file with the GAE attributes as reported by the Dependency Plugin. Assuming I had more than a few dependencies. Some repository managers (e.g. Nexus) are good at working out the GAE info.