cdm-webapp is not using current version of cdmlib-remote-webapp.war
After pushing a specific commit to the server and runing the build pipeline the resulting cdm-server is nor making use of that commit. It seems to be running on the old code.
A comparison of the md5sums of the cdmlib-remote-webapp.war artifacts as used in the jenkins pipeline revealed that the problem occures in the cdm-webapp project.
The correct war file is downloaded by maven but when creating the war overlay an old version of that artifact is used.
Summary of the md5sum comparison:
cdmlib-remote-4.4.0-SNAPSHOT.jar in different steps of the build pipeline:¶
all checksums are md5
as produced by the cdmlib integration job¶
what has been downloaded by the cdm-webapp job¶
Downloaded: http://wp5.e-taxonomy.eu/mavenrepo/eu/etaxonomy/cdmlib-remote-webapp/4.4.0-SNAPSHOT/cdmlib-remote-webapp-4.4.0-20161125.142844-97.war (72706 KB at 86967.7 KB/sec)
Downloaded: http://wp5.e-taxonomy.eu/mavenrepo/eu/etaxonomy/cdm-vaadin/4.4.0-SNAPSHOT/cdm-vaadin-4.4.0-20161125.140639-1562.war (90568 KB at 88100.6 KB/sec)
what is contained in the cdm-webapp¶
what is contained in the cdm-servers cdm-webapp¶
The problem obviously is the order of the overlays. In the pom vaadin comes first and thus determines the version of the cdmlib-remote-webapp artifact. Swapping the order solves the probelm.
The blog post https://dzone.com/articles/mavens-war-overlays-how-manage has interesting details on skinny overlays an is woirth reading even if it is not directly helpful in understanding the issue here.
#4 Updated by Andreas Kohlbecker over 2 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 50
Applied in changeset cdm-webapp|f55d498166acfa645e4f31af5869302f6acdb814.