[ 
https://jira.codehaus.org/browse/MWAR-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MWAR-271.
-------------------------------

    Resolution: Won't Fix

Please refer to 
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
 if you're wondering why this issue was closed out.

> Manifest.mf file refers to the timestamped version of the SNAPSHOT dependency 
> while ear actually has the SNAPSHOT version of the dependency.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MWAR-271
>                 URL: https://jira.codehaus.org/browse/MWAR-271
>             Project: Maven WAR Plugin
>          Issue Type: Bug
>          Components: manifest
>    Affects Versions: 2.1.1
>         Environment: Windows XP
>            Reporter: Arun Shankar Tiwari
>         Attachments: MANIFEST.MF
>
>
> I have multimodule project say ModuleA, moduleB, moduleC.ModuleB is a web 
> based project while other are jar based project under a parent module  
> parentA.
> I am finally packaging all the jar and war under ear module using maven ear 
> plugin version 2.6. I am using WAR plugin version 2.1.1 and jar plugin 
> version as 2.3.
> Each module have multiple dependencies some with SNAPSHOT depenedency.
> My final artifact is ear  inside which war along with other jars are added. 
> WAR artifacts has manifest.mf file which mentions all the classpath 
> dependencies. I have noticed that most of the SNAPSHOT dependencies are 
> referenced as 1.0.0-SNAPSHOT while one of the SNAPSHOT dependency has the 
> notion of timestamped. 



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to