I don't see anything odd about what you want.
We have an application made up of 60+ modules that are coded
independently and have inter-dependencies all over the place.
Do you have a Maven repo such as Nexus? If not that is a starting move.
Do you use SNAPSHOTS? They will do what you want.
Ron
On 15/11/2012 5:09 AM, mar wrote:
Hello,
I am trying to achieve a structure where a project is wrapping and depending
on another project.
The sub-project is a library and should be indifferent about its outer
project, but should be built and installed (to a local repo) everytime the
outer project it built, preferably only when
1. the inner project artifact isn't available, or;
2. the inner project has been updated.
Both the projects are hosted with git in their own repo, the wrapped project
being a git submodule of the larger project. What I'm trying to achieve is a
way to pull the larger project and have a buildable artifact without loose
dependencies, while at the same time being able to work on both projects at
the same time.
This is the disk structure of my project:
Am I doing something weird here?
--
View this message in context:
http://maven.40175.n5.nabble.com/Compile-and-install-sub-project-on-build-tp5731080.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
