42

The application version defined in the banner.txt does not show up on console, when running the application. It is defined according to the docs of Spring Boot 

${application.version}

The project uses the spring-boot-starter-parent as parent pom (Basic project setup from start.spring.io)

pas2al
  • 564
  • 1
  • 4
  • 15
  • This worked fine for me. I generated a project from start.spring.io. Then, I added file src/main/resources/banner.txt, with contents referencing `${application.version}`. Then, I reran `./mvnw clean package`. Then, I ran `java -jar target/demo-0.0.1-SNAPSHOT.jar`. It printed `0.0.1-SNAPSHOT` as expected. If this is not working for you, do you want to provide more details, like perhaps your banner.txt file? – Chris Nauroth Dec 29 '15 at 22:48

7 Answers7

41

Ok, the version gets printed if i build the project and run it via java -jar. But if i start the application within my IDE (IntelliJ IDEA) the version will not be printed.

According to the Spring Boot documentation on Customizing the Banner, the value of ${application.version} is taken from the jar manifest.

The version number of your application as declared in MANIFEST.MF. For example Implementation-Version: 1.0 is printed as 1.0.

When running from an IDE, it's typical for execution to occur against the class files compiled by the IDE. The IDE typically doesn't go through a full cycle of building the whole jar with a manifest. Therefore, there is no MANIFEST.MF available at runtime for substituting the value of ${application.version}, and you're left with the bare token.

This is not a bug in your code, and you've already seen that it works correctly when doing a full jar build. If it's really important to fix this while running through the IDE, then you could consider setting up a custom build step that does go through the full jar build and manifest generation first. That's probably overkill though. The banner could be validated later outside the IDE by testing against a real release build of the jar.

Stefan
  • 12,108
  • 5
  • 47
  • 66
Chris Nauroth
  • 9,614
  • 1
  • 35
  • 39
  • 4
    It doesn't work for me even when running the jar file with java. Any idea why? I have this line inside my banner.txt file: `Version ${application.version}` which is shown exactly the same in the console – Alireza Mirian Feb 15 '16 at 08:38
  • @AlirezaMirian, did you follow the exact same steps to build and execute that I described in my comment on the question? That's working fine for me. If that still doesn't work for you, then I'm afraid I'm out of ideas. There must be something different in your environment, but I'm not sure what. – Chris Nauroth Feb 16 '16 at 17:45
  • If you package the spring-boot application as WebApp and deploy it on Liberty server it does not print the application version etc. – user1428716 Apr 11 '18 at 12:24
15

Another solution:

Use the maven resources plugin to "filter" (replace) properties in resource files.

In the pom, activate resources filtering with the following definition:

<resources>
    <resource>
        <filtering>true</filtering>
        <directory>src/main/resources</directory>
        <includes>
            <include>application.properties</include>
        </includes>
    </resource>
</resources>

In the application.properties file:

info.app.name=@project.artifactId@
info.app.version=@project.version@

In the banner.txt file:

${info.app.name} (${info.app.version})
Nicolas Dos Santos
  • 449
  • 5
  • 14
  • 1
    This worked fine for me with no adaptation in name application.properties even though my properties-file reads application.yml – kitekat Oct 28 '22 at 08:54
  • I see the version info in the Banner in IntelliJ without building a JAR, anyhow project is set up to build a WAR. – kitekat Oct 28 '22 at 09:00
9

Just for reference, here's what I found works for the command-line in Spring Boot 2 with a Gradle-based project (using the Spring Boot Gradle plugin). Intellij’s console still doesn't work for me, but that problem has been around for several years now.

Using the jar task wasn't working for me on a standard 2.0.5.RELEASE build.gradle, because the bootJar task takes precedence:

By default, when the bootJar or bootWar tasks are configured, the jar or war tasks are disabled.

So I tried the bootJar task, and it works:

version = '0.0.1-SNAPSHOT'

bootJar {
    mainClassName = 'com.demo.Application'
    manifest {
        attributes('Implementation-Title':   'Demo Application',
                   'Implementation-Version': version)
    }
}

Note: There is no need for mainClassName and its equivalents if you have only one main class. The discovered or configured main class is automatically added to the MANIFEST.MF as 'Start-Class'.

Once this is working, you can use ${application.title} and ${application.version} as usual in your Spring Boot banner.txt file.

ben3000
  • 4,629
  • 6
  • 24
  • 43
6

In my case, I look inside the manifest created by spring-boot-maven-plugin and there were no Implementation-version inside.

To add it, I add the plugin maven-jar-plugin in build.plugins section of my pom.xml. 

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-jar-plugin</artifactId>
    <version>3.0.2</version>
    <configuration>
         <archive>
              <manifestEntries>
                    <Implementation-Version>${project.version}</Implementation-Version>
              </manifestEntries>
         </archive>
    </configuration>
</plugin>

After that as already mention before I can see the banner with the application version only when I do java -jar et not with my ide

bolivier
  • 175
  • 2
  • 10
6

You can also use resource filtering in banner.txt. Just use ${project.version} in banner.txt

Example for maven:

<resources>
            <resource>
                <filtering>true</filtering>
                <directory>src/main/resources</directory>
                <includes>
                    <include>banner.txt</include>
                </includes>
            </resource>
        </resources>
spx01
  • 359
  • 4
  • 6
0

For me works perfectly replace texts on mvn build by:

com.google.code.maven-replacer-plugin

  <plugin>
    <groupId>com.google.code.maven-replacer-plugin</groupId>
    <artifactId>replacer</artifactId>
    <version>1.5.3</version>
    <executions>
      <execution>
        <phase>prepare-package</phase>
        <goals>
          <goal>replace</goal>
        </goals>
      </execution>
    </executions>
    <configuration>
      <file>target/classes/banner.txt</file>
      <replacements>
        <replacement>
          <token>application.title</token>
          <value>${artifactId}</value>
        </replacement>
        <replacement>
          <token>application.version</token>
          <value>${version}</value>
        </replacement>
      </replacements>
    </configuration>
  </plugin>

Yes I did remove ${} from banner.txt

NotLikeNames
  • 1
  • 1
0

Basically ${application.title} ${application.formatted-version} values are picked from the manifest file of the packaged jar file. so i am not sure we can really print them during build life cycle of the project.enter link description here

you can refer below example

ManjuGH
  • 21
  • 2