npm tasks for grunt-maven-plugin.
grunt-maven-plugin NPM tasks power Maven+Grunt integrated workflow. These tasks depend on properties file produced by grunt-maven-plugin, which contains paths and options derived from projects pom.xml.
Add plugin dependency to your package.json:
Load tasks in Gruntfile:
This tasks role is to copy raw sources from Maven webapp sources to
target-grunt, where Grunt tasks will be executed.
In your project's Gruntfile, add a section named
mavenPrepare to the data object passed into
List of patterns that will be evaluated using minimatch to choose resources that will be copied from Maven webapp to target-grunt.
mavenDist task copies artifacts produced by Grunt (less -> css, minified JS) from
target-grunt to Maven WAR directory.
Name of WAR directory, residing in
/target/, to which all deliverables will be copied.
List of patterns that will be evaluated using minimatch to choose deliverables that
will be copied from
target-grunt/dist and to WAR.
Default: Directory where gruntfile is located
Deliverable patterns will be matched relative to this path, and all returned filepaths will also be relative to this path.
Name of directory residing in
target-grunt, where all deliverables will be copied.
Using maven* tasks
Each defined task that wants to operate on resources from Maven, should start with
mavenPrepare and end with
- prepare environment in
- run all Grunt specific tasks in
- copy deliverables to WAR
grunt-contrib-watch can be very useful to create good development environment, just register whatever task
you should need to run on resources change, using properties generated by grunt-maven-plugin to obtain watch path:
gruntMavenProperties.filesToWatch evaluates to
/src/main/webapp/statics_dir/**. If you need to exclude some resources from
being watched (although you probably shouldn't need to), use
gruntMavenProperties.directoryToWatch. This is simply path
to directory without globing pattern appended, in our case:
grunt-maven-plugin NPM tasks are published under Apache License 2.0.