Use Ant to unjar to your classpath and then jar everything back up
again. You can also use <zipfileset>. Alternatively, you can use
JarJar [1]. The really nifty thing about JarJar is that you can
actually modify the package for Log4j and move it into your own
namespace. Not sure if this is something you care about? If this is
what you want, you'd also have to do some tesing to verify that
JarJar did a good job. JarJar won't catch cases where reflection is used.
[1] http://tonicsystems.com/products/jarjar/
Jake
At 02:30 PM 9/10/2006, you wrote:
>Hi Every body:
>I am using log4j to debug application that's intsalled on different
>systems, and to be distributed and installed on more systems.
>However, log4j has to be installed in the classpath on all these
>systems. Therfore I decided to include the classes from log4j.jar into
>my application and
>put it in a jar. Anyone have an idea about how to get around this ?
>What I am thinking about doing is removing the log4j.jar file from my
>classpath, and add the "log4j_src" whick includes all the *.java files.
>Therefore forcing my application to compile the needed classes and
>include them in along with the classes from my application. Then put
>them all in a jar.
>I am using ant for mu build. I am working on this but I don't know if
>there's another way to do it. Any ideas ??
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
