Re: maven renaming jar files

I have overcome the problem. And guess know the reason for that, actually at the time of creating the LAN maven repository, I have installed common components under org.apache.commons groupId ( assuming the convention of groupId as package name ). So now when I was including commons-logging as

Re: maven renaming jar files

If you're using mvn install or mvn deploy to install/deploy common artifacts like commons-logging etc, then you're probably using Maven wrong. What you've described is exactly what the problem was. You had added c-l as a particular G/A/V and then c-l was coming in as a transitive dep under a

Re: maven renaming jar files

I've certainly done something similar in the past. To reduce network traffic, and to better control what libs are used, it is nice to have a repository on a local server hosting the jars you need. It is very tempting to just take the set of jars you have always been using (in an existing

Re: maven renaming jar files

We've had more than one person show up on this list complaining about strange difficulties with Maven. After a bit of prodding, they tell us that they manually created their repo and the pom files, if they exist at all, are just GAV with no transitive deps. And then they're usually complaining

Re: maven renaming jar files

Or if you are checking them in manually, at least use a different version which includes your company name, e.g. groupIdcommons-logging/groupId artifactIdcommins-logging/artifactId version1.0-mycompany-1/version That way maven will at least detect that these are different versions of the same

Re: maven renaming jar files

Actually all that happened ( installing commons into the LAN repository ) on the second day of i started using maven(2nd week of my first job :) ), there has been a strict deadline for that. But anyways I guess these are just lame excuses for misusing maven(unintentional), but at that time thats'

maven renaming jar files

Hi,. When I am packaging a WAR project, I am seeing the following thing happening... [DEBUG] Processing: commons-logging-1.1.jar [DEBUG] Duplicate found: commons-logging-1.1.jar [DEBUG] Renamed to: commons-logging-commons-logging-1.1.jar Any idea why this happens and how to avoid this? I am

Re: maven renaming jar files

Looks weird. Do you use a released version ? or the current snapshot ? Could you load an issue in jira with a simple project which reproduce this ? -- Olivier 2008/1/30, amit kumar [EMAIL PROTECTED]: Hi,. When I am packaging a WAR project, I am seeing the following thing happening...