To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4j-chainsaw has an issue affecting its community integration.
This iss
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4j-chainsaw has an issue affecting its community integration.
This iss
- Chainsaw wouldn't mvn install until I copied known.receivers to
chainsaw/target/classes (was getting an error on the
receivershelpertest)
Fixed it, some resources were still in the java tree, where they
shouldn't have been. Do:
svn update
mvn clean test
It should consistently pass now
Got it all working. A few things:
- getting the log4j 1.2 branch to mvn install was a bit of a hassle
because I needed to get nteventappender.dll into my path (from
1.2.14) - the dll wasn't getting built via mvn install - should it
have been? maybe another maven target I should have looke
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
Got it all working. A few things:
- getting the log4j 1.2 branch to mvn install was a bit of a hassle because I
needed to get nteventappender.dll into my path (from 1.2.14) - the dll wasn't
getting built via mvn install - should it have been? maybe another maven target
I should have looked into
Ok gang, mavenization completed I think.
Please grab maven 2.0.4 and install it, and if you use Eclipse,
install the Maven Eclipse plugin:
http://maven.apache.org/
http://m2eclipse.codehaus.org/
After installing the Maven Eclipse plugin, you can activate the
project as a Maven project by d
