Maven / JavaScript Project

Take a look at the frontend-maven-plugin. This is useful if you want to bundle scripts with a maven artefact.

I haven't needed to use this because my javascript code has been an entirely separate deployable (decoupling and all that). So this is a good use case for gulp. Take a look at the gulpfile.js from hottowel.

First take a look at the build task and its dependencies:

/**
 * Build everything
 * This is separate so we can run tests on
 * optimize before handling image or fonts
 */
gulp.task('build', ['optimize', 'images', 'fonts', 'test-server'], function() {
    log('Building everything');

    var msg = {
        title: 'gulp build',
        subtitle: 'Deployed to the build folder',
        message: 'Running `gulp serve-build`'
    };
    del(config.temp);
    log(msg);
    notify(msg);
});

These should do most of the things you want. There are also environment specific gulp tasks:

gulp serve-dev
gulp build

There are a lot more in there so take a read through.

I've also worked on java + angular projects and it was handy for deployment and consistent with the java/maven approach to create artefacts for the javascript code that can be stored on nexus and fetched for deployment when needed.

The artefact for the javascript code is just a zip file which I create with the following gulp task (ignoring directories and files with ! in front of the directory name):

/**
 * Create a versioned artefact
 */

    gulp.task('generate-artifact', function() {
        var filename = getFilename();
        return gulp
            .src([
                './**/*.*',
                '!artifacts/',
                '!artifacts/**',
                '!build/',
                '!build/**',
                '!node_modules/',
                '!node_modules/**',
                '!bower_components/',
                '!bower_components/**'
                ])
            .pipe($.tar(filename + '.tar'))
            .pipe($.gzip())
            .pipe(gulp.dest('./artifacts/'));
    });

Then to deploy to nexus using the nexus-deployer plugin:

/**
 * Deploy release to nexus
 */ 
gulp.task('deploy-release', ['clean-pomdir'], function(cb) {
    var deployer = require('nexus-deployer');
    var filename = getFilename();
    var pkg = require('./package.json');

    log('Retrieving artifact ' + filename + '.tar.gz' + 'from artifacts dir');
    log('Deploying version ' + pkg.version + ' of ' + pkg.name);

    var release = {
        groupId: 'my.group.id',
        artifactId: 'my-artefact',
        version: pkg.version,
        packaging: 'tar.gz',
        auth: {
            username: args.username,
            password: args.password
        },
        pomDir: config.pomDirReleases,
        url: 'http://path-to-nexus.repo',
        artifact: './artifacts/' + filename + '.tar.gz',
        noproxy: '',
        cwd: ''
    };

    deployer.deploy(release, cb);
});

There are a few custom methods and config things in there too: the great yargs module to pass in username and password as command line arguments; convenience method in gulpfile.js to get the filename:

function getFilename() {
    var pkg = require('./package.json');
    var filename = pkg.name + '_' + pkg.version;
    return filename;
}