[maven-ear-plugin] branch master updated: [MEAR-278] log outdated resources deletion

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[maven-ear-plugin] branch master updated: [MEAR-278] log outdated resources deletion

hboutemy
This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-ear-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new 6a5ec73  [MEAR-278] log outdated resources deletion
6a5ec73 is described below

commit 6a5ec7360101ca4e174cbf523b13264ca3da5695
Author: Hervé Boutemy <[hidden email]>
AuthorDate: Sat Sep 12 19:29:54 2020 +0200

    [MEAR-278] log outdated resources deletion
   
    experience on MWAR or MEAR-284 show that if outdated deletion gives
    unexpected result, understanding that the unexpectedly missing file has
    been deleted by the outdated managment is f**ing hard
---
 src/main/java/org/apache/maven/plugins/ear/EarMojo.java | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/main/java/org/apache/maven/plugins/ear/EarMojo.java b/src/main/java/org/apache/maven/plugins/ear/EarMojo.java
index 413f3b6..374339b 100644
--- a/src/main/java/org/apache/maven/plugins/ear/EarMojo.java
+++ b/src/main/java/org/apache/maven/plugins/ear/EarMojo.java
@@ -374,6 +374,7 @@ public class EarMojo
         {
             if ( new File( getWorkDirectory(), outdatedResource ).lastModified() < startTime )
             {
+                getLog().info( "deleting outdated resource " + outdatedResource );
                 new File( getWorkDirectory(), outdatedResource ).delete();
             }
         }