Was happy too soon.
If I move the invoker plugin profile to my company-parent pom, then all
steps to remove the recursion problem make it not work anymore for my
multimodule build :(
-
To unsubscribe, e-mail: users-unsubscr..
>> 1. needs to be bound in a non-default profile
>> 2. needs to have false to stop the child
>> projects running invoker
>> 3. need to set invoker.nonRecursive or invoker.nonRecursive.N where N
>> is the invokation you want only on the root pom.
Now invoker plugin is doing what I want now!
Thanks
>> Please always keep replies on the list for future queries.
Sorry, answered to the wrong mail, will keep an eye on it in the future.
>> Maven invoker plugin could do what you want... you would bind it in a
>> profile to e.g. the validate phase of the lifecycle. then you can use
>> defaultGoal as
>> Bind the goals you want to run to chosen phases.
This unfortuntaly is not possible in a multimodule build, let's take the
dashboard plugin as an example:
The dashboard:dashboard needs to run AFTER the full site has been created
in a multimodule build (because it needs access to all checksty
To generate a site, using the clover and dashboard plugin currently I need
to use the following command-line:
mvn clover2:setup site clover2:aggregate clover2:clover
dashboard:dashboard site:deploy
(this is to overcome some problems with the site-plugin, which in
multi-module builds seems to h
>> You should use the maven-failsave-plugin instead of the
maven-surefire-plugin.
>> The maven-failsave-plugin doesn't fail the build, but the test failures
will be in Your reports.
This looks much like what I want! So if people insist on a dedicated
HTML-JUnit report I can leverage this plugi
>> You should use the maven-failsave-plugin instead of the
maven-surefire-plugin.
>> The maven-failsave-plugin doesn't fail the build, but the test failures
will be in Your reports.
This looks much like what I want! So if people insist on a dedicated
HTML-JUnit report I can leverage this plugi
>> another idea could be to call Maven with the --fail-at-end (-fae)
>> option. But this doesn't seem to work with Maven 3 anymore.
Even if 'fail-at-end' was working: wouldn't the artifacts still be
deployed, when running 'mvn deploy' ?
>> What is the point of JUnit failure reports in CI environment? It's
absolutely un-acceptable situation when your source codebase contains a
defect in "trunk". It's not a matter of reporting any more, but of an
immediate action.
>> If you still need your build to be valid with defects inside (u
Well,
I don't consider 'use another tool to overcome your maven problem' as a
valid answer. There are reasons we chose TeamCity over Jenkins.
TeamCity is catching the JUnit failures as well, but I need to care about
any other report as well.
And right now I'm not able to configure maven in a w
Hi Yegor,
thanks for taking the time to share your thoughts.
>>The only option you have is to run your project twice in your CI
environment
I'm afraid that is no option for us. I planned to use Maven to reduce
build-times (right now dependent projects are checkouted and compiled over
and over
Hi there,
I'm in the process of migrating our Ant-based CI environment to Maven.
After searching mailing lists and google for hours I'm near giving up but
hope you are able to help.
Actually we want to do quite simple things:
1) the buildserver should regularly deploy our project to a reposito
Hi there,
I'm having a multimodule project with flat directory layout
./root
./module1
The generated site then also is in a flat layout directory:
./site/root
./site/module1
(using help:effective-pom also shows that these are the automatically
generated distribution-urls for the childs, so the
13 matches
Mail list logo
