As of svn 956915, rat plugin was added to all pom files, and I've added licenses to all required files. Log4j still has an issue in its rat config (output folder is causing the ant:check maven task to fail)
Scott On Tue, Jun 8, 2010 at 6:14 AM, Curt Arnold <[email protected]> wrote: > > On Jun 7, 2010, at 11:39 PM, Scott Deboy wrote: > > > I think we'd be ok either way..UnrecognizedElementHandler is in > component...and I could see someone needing that. > > > > I have one Chainsaw feature I've implemented that I don't know if I want > to commit (displaying the time deltas between events visually in the table) > so I think I'm pretty close to ready for a Chainsaw release...maybe one or > two little annoying things I may want to tackle before release, but I could > cut a release candidate today and be ok with it.. > > > > Scott > > > > UnrecognizedElementHandler is in 1.2.16. The copies in extras and > component were to support them working with earlier versions of log4j. > Likely we could make component depend on 1.2.16 and eliminate the possible > conflict, don'[t see a huge demand for component working with earlier > versions of log4j since it has been quiet for so long. > > Could you add the rat plugin and do a mvn rat:check to catch any missing > source file headers? > > How do you see a Chainsaw user getting its dependencies? If we could > assume that Maven is installed, then "mvn exec:java" would work (and it > should work even if we do more than that), could do something with Ant and > Ivy or we could include the other jars in with the release and provide .sh > and .bat files. > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
