[
https://issues.apache.org/jira/browse/MWAR-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134816#comment-17134816
]
Herve Boutemy edited comment on MWAR-434 at 6/13/20, 2:52 PM:
--------------------------------------------------------------
given the goal creates the jar, I think this timestamp check is not useful: the
jar is created in-place instead of being copied, it just need to be marked as
not outdated the same way copy does
was (Author: hboutemy):
given the goal creates the jar, I think this timestamp check is not useful: the
jar is a dependency, even if not in pom dependencies: just need to mark it as
not outdated
> archiveClasses Jar file is not created in WEB-INF/lib
> -----------------------------------------------------
>
> Key: MWAR-434
> URL: https://issues.apache.org/jira/browse/MWAR-434
> Project: Maven WAR Plugin
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Maxim Solodovnik
> Priority: Blocker
>
> I just have switched from 3.2.3 to this new version and it seems
> https://maven.apache.org/plugins/maven-war-plugin/exploded-mojo.html#archiveClasses
> Is not working anymore :(
> Here is the sample project
> https://github.com/solomax/multimodule-with-war
> JAR file in
> multimodule-with-war-web/target/multimodule-with-war-web-1.0.0-SNAPSHOT/WEB-INF/lib/
> Is NOT created with 3.3.0 and created with lower versions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
