Hi Karsten, Yes, I would love to see the log4j configuration component that you put in your workflow! Logging is so frustrating otherwise. Is this something that you created? Please let me know if/when you share it.
Thanks! --Polly On Sat, Jun 27, 2009 at 7:42 AM, Karsten Thoms <karsten.th...@itemis.de>wrote: > H Polly, > > Hmm, I have no idea why these messages suddenly appear. I do not think that > it has something to do with the oAW M2 plugin. On my side I do not get the > debug messages, must be a matter of log4j configuration taken from the > classpath. I once experienced that log4j.properties wins before log4j.xml. > In my project we have added a log4j configuration component to the workflow. > This way we can control logging. I think this could be a useful standard > component that I could add. > > ~Karsten > > Am 26.06.2009 um 23:38 schrieb Polly C. Chang: > > Hi Karsten, > > I have the same setup for the Surefire plugin, and that works fine. The > problems is that before we get to the unit tests, when Maven is generating > sources, there is tons of debug output from oAW and Hybridlabs Beautifier. > I put a log4j.xml file in src/main/resources and that still doesn't turn off > the oAW messages (though I am able to turn off the Hybridlabs messages). > > Are you able to turn off all the "Opening file", "Skipping file" kind of > debug messages? > > [org.openarchitectureware.xpand2.output.FileHandleImpl] : Opening file : > C:\projects\runtime\com.foo.model\src\main\java\com\foo\model\package.html > [org.openarchitectureware.xpand2.output.FileHandleImpl] : Skipping file : > C:\projects\runtime\com.foo.model\src\main\java\com\foo\model\package.html > cause it exists already > > As you can imagine, with a big domain model, these messages just scroll on > and on and really seem to slow things down. :( > > btw, I am using Maven 2.1.0 and JDK 1.6_13. > > Thanks! > --Polly > > > On Fri, Jun 26, 2009 at 1:51 AM, Karsten Thoms <karsten.th...@itemis.de>wrote: > >> Hi Polly, >> when looking at the sources I recognized that it might be no issue of the >> Fornax Maven plugin. Debug output has changed there, but just regarding the >> debug output that the plugin does. This is now I mean correctly directed to >> the Plugin's context logger, and these debug messages are activated when >> running mvn -X install. >> I saw that Sculptor overrides the log4j configuration for Surefire in >> their library example project like this: >> >> <plugin> >> <artifactId>maven-surefire-plugin</artifactId> >> <version>2.3</version> >> <configuration> >> <skip>false</skip> >> <forkMode>pertest</forkMode> >> <!-- <forkMode>once</forkMode> --> >> <argLine>-Xms32m -Xmx1024m -Dlog4j.configuration=log4j-test.properties</ >> argLine> >> <excludes> >> <exclude>**/IsolatedDatabaseTestCase.java</exclude> >> </excludes> >> </configuration> >> </plugin> >> >> Could you check if this would work for you, too? >> >> Best wishes, >> ~Karsten >> >> Am 25.06.2009 um 16:43 schrieb Polly C. Chang: >> >> Thanks! >> >> --Polly >> >> >> On Thu, Jun 25, 2009 at 2:21 AM, Karsten Thoms <th...@itemis.de> wrote: >> >>> Hi Polly, >>> >>> logging has been changed to Commons Logging. I will change this back next >>> week, maybe I can already deploy a snapshot tomorrow. >>> Opened Bug: https://fornax.itemis.de/jira/browse/TOM-26 >>> >>> ~Karsten >>> >>> >>> ----- Original Message ----- >>> From: "Polly C. Chang" <polly.c.ch...@gmail.com> >>> To: fornax-developer@lists.sourceforge.net >>> Sent: Thursday, June 25, 2009 3:09:08 AM (GMT+0100) Europe/Berlin >>> Subject: Re: [Fornax-developer] logging with fornax-oaw-m2-plugin >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Fornax-developer mailing list >>> Fornax-developer@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/fornax-developer >>> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Fornax-developer mailing list >> Fornax-developer@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/fornax-developer >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Fornax-developer mailing list >> Fornax-developer@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/fornax-developer >> >> > > ------------------------------------------------------------------------------ > _______________________________________________ > Fornax-developer mailing list > Fornax-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fornax-developer > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Fornax-developer mailing list > Fornax-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fornax-developer > >
------------------------------------------------------------------------------
_______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
