Disabling a Surefire/Failsafe in a particular module is easy but it won't
gain the performance so much if you do not analyse the relations between
classes and the test.
If you analyse the relations then you can easily fetch the list of the
tests in -Dtests or in the included/excludedTests. So
There are multiple possible incremental support:
1. Scm related: do a status and rebuild downstream reactor
2. Full and module build graph: seems it is the one you target, ie bypass
modules without change. Note that it only works if upstream graph is taken
into account.
3. Full build: each mojo
In theory, the incremental compiler would make it faster.
But this can be told only if you present a demo project with has trivial
tests taking much less time to complete than the compiler.
In reality the tests in huge projects take significantly longer time than
the compiler.
Some developers say
Hi there,
just a shot in a dark: Have you tried any of the existing stuff, like
Takari Lifecycle before modding Maven itself? (
http://takari.io/book/40-lifecycle.html)
Thanks,
T
On Fri, Sep 13, 2019 at 10:46 PM Maximilian Novikov <
maximilian.novi...@db.com> wrote:
> Hi All,
>
>
>
> *We want
Hi All,
We want to create upstream change to Maven to support true incremental build
for big-sized projects.
To raise a pull request we have to pass long chain of Deutsche Bank's internal
procedures. So, before starting the process we would like to get your feedback
regarding this feature.
I'll be offline for about 2 weeks, but I guess nobody else has enough
knowledge to verify this...
Robert
On Fri, 13 Sep 2019 21:39:49 +0200, Gabriel Belingueres
wrote:
Hi!
Is there any chance to merge PR for MSHARED-817 [1]?
I would need that change in place as base to make a final
Hi!
Is there any chance to merge PR for MSHARED-817 [1]?
I would need that change in place as base to make a final commit for
MSHARED-801 [2].
[1] https://github.com/apache/maven-artifact-transfer/pull/2
[2] https://github.com/apache/maven-artifact-transfer/pull/1
Kind regards,
Gabriel
@Dan Tran use 'deployAtEnd':
org.apache.maven.plugins
maven-deploy-plugin
someVersion
true
https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html
Maybe you'd want to deployAtEnd?
https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
On Fri, Sep 13, 2019 at 12:03 PM Dan Tran wrote:
> Looks like I need to clear thing a little bit
>
> Assume I have a reactor of few hundreds of maven modules and my CI
> build
Looks like I need to clear thing a little bit
Assume I have a reactor of few hundreds of maven modules and my CI
build deploys snapshots, first few good builds, each module deployed to
maven repository have same snapshot number
Once we encounter a build failure at a module, the snapshot number
Dan,
Are you running a single 'mvn deploy' or do you have multiple runs?
I have never seen weird behaviours in multi module projects
Cheers
Enrico
Il ven 13 set 2019, 08:19 Dan Tran ha scritto:
> Hello, Maven dev
>
> any suggestion/thoughts on this issue are very much appreciated
>
> Regards
>
Hello, Maven dev
any suggestion/thoughts on this issue are very much appreciated
Regards
-D
On Wed, Sep 11, 2019 at 7:06 PM Dan Tran wrote:
> Hello Maven Users and Development Team
>
> Currently, artifact deployed as snapshot at Maven repository has the
> following format
>
>
12 matches
Mail list logo
