[
https://issues.apache.org/jira/browse/USERGRID-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596226#comment-14596226
]
David Johnson commented on USERGRID-758:
----------------------------------------
If we add this to the REST module's POM file, inside the maven-war-plugin:
<configuration>
<archive>
<manifestEntries>
<Usergrid-Version>${project.version}</Usergrid-Version>
</manifestEntries>
</archive>
</configuration>
Then we will get this in the MANIFEST.MF file:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Built-By: ApigeeCorporation
Usergrid-Version: 1.0.2
Created-By: Apache Maven 3.3.1
Build-Jdk: 1.8.0
(Where "built-by" will be the username of the user account who built to the
release)
And by removing <final-name> from the POM, we will get a WAR file named like so:
usergrid-rest-1.0.2.war
Is that what we want? If we do this we will also want to update the various
installation guides that we provide to tell people how to deploy
usergrid-rest-1.0.2.war to Tomcat's ROOT context.
> Introduce Semantic Versioning in Build Artifacts
> ------------------------------------------------
>
> Key: USERGRID-758
> URL: https://issues.apache.org/jira/browse/USERGRID-758
> Project: Usergrid
> Issue Type: Story
> Reporter: Jeffrey
> Assignee: David Johnson
>
> We should include in the WAR manifests a version number to be able to
> identify a version of a build and which branch it belongs to. For example,
> right now we have 1.0, 2.0 and 2.1 branches and nothing about the artifact
> filenames differentiates them. This results to mistakes and builds of the
> wrong version getting deployed and mistaken.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
