grunt stop maven package

[Merguez22]

I use Windows 7, Maven 3.0.5 and Yeoman-maven-plugin 0.2-SNAPSHOT.
When i do a "mvn clean package" on the "yeoman-maven-samples" the packaging is blocked after "karma:unit" is completed. The WAR is not generated.

The java process is still running.

[trecloux]

Could you please :

• Provide me you node version
• Test a direct launch of "grunt test" and "grunt build" from the "yo" folder ?

[Merguez22]

nodeJS version : v0.10.22

direct launch of "grunt test" and "grunt build" pass with success

[tomikat]

I'm having the same issue with node v0.10.20, Windows 8.1 and Maven 3.0.4. Maven build hangs right after "grunt build" phase. Edit: Using yeoman-maven-plugin v0.1.

Running "grunt test" and "grunt build" on command line exists successfully.

[ojacquemart]

Same problem here.
Node version: v0.10.20
Karma version: v0.10.5

After '←[32mDone, without errors.←[39m', it seems like the node process used to launch the tests is not killed.

[trecloux]

Are you running windows too ?

On Tue, Nov 26, 2013 at 3:05 PM, Olivier Jacquemart <
notifications@github.com> wrote:

Same problem here.
Node version: v0.10.20
Karma version: v0.10.5

After '←[32mDone, without errors.←[39m', it seems like the node process
used to launch the tests is not killed.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-29294310
.

Thomas Recloux

[ojacquemart]

Yep, running on windows at work, unfortunately.

[trecloux]

Hi Guys,

Sorry for the delay.

I tested it on a Windows VM running Windows 7, Java 1.7.0_45, Node 10.0.22
=> No issue

Did you run it from windows command line ?

[ojacquemart]

I can't reproduce the issue anymore 👍
It was maybe a windows issue and yes I ran it from the command line.

[jmiddleton]

I'm facing the same issue on a Macbook with Java 1.7.0_45, Node 10.0.23. If I run grunt install, it works but from maven it gets blocked after the following:

Done, without errors.

Execution Time (2013-12-15 03:54:18 UTC)
concurrent:test 1s ▇▇▇▇▇▇▇▇▇▇▇ 24%
autoprefixer:dist 85ms ▇ 2%
concurrent:dist 2s ▇▇▇▇▇▇▇▇▇▇▇▇▇ 30%
autoprefixer:dist 77ms ▇ 1%
copy:dist 181ms ▇▇ 3%
uglify:generated 2s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 37%
Total 5s

[jdubois]

Same issue here...
Mac OS X, Java 1.7.0_45, Node 10.0.23, Maven 3.1.1

This is really strange:

• Everything was working perfectly yesterday
• @jmiddleton submitted the bug on JHipster, so I created a new test project
• And now it's all broken :-(

At least I can confirm the issue...

If you want to test it's easy:

npm install -g generator-jhipster
yo jhipster
mvn jetty:run -Pprod

[trecloux]

I can reproduce it with a jhipster generated app, headlamp switched on.

[trecloux]

The issue can be reproduced by launching grunt directly with the --no-color option.

Temporary workaround : do not use the time-grunt task, the issue seems to be caused by the combination of --no-color and time-grunt.

[trecloux]

I submited a pull request to the time-grunt project. sindresorhus/time-grunt#20

[jdubois]

So the issue is with time-grunt 0.2.4 which was released last night... which explains why it was working yesterday!