On Jan 8, 2005, at 9:55 AM, Ceki Gülcü wrote:
At 04:34 PM 1/8/2005, Curt Arnold wrote:logging-log4j is currently failing due to Gump expecting the "jar" target to prepare both a log4j.jar and a chainsaw.jar target when due to recent changes it only produces a log4j.jar target. I've got a series of changes that should get Gump back online which I will commit if there are no objections.
Basically, the changes do:
Restore the "jar" target to build both log4j.jar and log4j-chainsaw.jar. If you just want to build log4j.jar, you can use the "log4j.jar" target.
I committed exactly the same change a few hours ago.
I hadn't seen a commit message on it yet, but it is in there.
Change the Gump description of logging-log4j to run the "log4j.jar" target and only expect log4j.jar, change the name of the "log4j-tests" project to "logging-log4j-tests" and add a new project "logging-log4j-chainsaw" that builds chainsaw.jar.
+1.
Done
Remove the dependency of the "log4j.jar" target on "build.chainsaw" and "build.examples" by introducing a "build.log4j" target. Those targets don't contribute classes to log4j.jar and it would be good that any breakage in chainsaw or the examples, not break applications that depend just on log4j.jar.
+1
Done
Add "build.examples" as a dependency to the "regression" target in tests/build.xml. Maybe there is a better place for this, but it isolates dependent projects from breakages in the examples, but still compiles them as a "test" of the API.
build.examples is no longer a dependency of tests/build.xml. So there is no need to modify ./tests/build.xml.
Not changed. As it is currently committed, there will be no automatic notification if the examples don't compile.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
