In data lunedì 15 ottobre 2012 14:20:52, John Patrick ha scritto: > If this was me I would create a new pom, which would be the parent for > the 3 libraries, I would then also build at that level. > > e.g. > ~/mavenprojects/pom.xml (packaging pom) > ~/mavenprojects/myLib1/pom.xml (packaging jar) > ~/mavenprojects/myLib2/pom.xml (packaging jar) > ~/mavenprojects/myLib3/pom.xml (packaging jar) > > Basically that is how every project I've worked on works. You have to > define the parent and relative Path correctly in the lib projects, and > add modules into the parent pom.
The problem with this is that I also need to build standalone jars of myLib2 and myLib3, and they need myLib1 themselves. Their code refers to classes in myLib1 and myLib3 code defers also to classes in myLib2. myLib2 and myLib3 do not even compile if they don't have myLib1/myLib2 listed as dependency in their pom file. But if I list them as dependecies, those are expected to be found in a repository or manually installed. Otherwise if I list them as modules, I'm forced to packaging="pom", so no standalone jars... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
