Olaf Böde wrote: > > Hi Patrik, > > there is a simple 'workaround' that I always use. - I use separate > projects. > > 1. A project for oAW related sources. That contains my templates, knows > the oAW libraries in its classpath etc. > > 2. One or more java projects. They know all the generated and manually > written code. But they don't know anything about oAW libraries. - This way > there is no conflict with any config file (or commonly used lib in a wrong > version) in the classpath. > >
I understand. I use (develop) Sculptor and my templates are in another project (Sculptor). Yes I could create an additional project, but that feels like overkill. Thanks anyway. Olaf Böde wrote: > > > 2.a (not oAW related) In addition I use always separate test projects. > That automatically prevents conflicts between test and production config > files... > > I hope I got you point right. > > Regards, Olaf > I prefer to use the default structure in maven2, i.e. put test configuration in src/test/resources and use <scope>test</test> for dependencies only used when running test. Normally, this works fine. Thanks anyway. -- View this message in context: http://www.nabble.com/log4j.properties-tf3804666s17564.html#a10778478 Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
