I'm trying to automate the following case by writing a maven plugin
which can expose a directory as a repository for other modules.
The use case:
My module A requires as a dependency a module B in a remote (http)
location. That module B has a maven structure, but only the source part
is available (thus the src directory and the pom.xml, but the target
directory is missing).
Thus, before I "mvn install" in A, I always have to:
1. download code from B to a local directory
2. run "mvn install" in B to compile everything and publish B artefacts
to the local repository
I would like to write a module that can download the source of B from a
remote http location, run "mvn install" on it locally and publish the
generated artefacts into the local repository. How would I go about
that? Is there an easy way I'm overlooking?
Many thanks in advance!