log4j should be a dependency in your pom. other ppl using your project and maven will get the dependencies then automatically. It is not intended to be packaged into your jar.
On Tuesday 27 December 2005 00:32, Luiz Eduardo Guida Valmont wrote: > Hi everyone, > > I'm working on a simple command-line project and it has log4j as one of > its dep's. As I didn't find (or wasn't able to find, so to say) any > documentation on the subject, here is my question: how can I package > log4j along with my project's classes in the jar generated by the > "package" target? I know how I should setup the main class for the jar, > but I still cannot package loj4j along. > > I can bundle the lo4j-1.2.12.jar as a resource and that'd be the end of > it, but that would be far from "elegant" (as I would have to keep track > of changes in the pom.xml (if I decided to change to log4j-1.3.jar I'd > have to copy it over). > > Sorry if this is a question of old. I'd appreciate if anyone would just > point me links that I can follow. ;-) > > Thanks in advance, > Luiz Eduardo > > --------------------------------------------------------------------- > 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]
