I used the assembly:assembly plug to create a distribution, however
the descriptor (src/assembly/bin.xml) needs to be tweaked to drop
out non-re-distributable jars. Hopefully, all the non-re-
distributable jars are not essential to operation, at least not on
JDK 1.5. Currently, you can d
On 30/06/2007, at 7:15 AM, Curt Arnold wrote:
There is a splash screen that shows Chainsaw history. That should
be integrated into src/changes/changes.xml.
Is this is the Release Notes section you're referring to? Yes I
think tracking the changes in changes.xml is probably best from now
On Jul 1, 2007, at 5:27 PM, Paul Smith wrote:
I used the assembly:assembly plug to create a distribution,
however the descriptor (src/assembly/bin.xml) needs to be tweaked
to drop out non-re-distributable jars. Hopefully, all the non-re-
distributable jars are not essential to operation
On Jul 1, 2007, at 5:29 PM, Paul Smith wrote:
On 30/06/2007, at 7:15 AM, Curt Arnold wrote:
There is a splash screen that shows Chainsaw history. That should
be integrated into src/changes/changes.xml.
Is this is the Release Notes section you're referring to? Yes I
think tracking the
On Jun 28, 2007, at 1:03 AM, Scott Deboy wrote:
I pulled everything about 2 weeks ago and ran everything through
Chainsaw.
The backported receivers which set properties on events (all of the
new network appenders) are throwing NPEs - around the property
setting code if I recall.
We sho
I don't think we can redistribute activation.jar, jms-1.1.jar,
jmxri-1.2.1.jar, jmxtools-1.2.1.jar and mail-1.4.jar which are
currently included in the generated tarball and zip archive. They
are in the assembly since they are referenced by log4j, but they
can be suppressed.
None o
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
