Listing dependency names in manifest - conflict

[f sa <te...@yahoo.com.br>]

Hi all
   
  I'm having a problem with dependency jar naming within the war file generated by the WAR plugin. There's a dependency on X-2.0.1-SNAPSHOT.jar, but when maven downloads it form the local repository, it puts it in using the unique timestamped name the way it is stored in snapshot repository. It's fine like that normally, except when you need to include its name in the manifest
   
  So you get something like this
   
  WAR contents:
   .
 `-- WEB-INF
     `-- lib
         |-- dep1-1.0.jar
         |-- dep2-1.0.jar
         `-- X-2.0.1-20070626.141521-7
   
  <war>/META-INF/manifest.mf contents:
  Class-Path: dep1-1.0.jar dep2-1.0.jar X-2.0.1-SNAPSHOT.jar
   
  So when application loads, it's trying to set X-2.0.1-SNAPSHOT.jar in the classpath because that's what's listed in the manifest, but doesn't find such library.
   
  Is there a workaround for this kind of issue? Is there a way to force certain dependency name when it gets included in the war file?
   
  You'd expect maven plugin to figure out to either rename the dependency artifact or use the full unique name in the manifest; does this qualify as a bug?
   
  Appreciate any suggestions,
  -p

       
---------------------------------
Ask a question on any topic and get answers from real people. Go to Yahoo! Answers.