Paul Smith skrev den 07-08-2008 00:03:
The only thing I had to do was to delete the jmx reference in pom.xml
as this is present in the JDK. Then it built and installed without a
hinch (except it took 11 minutes).
That 11 minutes will be all the Maven artifacts being downloaded
(almost n
The only thing I had to do was to delete the jmx reference in
pom.xml as this is present in the JDK. Then it built and installed
without a hinch (except it took 11 minutes).
That 11 minutes will be all the Maven artifacts being downloaded
(almost nothing to do with log4j - only a handf
Paul Smith skrev den 04-08-2008 23:25:
I have had no problems mvn installing log4j (I've needed to do so a
lot because Pinpoint and some other log4j-* projects link against the
current SNAPSHOT).
I ended up taking a virgin (in log4j regards) Ubuntu box with Java 6,
installed latest Maven, pu
I have had no problems mvn installing log4j (I've needed to do so a
lot because Pinpoint and some other log4j-* projects link against the
current SNAPSHOT).
mvn dependency:tree will show you all the dependencies and transitive
dependencies.
Paul
On 04/08/2008, at 7:00 AM, Thorbjørn Ravn
Hi.
I am trying to figure out how to build the various subprojects of log4j,
and just want to know if it is just my configuration or if "Oro" is
required to run "mvn install" in log4j trunk?
(I also disabled the NTEventAppenderTest in test/build.xml as this is
under XP).
Is log4j being bui
