Hello,
I have a multi-module build that is essentially:
jars---a
b
c
Where jars is a directory that contains a parent/multimodule pom.xml that
builds a pom-type artifact called "jars-parent". a, b, and c are each
sub-directories within the jars directory with their own poms. a, b, and c,
all have jars-parent as their parent. They are referenced as modules in
jars-parent's pom.xml in the same order.
The problem arises in a situation when "c" depends on "a" for example. If I
build each of the submodules independently in the the order "a, b, c",
everything is fine. however, when I do a "mvn install" from the jars
directory, "a" and "b" build fine, but compilation of "c" fails - not an
artifact resolution problem, but a compilation problem. This is in spite of
the fact that "a" was built and installed to my local repo just fine.
The only unusual thing I am doing is that "a" doesn't actually compile
anything - it just packages some existing class files using the jar plugin.
(this is part of an ant conversion - don't get me started :,( )
I have had other multi-module build work just fine, but I am hoping somebody
can point out some potential gotchas that I am overlooking.
Thanks,
Shea.
--
View this message in context:
http://www.nabble.com/artifacts-build-fine-on-their-own-but-fail-in-multi-module-build-tp15863045s177p15863045.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]
