Hi Robert,
On 8/6/16 3:42 PM, Robert Scholte wrote:
Hi Karl Heinz,
I think what you should do is add -am and maybe even -amd to the
arguments. There should be no reason to run mvn install, even when using
the incremental module builder.
The more I'm thinking about this I come to the conclusio
Hi Karl Heinz,
I think what you should do is add -am and maybe even -amd to the
arguments. There should be no reason to run mvn install, even when using
the incremental module builder.
Robert
On Sat, 06 Aug 2016 15:38:44 +0200, Karl Heinz Marbaise
wrote:
Hi Robert,
On 8/6/16 3:22 PM
Hi Robert,
On 8/6/16 3:22 PM, Robert Scholte wrote:
Hi Karl Heinz,
This all sounds like repository policies[1], so something that should be
part of Aether.
Disabling such repositories should prevent them from downloading.
(assuming --offline is not an option)
From a plugin of MavenProject point
Hi Karl Heinz,
This all sounds like repository policies[1], so something that should be
part of Aether.
Disabling such repositories should prevent them from downloading.
(assuming --offline is not an option)
From a plugin of MavenProject point of view I'm not interested in the
logic behind
Hi,
If I do a mvn install with a project all artifacts are being installed
into my local cache..
The question I have:
Can I somehow identify if an artifact is already been in my local cache
or not (within a Maven plugin or extension)?
Something like:
if (artifact is in local cache) {
