Log of /logging/chainsaw/trunk/HOWTOBUILD.txt

---

Revision 670416 - (view) (annotate) - [select for diffs]
Modified Sun Jun 22 21:23:49 2008 UTC (17 months ago) by psmith
File length: 3321 byte(s)
Diff to previous 546018 (colored)

Updated HOWTOBUILD.txt to reflect some dependency build information change.

---

Revision 546018 - (view) (annotate) - [select for diffs]
Modified Mon Jun 11 05:34:14 2007 UTC (2 years, 5 months ago) by psmith
File length: 3543 byte(s)
Diff to previous 545981 (colored)

Added dependency to log4j-zeroconf companion module.

---

Revision 545981 - (view) (annotate) - [select for diffs]
Modified Sun Jun 10 23:44:37 2007 UTC (2 years, 5 months ago) by sdeboy
File length: 3451 byte(s)
Diff to previous 545445 (colored)

Added maven dependency on the pattern-layout log4j companion to support the 
display of event properties in Chainsaw's event detail panel

---

Revision 545445 - (view) (annotate) - [select for diffs]
Modified Fri Jun 8 07:14:20 2007 UTC (2 years, 5 months ago) by psmith
File length: 3348 byte(s)
Diff to previous 545442 (colored)

Updated dependencies to correct 1.0-SNAPSHOT version of the children, 
plus log4j 1.2.15-SNAPSHOT.

Update the HOWTOBUILD.txt to refer to the new svn location, and corrected
the javadoc creation documentation to refer to 1.0-SNAPSHOT.

Now mvn install will create a bundle that contains the latest code with javadoc embedded.

---

Revision 545442 - (view) (annotate) - [select for diffs]
Modified Fri Jun 8 06:54:41 2007 UTC (2 years, 5 months ago) by psmith
File length: 3342 byte(s)
Diff to previous 544038 (colored)

Worked out how to embed the receiver javadoc.  Currently needs a manual
build of the javadoc via the receivers module, and then a local installation.

I've used 'apache-log4j-receivers-javadoc' as the artifactId.  Happy to change
it if anyone can suggest something different.

Not sure how javadoc is automatically deployed/referenced as a depencency, my guess
is that it's not that common for the javadoc to be a dependency.

---

Revision 544038 - (view) (annotate) - [select for diffs]
Modified Mon Jun 4 03:42:09 2007 UTC (2 years, 5 months ago) by psmith
File length: 2992 byte(s)
Diff to previous 544025 (colored)

Added more details on how to get Chainsaw built using Maven,
plus how to create the webstart distribution with code-signing ability.

This hopefully should lower the barrier of other log4j-devs from signing and 
cutting a webstart release.

---

Revision 544025 - (view) (annotate) - [select for diffs]
Modified Mon Jun 4 01:01:04 2007 UTC (2 years, 5 months ago) by psmith
File length: 793 byte(s)
Diff to previous 345596 (colored)

Added webstart distribution steps, first cut at HOWTOBUILD.txt for general users.

---

Revision 345596 - (view) (annotate) - [select for diffs]
Modified Fri Nov 18 23:02:28 2005 UTC (4 years ago) by psmith
File length: 1774 byte(s)
Diff to previous 308064 (colored)

Tweaked some of the documentation a touch, added reference
to XStream.

---

Revision 308064 - (view) (annotate) - [select for diffs]
Added Fri Feb 25 03:23:48 2005 UTC (4 years, 9 months ago) by psmith
File length: 1734 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.