Yes, that is definitely an option that I may need to pursue. It's unfortunate, though, since the way I have it set up *should* work. This just seems like a bug in the dependency plugin which it depends on source modules as opposed to the artifacts built in the repos...
Arnaud Bailly wrote: > > cdesaint <[EMAIL PROTECTED]> writes: > >> Hi All, >> >> I've got a couple of projects, 1 is a WAR project, another is a JAR >> project >> which needs to depend on the java classes in the WAR. Normally, you >> wouldn't do this, but in this case, the JAR project is for unit tests and >> wants to be able to instantiate the Actions in the WAR project. >> > > Couldn't you just split your war ? If you need to have a separate > artifact for unit testing, then go ahead, the code is telling you it > wants to be split. Modules are cheap in maven. > > HTH > -- > OQube < software engineering \ génie logiciel > > Arnaud Bailly, Dr. > \web> http://www.oqube.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Problem-compiling-project-with-WAR-dependency-tf4524072s177.html#a12909417 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
