It searches for some log4J. But for development you can also use a jar with scope provided and provide log4j over pax logging or another bundle that run in your osgi container. Here is a part of my POM: So who is right? Anyway, I have added it to my POM, but maven fails at finding it on the repository. I use Nexus but others here use another one and are happy with it 2 Do things the “Maven” way.
|Date Added:||7 July 2004|
|File Size:||11.19 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
This makes so many things much easier and adds a lot of transparency and visibility to your work with maven.
I’m not sure what it really is: So who is right? If you do not like the Maven way, don’t start with Maven. I use Nexus but others here use another one and are happy with it 2 Do things the “Maven” way.
If the jar contain a osgi manifest it’s a bundle. I’m quite a newbie in Maven and I want to know how things are supposed to work, how much I can rely on the repositories. So, if “bundle” is a standard packaging option, as maven guys, would you say that: So don’t worry, Maven will do the job for you.
For now, I have found a workaround by deploying log4j in my local repository as a “jar” package: Hello, In my project, I have a dependency over log4j 1. Too many people use custom plug-ins to hide bad practices. Here is a part of my POM: I am working with m2eclipse and I think that he is as confused as I was.
Maven – Users – log4j:log4j:bundle : Bundle or JAR ?
In reply to this post by raphael. Hi, try to download with packaging type jar. Then, install log4j-1.2.16.jar using the command: However the type of this artifact is “jar” because it is still a JAR file – it just uses a different lifecycle to check and generate the JAR, and this lifecycle also adds the appropriate OSGi metadata to the artifact.
Thanks in advance for your advice.
Index of /groups/product-ga/log4j/log4j/redhat-3
So when in doubt, use the extension in the repository as your log4j-1.2.16.nar type and don’t worry about the actual pom packaging. It works great with CLI maven though.
I mean, I expect the stuff found in the central repository to be reliable able to find all needed dependencies, and all indexed artifact. They are fine for optimizing your builds but are not necessary if you are building a normal Java system 4 Read the maven books. Free advice – worth at least what you log4k-1.2.16.jar paying.
Index of /groups/product-ga/log4j/log4j/1.2.16.redhat-3
The central repository or my maven client? Definitely ask the Log4j team, we have no idea what they intended to do. It will drive you crazy, annoy the hell out of the rest of us, lead to countless frustrating questions and in the end it will be worse more fragile, more complex and less automated than your current system.
Isn’t the central repository a repository server of some kind that should have some consistency checks on “upload”? I don’t criticize or something. I’m actually migrating all our projects to maven and I want to log4j–1.2.16.jar sure of the durability of the solution I choose. He is still searching for alog4j.
Index of /nexus/content/groups/public/log4j/log4j/1.2.16
But I have some “maven-related” ideas to clarify: There are at least 2 free ones available. Search everywhere only in this topic.
Search everywhere only in this topic Advanced Search log4j: Anyway, I have added it to my POM, but maven fails at finding it on the repository. On 26 November