You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Barry McGillin (JIRA)" <ji...@apache.org> on 2018/12/18 22:00:00 UTC
[jira] [Created] (MWAR-421) Overlay WEB-INF/lib jars have either
really old or really futuristic timestamps
Barry McGillin created MWAR-421:
-----------------------------------
Summary: Overlay WEB-INF/lib jars have either really old or really futuristic timestamps
Key: MWAR-421
URL: https://issues.apache.org/jira/browse/MWAR-421
Project: Maven WAR Plugin
Issue Type: Bug
Components: overlay
Affects Versions: 3.2.2
Environment: mac (high sierra) n Oracle linux 7 (redhat)
Reporter: Barry McGillin
Attachments: Screen Shot 2018-12-18 at 18.51.52.png, Screen Shot 2018-12-18 at 18.54.07.png, Screen Shot 2018-12-18 at 18.56.17.png
We are building a war file which is a superset of one of the overlays. Ie we're adding some jars to the WEB-INF/lib with overlays.
On doing the overlay the dates of the files in the war get changed with no reason. Building locally is sort of ok, but the dates on the libs are in the future. however, on our build machine, the dates are way in the past like may 1940's!!!
Heres the relevant parts of the pom. its pretty simple, with a dependent war getting deps added and reshipped as a new war.
<packaging>war</packaging>
<name>example</name>
<properties>
<productName>sdw</productName>
<warPath>${project.build.directory}/${productName}.war</warPath>
</properties>
<dependencies>
<dependency>
<groupId>oracle.dbtools.modeler</groupId>
<artifactId>dbtools-modeler-common</artifactId>
<version>18.4.0-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>oracle.dbtools.sdw</groupId>
<artifactId>sdw-server</artifactId>
<version>${project.version}</version>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>oracle.dbtools.sdw</groupId>
<artifactId>sdw-client</artifactId>
<version>${project.version}</version>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>oracle.dbtools.ords</groupId>
<artifactId>ords</artifactId>
<version>${project.version}</version>
<type>war</type>
<exclusions>
<exclusion>
<groupId>*</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>3.2.2</version>
<configuration>
<overlays>
<overlay>
<id>ords-base</id>
<groupId>oracle.dbtools.ords</groupId>
<artifactId>ords</artifactId>
<filtered>false</filtered>
<includes></includes>
</overlay>
</overlays>
<archive>
<manifest>
<mainClass>oracle.dbtools.jarcl.Entrypoint</mainClass>
</manifest>
</archive>
</configuration>
</plugin>
</plugins>
</build>
</project>
$
$ ls -al
total 165624
drwxr-xr-x 64 bamcgill staff 2048 18 Dec 17:47 .
drwxr-xr-x 7 bamcgill staff 224 18 Dec 17:47 ..
-rw-r--r-- 1 bamcgill staff 70604 1 Feb 2077 commons-fileupload-1.3.3.jar
...
-rw-r--r-- 1 bamcgill staff 1889279 1 Feb 2077 xmlparserv2-sans-jaxp-services-18.3.0.0.jar
war/work/oracle.dbtools.ords/ords/WEB-INF/lib/
bamcgill master ... orahub sql-developer-web ords-sdw ls -al
total 124032
drwxr-xr-x 61 bamcgill staff 1952 18 Dec 17:47 .
drwxr-xr-x 7 bamcgill staff 224 18 Dec 17:47 ..
-rw-r--r-- 1 bamcgill staff 70604 1 Feb 2077 commons-fileupload-1.3.3.jar
...
-rw-r--r-- 1 bamcgill staff 88535 1 Feb 2077 sdodep3prt-19.1.0.0.0-180607.jar
-rw-r--r-- 1 bamcgill staff 391988 1 Feb 2077 sdoutl-18.1.0.0.0-170918.jar
-rw-r--r-- 1 bamcgill staff 1398331 1 Feb 2077 ucp-18.3.0.0.jar
-rw-r--r-- 1 bamcgill staff 262415 1 Feb 2077 xdb6-18.3.0.0.jar
This seems to be something in the overlay code which is setting these aggressively rather than just taking what was in the overlay war.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)