There is one thing I haven't seen mentioned in this thread yet that I wasn't going to offer up but after seeing this comment, perhaps I should...
<quote> > namely the maintenance effort to keep an up to date pom.xml (or > project.xml, which may be the more standard name IIRC, but it doesn't > matter much). </quote> At first pass reading this I thought "you're right, the maven project file name doesn't matter much." However, the mroe I think about it may be beneficial to point out that I believe I hear Curt discussing usage of Maven2 while others have shared anecdotes and experiences from past usage of Maven1 (M2 standardizes on "pom.xml" while M1 primarily used "project.xml"). I suggest a look at the Maven2 "for maven1 users" page for a discussion of what has changed (lots!) and why in the Maven project. http://maven.apache.org/maven1.html Just two-cents from a list lurker and log4j user, Scott Heaberlin On 12/16/05, Yoav Shapira <[EMAIL PROTECTED]> wrote: > Hi, > My take on it is same as before: it's a nice tool, has some cool > features. But it's only worth pursuing if the benefits outweigh the > costs, namely the maintenance effort to keep an up to date pom.xml (or > project.xml, which may be the more standard name IIRC, but it doesn't > matter much). > > I don't think it can replace Ant is the primary build mechanism for > log4j, because so many more people use Ant when compared to Maven. I > also think, as you pointed out, that logging-site should be tagged > with every release: be it a CVS or SVN tag, that's a separate to-do > item not related to the Ant or Maven discussion. But for > documentation, sure, maybe it's nice: FWIW, I like Forrest at least as > much as Maven. > > One good thing to ask ourselves is: is this really the itch to > scratch? Have users been complaining about the current documentation? > Or is our time better spent on getting log4j 1.3 backwards-compatible > and out-the-door already? > > Yoav > > On 12/16/05, Curt Arnold <[EMAIL PROTECTED]> wrote: > > Explored a little more and committed some additional enhancements. A > > sample of the generated documentation from Maven can be viewed at > > http://people.apache.org/~carnold/log4j_mvn/maven-reports.html. > > There are many known issues: several of the links point to non- > > existent documents, the checkstyle report throws an exception so it > > is suppressed and while the Javadocs are generated, the apidocs/ > > index.html page is empty (apidocs/overview-summary.html can be used > > to see the generated Javadocs). However, it looks pretty good for > > the amount of time put into it. Will post a message on maven-users > > to see if I can get any help in extending it. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Yoav Shapira > System Design and Management Fellow > MIT Sloan School of Management > Cambridge, MA, USA > [EMAIL PROTECTED] / www.yoavshapira.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
