[ 
https://issues.apache.org/jira/browse/MEAR-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214108#comment-17214108
 ] 

Marat Abrarov edited comment on MEAR-221 at 10/14/20, 5:54 PM:
---------------------------------------------------------------

According to [pull request 
#23|https://github.com/apache/maven-ear-plugin/pull/23] and (extended) 
skinny-wars-timestamp test this bug is not relevant. At least for the changes 
in [pull request #23|https://github.com/apache/maven-ear-plugin/pull/23].

[~afloom], could you please:
 # Provide minimal maven project and steps around it to reproduce this bug
 # Test [pull request #23|https://github.com/apache/maven-ear-plugin/pull/23] 
for your use case

?


was (Author: abrarovm):
According to [pull request 
#23|https://github.com/apache/maven-ear-plugin/pull/23] and (extended) 
skinny-wars-timestamp test this bug is not relevant. At least for the changes 
in [pull request #23|https://github.com/apache/maven-ear-plugin/pull/23].

[~afloom], could you please:

# Provide minimal maven project to reproduce this issue
# Test [pull request #23|https://github.com/apache/maven-ear-plugin/pull/23] 
for your use case

?

> SNAPSHOT included with timestamp in skinnyWars but not removed from war(s)
> --------------------------------------------------------------------------
>
>                 Key: MEAR-221
>                 URL: https://issues.apache.org/jira/browse/MEAR-221
>             Project: Maven Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.10.1
>         Environment: Windows 7, Maven 3.0.4, IBM JDK 7.1
>            Reporter: Anders Hammar
>            Priority: Major
>
> When configuring ear for skinnyWars and adding a SNAPSHOT dependency, that 
> jar artifact is added with (with snapshot timestamp identifier) in ear's lib 
> folder but the SNAPSHOT jar artifact is not removed from skinny wars. (The 
> jar artifact in the war is not using timestamp identifier but -SNAPSHOT 
> version in file name.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to