DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Two Engines, One Query: DuckDB Inside Neo4j
  • Testing Java and Spring Applications With Kotlin: Low-Risk to Adoption
  • Wasm Inside Neo4j: Building the Example That Didn't Exist
  • OpenAPI From Code With Spring and Java: A Recipe for Your CI

Trending

  • Evals in CI: How to Catch Agent Regressions Before Production Does
  • Why Spark Executors Leave Cores Idle on YARN: A Packing Model for Executor Sizing
  • PWA on iOS, Part 2: HTTPS, Manifest and Service Worker
  • Closing the Drift Loop: An AI Agent That Drafts Terraform Fixes

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Coding
  3. Java
  4. How to Display Maven Project Version in Your Webapp Overview

How to Display Maven Project Version in Your Webapp Overview

By 
Vineet Manohar
·
Sep. 23, 10 · Interview
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
37.1K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

sometimes it is useful to display the version of your web application, typically in the footer area of the web page. by displaying the version information, one can quickly determine which version of the app is running or users can use it for error reporting purposes. displaying the version is also useful when there are frequent automated releases using the maven release plugin and it is hard to track which version is actually deployed on a server. here’s an illustration of how version can be displayed in the footer.

project version shown in footer

this article describes how to display the version of your maven project in your web application.

step 1: create a view file to display the version

first we will create a view file which will display the version. the view file could be a jsp, html, xhtml, a facelet or any format depending on your stack. in this example, we will create a jsp file which will print the version somewhere in the page. however, instead of the hardcoding an actual version, we put a special token ‘project_version’. we don’t want to hard code the version information as it will change from release to release. the special token will be replaced with actual maven project version when the app is packaged.

create the following jsp.

src/main/webapp/version.jsp 

here’s a simple file which displays the version information.

 <html>
  <body>project version is <i>project_version</i></body>
</html>

step 2: add snippet to pom.xml

the maven replacer plugin is a simple and useful plugin which can replaces tokens in file of your choice. add the following snippet of code to your pom.xml.

<project>
 <build>
  <plugins>
   <!-- replace version in file -->
   <plugin>
    <groupid>com.google.code.maven-replacer-plugin</groupid>
    <artifactid>maven-replacer-plugin</artifactid>
    <version>1.3.2</version>
    <executions>
     <execution>
      <!-- the replace should happen before the app is packaged -->
      <phase>prepare-package</phase>
      <goals>
       <goal>replace</goal>
      </goals>
     </execution>
    </executions>

    <configuration>
     <includes>
      <!-- replace the token in this file -->
      <include>target/myproject/version.jsp</include>
     </includes>
     <regex>false</regex>
     <!-- the name of the token to replace -->
     <token>project_version</token>
     <!-- replace it with the maven project version -->
     <value>${project.version}</value>
    </configuration>
   </plugin>
  </plugins>
 </build>
</project>

to test the above setup, you can run the following command:

mvn prepare-package

navigate to the following file.

target/myproject/version.jsp

the contents of this file will look something like this (assuming that your project version is 1.0-snapshot):

<html>
  <body>project version is <i><strong>1.0-snapshot</strong></i></body>
</html>

when your application ships, the version.jsp file will always have the correct version. you can see the version by invoking the version.jsp page.

http://localhost:8080/myproject/version.jsp 

note:

  • your view file does not have to be a jsp, it can be any a view file suitable to your stack. it could be part of your footer which could be included at the bottom in each page.
  • the special token can be changed from project_version to another value of your choice, just change it in the view file as well as the pom.xml
  • instead of having the version contained in a view file, you could have the version in a properties file or a message bundle and then display a message from the message bundle on the view

references

  • maven replace plugin on google code

from http://www.vineetmanohar.com/2010/09/how-to-display-maven-project-version-in-your-webapp

Apache Maven

Opinions expressed by DZone contributors are their own.

Related

  • Two Engines, One Query: DuckDB Inside Neo4j
  • Testing Java and Spring Applications With Kotlin: Low-Risk to Adoption
  • Wasm Inside Neo4j: Building the Example That Didn't Exist
  • OpenAPI From Code With Spring and Java: A Recipe for Your CI

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook