Thatś not the way I meant it... Sorry if it looked that way! When I have a WAR-project, I normally create 2 modules: 1 with the java-code (package: JAR) and 1 with the other WAR-stuff (JSP, CSS, etc - package: WAR).
That way, I can use the code inside the JAR as a normal dependency in any and all tests I have. Hope this cleared it up a bit. :-) On Wednesday 07 October 2009 16:41, Chris Bredesen wrote: > Why stop there? I'll just not write ANY code. Stress-free life! :) :) > > On 10/07/2009 10:13 AM, Roland Asmann wrote: > > 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] > > --------------------------------------------------------------------- > 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]
