Hi,
I'd recommend you to use the fronend-maven-plugin [1] for your use case.
This plugin installs and configures npm for you, so your build is
regardless of external tools.
Best regards,
Sandra
[1]https://github.com/eirslett/frontend-maven-plugin
Am 29.01.2018 um 22:02 schrieb yossi
Plugin has a goal named update-properties. But it requires
>> that the properties are used in the dependency definition. I search for
>> something like 'set-property -Dname=propertyName
>> -Dvalue=newValueForProperty'. Do you know a Maven Plugin that supports this
>> use case?
>>>
&g
Hi,
You have to add the junit dependency in your section.
But I would recommend you to move the tests to src/test/java.
Best regards,
Sandra
Am 30.08.2015 um 15:40 schrieb 建文:
> I add junit4.8 in my project, and the test java classes are in
> src/main/java not src/test/java(i know it's not
Hi,
you can use the property -Dclassifier. For the Linux build I would use
-Dclassifier=linux and for the Windows build -Dclassifier=win.
Best regards,
Sandra
Am 29.06.2015 um 09:53 schrieb Francois MAROT:
Hello all,
I'm in the process of converting an existing build to Maven. I have
2
Hi,
the website for appassembler-maven-plugin doesn't follow the pattern.
Its current website is
http://www.mojohaus.org/appassembler/appassembler-maven-plugin/
Greetz,
Sandra
Am 08.06.2015 um 09:24 schrieb Baptiste Mathus:
Yes, MOJO@Codehaus project was renamed MojoHaus.
So, basically,
=appassembler%20maven%20plugin)
Cheers
2015-06-08 21:27 GMT+02:00 Sandra Parsick spars...@web.de:
Hi,
the website for appassembler-maven-plugin doesn't follow the pattern.
Its current website is
http://www.mojohaus.org/appassembler/appassembler-maven-plugin/
Greetz,
Sandra
Am 08.06.2015 um
I would move the integration tests from myproject-api-impl to the war module
Regards,
Sandra
Am 13.03.2015 um 09:18 schrieb Martin Gütlein:
The failsave integration tests do not run. They should be applied to the
whole service (war). But they are defined within a module
(myproject-api-impl)