-
Notifications
You must be signed in to change notification settings - Fork 867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<triggerfile> #329
Comments
+1 I've the same behavior on v1.6 The problem is here https://github.com/eirslett/frontend-maven-plugin/blob/4f21ed9a467fe407f849356957e2b9c27e5eb972/frontend-maven-plugin/src/main/java/com/github/eirslett/maven/plugins/frontend/mojo/MojoUtils.java#L83-100 My workaround: <execution>
<id>gulp-build</id>
<goals>
<goal>gulp</goal>
</goals>
<phase>generate-resources</phase>
<configuration>
<arguments>build ${frontend.deploy}</arguments>
<triggerfiles>
<triggerfile>Gulpfile.js</triggerfile>
<triggerfile>package.json</triggerfile>
</triggerfiles>
<srcdir>src/main/unused</srcdir>
</configuration>
</execution>
<execution>
<id>gulp-styles</id>
<goals>
<goal>gulp</goal>
</goals>
<phase>generate-resources</phase>
<configuration>
<arguments>styles ${frontend.deploy}</arguments>
<srcdir>src/main/frontend/css/</srcdir>
</configuration>
</execution>
<execution>
<id>gulp-js</id>
<goals>
<goal>gulp</goal>
</goals>
<phase>generate-resources</phase>
<configuration>
<arguments>javascripts ${frontend.deploy}</arguments>
<srcdir>src/main/frontend/js/</srcdir>
</configuration>
</execution>
|
If triggerfile is define and srcdir it isn't any file changed trigger the build. This behavior should be that just triggerfile must trigger the build.
Trigger file does not work for me, it always fire up full build even if the files in trigger file didn't change
version 0.26, execution gulp.
The text was updated successfully, but these errors were encountered: