You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The name of the WAR archive file built by the maven-war-plugin can be important and in Maven & Gradle builds defaults to the artifact + version. However, it can be easily pre-set to a given name .
Here is an example Maven pom.xml excerpt, which uses the <warName> attribute to set the name of the WAR archive. This works correctly and the WAR file is built as cics-java-liberty-restapp.war. However, a bundle-war build ignores this and creates a CICS bundle zip using a WAR built using the <artifact> and '' elements i.e. cics-java-liberty-restapp-0.1.0.war
The name of the WAR archive file built by the maven-war-plugin can be important and in Maven & Gradle builds defaults to the artifact + version. However, it can be easily pre-set to a given name .
Here is an example Maven pom.xml excerpt, which uses the
<warName>
attribute to set the name of the WAR archive. This works correctly and the WAR file is built ascics-java-liberty-restapp.war
. However, a bundle-war build ignores this and creates a CICS bundle zip using a WAR built using the<artifact>
and '' elements i.e.cics-java-liberty-restapp-0.1.0.war
When using the Gradle plugin, this problem does not exist as the
archiveFileName
property is respected by the CICS bundle plugin build. i.e.This sample repo was used in the above example
The text was updated successfully, but these errors were encountered: