> However, is there a setting that says, don't expect Child1 in the > repository, just use the target class files since its a sibling child? The
No. > various IDE reasons, I would like to have Child1 target classes directly > accessed whenever I run a maven command in Child2. You can't. > Is there a switch that says when I issue a mvn command in Child2 to use the > target classes in Child1 instead of forcing Child1 to have to be in the > repository? No. Unless you are building from the parent, as you already stated. > Is there another way to handle this that is a better pattern or approach? The reactor plugin may be helpful, but I'm honestly unsure as I've never formally used it as yet. http://stackoverflow.com/questions/2050241/what-is-the-maven-reactor Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
