How to diagnose false "unsatisfied dependency" messages?
So my build just started complaining of the lack of commons-io-1.2.jar, which is obviously not something we internally build. Furthermore, it IS available on our internal repository from which the script succesfully downloads other dependencies. Even further furthermore, I just hacked at .maven/repository and plopped commons-io-1.2.jar and it's .md5 into the right place and the script still complains of an unsatisfied dependency. Nuked .maven/cache just for fun and it seemed to make no difference. We have no explicit dependencies on commons-io, it appears to be something that one of the reporting plugins wants to use. Did nothing to the repository or cache prior to the problem cropping up, but I did nuke the entire source directory, as we were suspicious that there was some cruft lying around (and surviving "clean" calls) breaking other things. Apparently some of that cruft was duct-taping things together. Thoughts on how to diagnose what's really going on? TIA, Brian
RE: Support multiple child module pom's in the same directory?
So the current implementation requires that a child pom module MUST be in a file named pom.xml? Just trying to understand... And thank you very much for the quicky reply. Brian -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 06, 2007 12:40 PM To: Maven Users List Subject: Re: Support multiple child module pom's in the same directory? This is not possible. However, you can run "mvn -f siblingpom.xml" from the foo/bar directory and Maven will execute using that pom rather than the default pom.xml in the directory. Wayne On 6/6/07, Deacon, Brian <[EMAIL PROTECTED]> wrote: > Hi all, > > For reasons that are un-mavenish and evil and will eventually be > solved with a source code reorganization, I am stuck with having to > try to build two separate modules that sit in the same source tree. > What I'd like to do in the parent multi-module pom is this: > > > > foo/bar > > > foo/bar/SiblingPom.xml > > > > > But when I try to build this, it looks for > foo/bar/SiblingPom.xml/pom.xml > > I'm hoping this is just me not using the right syntax. Or is there a > workaround I need for this? > > This is 2.0.6, btw. > > TIA, > > Brian > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Support multiple child module pom's in the same directory?
Hi all, For reasons that are un-mavenish and evil and will eventually be solved with a source code reorganization, I am stuck with having to try to build two separate modules that sit in the same source tree. What I'd like to do in the parent multi-module pom is this: foo/bar foo/bar/SiblingPom.xml But when I try to build this, it looks for foo/bar/SiblingPom.xml/pom.xml I'm hoping this is just me not using the right syntax. Or is there a workaround I need for this? This is 2.0.6, btw. TIA, Brian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
