[Tony Herstell]

I think I found the “annoying” bug where the Archive name keeps “re-setting”
The DeploymentAssembly setting
->
Archive Name

gets reset when you do a maven update.

This is a sly and big timewaster and you end up with two deployments and this can REALLY confuse you as you keep running agaist the old one (as the new one has the some-project-0.0.1-SNAPSHOT.war added)…

I may not have found it; but…. looks like it…

• This topic was modified 5 years, 1 month ago by Tony Herstell.

[support-tony]

Tony,

Maven>Update Project has the option Update project configuration from pom.xml. If set, it will, well, update the project configuration, including the archive name. Unfortunately, there is no way to change the default for that option.

So the choices are to either ensure this option is unset, every time you do a project update, or to alter the pom, to get the archive name you want. For the latter, you can either change the artifact ID and/or version, or make use of the <finalName> tag in the build section of the pom. For example,

  <build>
  	<finalName>${project.name}</finalName>
...

will set the archive name to just the project name (specified in the name field of the pom). Or you can specify a fixed name for the archive.

Please let us know if this helps.

[Tony Herstell]

Slapped it in here… thx…
<build>
<finalName>openshift-support</finalName>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.0</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>

[support-tony]

Tony,

That’s great news. Thanks for getting back to us.

[Author]

Posts