Personally, I don't put ANY code in the WAR. That will definitely solve your problem! :-)
On Wednesday 07 October 2009 16:03, Chris Bredesen wrote: > All, > > I have split my unit tests out into a separate project which will > eventually become a module (not there yet). I've got it mostly sorted > but I'm getting compile errors on classes that are part of the main > project which uses war packaging. > > Maven doesn't seem to add the WAR's code into the test module's test > classpath correctly. Is this a known issue? Any idea how to get around > it? Maven is definitely finding the artifact in my repository; it's > just not contributing the WAR's code (I think). > > Any help is appreciated. > > -Chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [email protected] Web: www.cfc.at --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
