On Apr 22, 2007, at 9:54 PM, Paul Smith wrote:
firstly, the pom.xml that is in svn for the 1.2 tree seems to have
odd line endings. I've converted them to to LF only for my
purposes purely so I can edit the text properly. I've then added a
copy of the build & depenency block from the trunk, and added the
one missing jmxtools dependency it needs (one of those Sun ones
you'll need).
Heres a diff of what I have local, which shows the whole file as
being changed completely because of the line endings. Curt, care
to review?
The unit tests don't work yet, I'm guessing further work needs to
adjust it so that a package can be built, but at least it compiles
ok and using the maven-eclipse plugin does seem to like it also
with no compile errors.
Paul
Sorry about the line-endings, hopefully I did better this time. I
was able to simplify the dependencies so that only one file
(jmxtools) needs to be manually downloaded and installed to build
log4j 1.2 on Java SE 5. I added explicit specifications to target
Java 1.3 or later and only accept Java 1.3 language features. I
specified the working directory for the unit tests which allowed
things to get started, but there are a decent number of failures.
Some are due to the tests not stripping out Maven's entries in the
stack traces. I cut and pasted some of the site reporting code from
one of the plugins. I thought, but refrained, from copying over src/
site and src/changes from one of the other projects, but I am pretty
tempted to make a shot at moving to a Maven generated site and
documentation.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
