from user perspective, some thing in maven changes the artifact file name which is unexpected. maven-dependency-plugin does a lots of artfacts manipulations, unless the user tells it so, the file name remains the same.
-D On 10/12/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
Dan, What makes you think this is a bug? The classifier behavior seems to be hardly documented; at least I am not able to find any documentation. I am switching back and forth if this behavior is intentionally or not. I started to look into the maven-war-plugin sources but so far could not spot the code that is actually causing the removing of the classifier. I added information about the classifier in the affected jar files we are using just to make sure that I end up with the correct jar file. So far the jar files are the right one, but just without the classifier in the name. As said, this makes me think this is intentionally. Please explain why you think this is a bug. I have no problems filing a bug, but would like to collect other opinions as well. But maybe a bug entry would be the best place to discuss this. Thanks in advance, Andreas -----Original Message----- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 8:36 PM To: Maven Users List Subject: Re: [M2] Classifier removed during packaging It is a definitely a bug. Please file a Jira against war plugin -D On 10/11/06, Andreas Guther <[EMAIL PROTECTED]> wrote: > > So far it looks to me as if the behavior is intentionally. > > I made some tests with the classifier giving TestNG the scope compile > which forces Maven to add it to the war file which I usually do not > (<scope>test<scope> instead) and used <classifier>jdk14</classifier>. > > I ended up again with a jar file that did not contain the classifier in > its name. This lets me conclude that this is an desired behavior. > > I personally would feel more comfortable if the classifier would remain > in the jar file name. It makes it easier to control what is actually in > the WEB-INF/lib folder. That removing of the classifier behind the > scene is a little bit unexpected and confusing in my view. > > > > Is there a way to force Maven (i.e. the responsible plug-in) to keep the > jar file classifier while adding jars to the war file? > > Andreas > > > > -----Original Message----- > From: Andreas Guther [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 10, 2006 11:43 AM > To: Maven Users List > Subject: [M2] Classifier removed during packaging > > I have the following situation with Maven 2, classifier usage, and > packaging to a war file: > > The classified jar file is correctly downloaded from repository but ends > in the war file without the classifier part in the jar file name. > > I.e. in my local repository I get the dependency > "something-1.0-classified.jar" downloaded but in the war file I get only > "something-1.0.jar". I expected to see the something-1.0-classified.jar > file in the war. The strange thing is that our repositories do not > contain the classifier-less jar file at all. > > I went through the Maven debug output of the build process and during > the compile phase the file with the classifier is downloaded from the > repository and put on the compile path as expected. > > But during the Assembling the classifier in the name seems to get > removed and the debug output reads Processing: something-1.0.jar > > I am not sure if this behavior is intentional or if I do something > wrong. > > Can someone tell me if this is by design? If not, I at least know that > I have to dig more into the issue. > > Thanks in advance, > > Andreas > > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
