The Maven team is pleased to announce the release of the Apache Maven
Checkstyle Plugin, version 2.12.1
Generates a report on violations of code style and optionally fails the build
if violations are detected.
http://maven.apache.org/plugins/maven-checkstyle-plugin/
You should specify the
I am trying to filter my jboss-web.xml but am having problems. For sure,
the file is getting processed because ${project.version} is substituted
just fine, but any of my custom properties are not. It doesn't seem that
the war plugin is paying attention to my list of filters.
build
filters
I think my problem is regarding these open issues:
http://jira.codehaus.org/browse/MWAR-301
http://jira.codehaus.org/browse/MWAR-305
I did a debug dump of my build and noticed that my filters are definitely
not being included in the list of available properties.
Unless someone else can give
OK, I solved this. I've seen others on the web who complained of similar
issues -- and the JIRA tickets may be related -- but here's the answer for
posterity:
The filters/filter tags need to be in the configuration of the
maven-war-plugin and NOT your build. The former is for your web
resources;
Hi everyone,
I am not sure if some of you met this problem before, we have some smoke test
in Jenkins sever, which will run some test case through maven sure fire plugin,
version is 2.17
But it will always throw an exception like this:
java.lang.NullPointerException
at
Is there any downside to using forkModenever/forkMode?
--
View this message in context:
http://maven.40175.n5.nabble.com/ForkedBooter-in-2-2-1-does-not-honor-MAVEN-OPTS-tp5764410p5791911.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Yes, it does not isolate your tests from your main maven build. So if for
example your tests require too much memory, the OOME will kill the whole
maven build.
BTW, as maven 2.x is in the title, you should be aware it's now
deprecated/end of life.
Cheers
Le 25 avr. 2014 03:22, victropolis
It would appear that testng is not reporting the throwable that is cause of
the failure. You might want to try a few different testNG versions to see
if this is a recently introduced regression.
Surefire should probably not NPE on this, but gaining some insight into the
root cause is probably a
