Many companies with Java as primary platform nowadays start to write pure HTML5/JavaScript front-ends, which is basically a good idea, since most Java Web Frameworks are quite painful.

The question is, how to integrate such an App into the existing Maven/Graddle build and how to deploy it on the application server. Since JavaScript has its own ecosystem of build and packaging systems, such as Node.js, Grunt or Bower.

One approach, I see a lot, is to integrate HTML5/JavaScript completely into the Java Project structure and let Maven trigger the JavaScript build. The idea is to just put all the JavaScript code and assets into a Maven WAR module and use the grunt-maven-plugin, or something similar, to launch the Grunt build.

Well, that works, but I’d advice against this approach, because:

  • It’s odd to couple two full featured build systems
  • Their build phases are not synchronized: The whole Grunt build, including the JavaScript tests, is executed in the Maven Test phase (default)
  • It slows things up to launch Maven and the Java VM to just start-up V8 and Grunt
  • The developers will start to use the Java Application Server instead of node.js for development, which is significantly slower and doesn’t allowed to run jshint and the JavaScript unit tests in the background
  • As your JavaScript applications grow you might want to re-use some Code and CSS in other Apps. That’s not possible with the integrated approach.
  • You might hire some JavaScript hackers which are not pretty familiar with the Java tooling landscape.

I present here an approach, which builds the Java and JavaScript stuff separately and merges it together at the end. The steps are:

  1. On the JavaScript side:
    1. Create separated HTML5/JavaScript modules with Grunt and Bower as build and packaging system
    2. Use a Grunt compress task to create Bower compatible ZIP file as the last build step
    3. Use a custom Grunt task to generate a Maven POM file, which just includes a build-helper:attach-artifact goal to turn the Bower ZIP file into a Maven artifact
    4. Add the project as dependency to another Bower module by just stating the full URL to the generated ZIP file. Which could of course be an URL of a Nexus or Artifactory repository.
  2. On the Build Server:
    1. On your build server run mvn install in the folder of the generated POM to install the Bower ZIP as Maven artifact in your local repository
    2. Install the artifact on Nexus or Artifactory
  3. On the Java side:
    1. Add the ZIP as dependency and unpack it into your WAR module in the package phase

Create the HTML5/JavaScript projects

To make things a bit more interesting we’re going to creating two Bower modules: A Theme, with just a single CSS file, and a AngularJS App.

The Theme project contains just a css/theme.css and a bower.json configuration like this:

  "name": "myTheme",
  "version": "1.0.0-SNAPSHOT",
  "main": "theme.css",
  "dependencies": {
    "bootstrap": "~3.1"

In package.json we need to add grunt-contrib-compress as a development dependency:

  "dependencies": {
  "devDependencies": {
    "grunt": "~0.4.1",
    "bower": "~1.3",
    "grunt-contrib-cssmin": "~0.7.0",
    "grunt-contrib-compress": "~0.7.0"
  "scripts": {
    "postinstall": "bower install"
  "engines": {
    "node": ">=0.8.0"

In Gruntfile.js we have to add a compress task and a custom task to generate a pom.xml:

module.exports = function (grunt) {
   cssmin: {
    combine: {
    files: {
      'dist/theme.css': ['css/theme.css']
  compress: {
    main: {
     options: {
       archive: 'deploy/'
      files: [
        { expand: true, cwd: 'dist/', src: ['**'], dest: '/'},
        { src: ['bower.json'], dest: '/'}
  grunt.registerTask('mavenpom', function () {
   var bowerJson = grunt.file.readJSON('bower.json');
   grunt.log.writeln('Determined project version: ' + bowerJson.version);
   var pom = '<?xml version="1.0" encoding="UTF-8"?>\n' +
     '<project xmlns=""' +
     ' xmlns:xsi=""' +
     ' xsi:schemaLocation="">\n' +
     '  <modelVersion>4.0.0</modelVersion>\n' +
     '  <groupId>at.nonblocking.bower</groupId>\n' +
     '  <artifactId>myTheme</artifactId>\n' +
     '  <packaging>pom</packaging>\n' +
     '  <version>' + bowerJson.version + '</version>\n' +
     '  <build>\n' +
     '    <plugins>\n' +
     '      <plugin>\n' +
     '        <groupId>org.codehaus.mojo</groupId>\n' +
     '        <artifactId>build-helper-maven-plugin</artifactId>\n' +
     '        <version>1.8</version>\n' +
     '        <executions>\n' +
     '          <execution>\n' +
     '            <id>attach-artifacts</id>\n' +
     '            <phase>package</phase>\n' +
     '            <goals>\n' +
     '              <goal>attach-artifact</goal>\n' +
     '            </goals>\n' +
     '            <configuration>\n' +
     '              <artifacts>\n' +
     '                <artifact>\n' +
     '                  <file>deploy/</file>\n' +
     '                   <type>zip</type>\n' +
     '                </artifact>\n' +
     '              </artifacts>\n' +
     '            </configuration>\n' +
     '          </execution>\n' +
     '        </executions>\n' +
     '      </plugin>\n' +
     '    </plugins>\n' +
     '  </build>\n' +
     '</project> ';
   grunt.log.writeln('Writing deploy/pom.xml');
   grunt.file.write('deploy/pom.xml', pom);
  grunt.registerTask('default', [

Please note, the POM artifactId and version is taken from bower.json!

If we now execute:

npm install
cd deploy
mvn install

a Bower module is generated and installed it as Maven artifact.

For the actual app we can use Yeoman to generate a AngularJS hello world example:

npm install -g yo
npm install -g generator-angular  
yo angular

And should get a structure like this:


Let’s say, the myTheme project is already on an artifactory repository, then you can add it as dependency like this:

  "name": "myApp",
  "version": "1.0.0-SNAPSHOT",
  "dependencies": {
    "angular": "1.2.16",
    "angular-resource": "1.2.16",
    "angular-cookies": "1.2.16",
    "angular-sanitize": "1.2.16",
    "angular-route": "1.2.16"
    "myTheme": "http://myserver/artifactory/release/at/nonblocking/bower/myTheme-1.0.0-SNAPSHOT/"

Furthermore you have to add the same compress and mavenpom task to Gruntfile.js as for the myTheme module.

Create the Jenkins Jobs

On Jenkins we will need two jobs to build myTheme and myApp. Just create two free-style projects, configure the source code management section accordingly and add node.js to the PATH:


Then create two build tasks for each job:

  1. An Execute Shell build step to start the grunt default task
  2. And a Maven step to install the generated bower ZIP locally in your repository


The last step on Jenkins is to publish the ZIP artifact in your remote repository:

Create the Java WAR module

The configuration of the WAR module is straight forward: Add the ZIP files as dependencies and use the dependency plugin to unzip it into the target/projectName folder:



That’s it! Now your HTML5 front-end team can work completely independently from your Java back-end team. And both teams will use the existing Maven repository.

7 thoughts on “Bringing the Java and Javascript world together

  1. It’s hard to find your articles in google. I found
    it on 12 spot, you should build quality backlinks , it will help you to increase traffic.
    I know how to help you, just search in google – k2 seo tips and tricks

  2. Great read, will be testing this workflow out. Have you worked with a scenario where the Java team is also augmenting the HTML such as required in using something like Tymeleaf?

  3. Hi, can you please do a small step by step tutorial with
    1 packaging and deploying angularjs app on tomcat server
    2 deploying java webservice app on jboss
    3 Now request from the browser goes to angular on tomcat and this communicates to web service on jboss

  4. As a pure Java Shop We are using the complete integrated approach and hit the share UI components road. Thanks for this blog post it really gives great insight,

  5. It’s been a while now since you wrote this so I’m wondering if grunt has now got some sort of module to make that step with the maven pom.xml easier? (Don’t know grunt at all)

Leave a Reply

Your email address will not be published. Required fields are marked *