Log of /logging/chainsaw/trunk/build.xml
Parent Directory
| 
Revision Log
Revision
496155 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sun Jan 14 21:18:59 2007 UTC
(2 years, 10 months ago)
by
psmith
File length: 17230 byte(s)
Diff to
previous 430930
(
colored)
Bug 41239 Mac OSX distribution did not exit
cleanly because of missing jars in the distribution.
Fixed by using the webstart-dist directory of jars, which matches the other distribution and
also uses signed jars to boot
Revision
382249 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Mar 2 02:47:14 2006 UTC
(3 years, 8 months ago)
by
psmith
File length: 17184 byte(s)
Diff to
previous 380234
(
colored)
Changed the distribution mechanism so that all distributions exclude the DB & JMS
bits and pieces, because it just won't work like that.
Everyone just has to put these jars is the .chainsaw/plugins directory like VFS. *sigh*.
Revision
380234 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Feb 23 21:49:49 2006 UTC
(3 years, 9 months ago)
by
psmith
File length: 17122 byte(s)
Diff to
previous 376082
(
colored)
Bit of a hack for gump. The log4j main source code is not available during
a gump run, so I have set a 'gump' flag in the chainsaw gump run, which disables
generation of the JavaDoc for ALL receivers.
That's all I can think of doing for now, ideas appreciated.
Revision
376082 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Wed Feb 8 21:37:12 2006 UTC
(3 years, 9 months ago)
by
psmith
File length: 16937 byte(s)
Diff to
previous 373042
(
colored)
Fix for Bug #38582. Since Chainsaw moved out into it's own SVN repo,
it appears that the distribution no longer built all the Receiver Java Doc (because
they are still in the log4j source path.
Changed the build sequence so that to get the JavaDoc for Receivers requires the
location of the log4j source code. Failing to have this just means that Chainsaw
doesn't have all the JavaDoc embedded.
Revision
370986 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sat Jan 21 05:40:04 2006 UTC
(3 years, 10 months ago)
by
psmith
File length: 16389 byte(s)
Diff to
previous 370984
(
colored)
'distribution' target now builds OSX bundle and auto-creates
.dmg bundle which goes with the other distributions when uploading.
Revision
370984 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sat Jan 21 05:08:59 2006 UTC
(3 years, 10 months ago)
by
psmith
File length: 16203 byte(s)
Diff to
previous 369425
(
colored)
Change to distribution build such that the Webstart distribution
does NOT ship with Comomons VFS because of classloading issues.
Webstart users who wish to use VFS will need to place Commons VFs
jars and all the filestore implementation jars inside the Chainsaw
plugin directory. Shell script and OSX distro users won't have that
limitation.
Revision
369425 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Mon Jan 16 10:20:31 2006 UTC
(3 years, 10 months ago)
by
psmith
File length: 14971 byte(s)
Diff to
previous 369178
(
colored)
Added a 'distribution' target, which creates all distributions,
bundles them together and then SCP's them to a set location,
ready for unpacking.
This just automates quite a bit of stuff that I do often when creating
the distribution, often time consuming and error prone, exactly what
ant is good for.
I'll add the OSX distribution to this set next.
Revision
368983 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sat Jan 14 05:40:22 2006 UTC
(3 years, 10 months ago)
by
psmith
File length: 13608 byte(s)
Diff to
previous 348906
(
colored)
Modified Chainsaw 'webstart' build process so that it can
automatically generate the .sh and .bat files required.
I was getting really tired of having to manually change these, so created
a custom Ant task to assist. Placed the Ant task source code in it's
own source folder out of the way of the rest of the app, as it is only
needed during the build process.
Revision
348906 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Fri Nov 25 07:06:30 2005 UTC
(4 years ago)
by
psmith
File length: 12550 byte(s)
Diff to
previous 345811
(
colored)
Added a target that creates a jar with the ZeroConf appender and related classes.
This jar can be bundled with a log4j1.2.x distribution to add ZeroConf ability to
it's SocketHubAppender. (have tested this with an external project)
Revision
345811 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Mon Nov 21 02:31:35 2005 UTC
(4 years ago)
by
psmith
File length: 11345 byte(s)
Diff to
previous 308068
(
colored)
Added native OS X support to Chainsaw.
Used dynamic(reflection) to determine if the current running OS is OSX
and if the appropriate Mac Java extensions are available, and dynamically
install the hooks so that the Menu bar appears where it should in OSX, plus
place Preferences/About and Quit menu items where they should too (don't
display them in the other menu items either).
Using dynamic means removes the need for a user to have OS X to compile Chainsaw.
Also added a "iSaw" target (yes it sounds like "eyesore"... can't think of anything else
as yet) that uses jarbundler to create a ".app" folder of the Chainsaw distribution.
I'm currently manually creating a .dmg file with Disk Utility, but hope to ant
that step as well.
Will get the user community to test the .dmg distribution and get feedback before placing
it as a supported distribution from the website.
Revision
308064 -
(
view)
(
annotate)
-
[select for diffs]
Added
Fri Feb 25 03:23:48 2005 UTC
(4 years, 8 months ago)
by
psmith
File length: 9094 byte(s)
Using CVS tricks suggested by Ceki, I have already copied over the chainsaw source file history,
so you won't see any of that here.
These are just misc other files needed by Chainsaw that was easier to do by hand (had already
done the move last night), plus a fixed up build process.
I copied the NOTICES and LICENSE file from logging-log4j, which I figured was the correct
thing to do.
One can build an run Chainsaw via Ant if one plonks log4j jars in a lib/ subdirectory
and run "ant chainsaw", or if in Eclipse, you can just make logging-chainsaw
depend on your logging-log4j project, and just run the LogUI as the main class.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
enter a numeric revision.
