Hello
$ mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:resolve-plugins
...
Downloading:
https://repo.maven.apache.org/maven2/com/puppycrawl/tools/checkstyle/8.29/checkstyle-8.29.pom
Downloaded:
https://repo.maven.apache.org/maven2/com/puppycrawl/tools/checkstyle/8.29/
421)
28.11.2020, 20:57, "Anton Vodonosov" :
> MDEP-409 was fixed by passing reactor projects as the 3rd parameter
> to dependencyGraphBuilder.buildDependencyGraph:
> https://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/main/java/org/apache/maven/p
k Stolwijk
>
> ~~~ Try to leave this world a little better than you found it and, when
> your turn comes to die, you can die happy in feeling that at any rate you
> have not wasted your time but have done your best ~~~
>
> Lord Baden-Powell
>
> On Sat, Nov 28, 2020 at 6:46 AM
s the default for
> that repo.
>
> Am 25.11.2020 um 22:18 schrieb Anton Vodonosov:
>> When I run `mvn -X dependency:tree` in the root directory
>> of redisson (https://github.com/redisson/redisson), I get the below error.
>>
>> Question: why does maven tries to reso
When I run `mvn -X dependency:tree` in the root directory
of redisson (https://github.com/redisson/redisson), I get the below error.
Question: why does maven tries to resolve the `redisson` dependency
of the `redisson-all` module using a remote repository, when `redisson`
is a part of the reactor?
B.jar from your local repo,
> and resort to checking your remote repo (e.g. Maven Central) if it's not
> there. But if you omit the `-pl A` part, Maven will build B, then build A
> using B.jar.
>
> Essentially, the plugin I linked to determines the project list based on
Thank you, it works.
17.07.2020, 01:34, "Anthony Whitford" :
> You will want to use settings.xml.
> See https://maven.apache.org/settings.html
> <https://maven.apache.org/settings.html>
>
>> On Jul 16, 2020, at 3:31 PM, Anton Vodonosov wrote:
>>
>&
Is it possible to specify URL of artifact server
on command line (or somehow else externally to the project pom.xml)?
For example, if I want to build a 3rd party project, and want it through my
proxying
artifact server, without modifications in the project's pom.xml file.
-
Hi, thank you for the responses.
Currently I was trying on a multi-module project, and
mvn dependency:tree
fails complaining about the impossibility to find artifact for one of the
reactor modules, but
mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:tree
works. I've tried
Hello,
Can anyone explain why "mvn dependency:tree" fails if the project artifacts are
absent in ~/.m2?
Also, if I place an empty, dummy file in place of the artifact in ~/.m2
dependency:tree starts working.
This means the artifact content is not needed for that operation.
Can this be worked a
Can this work also allow arbitrary property expression in a module ?
Currently, this practice is discouraged because the deployed pom with property
expression is meaningless.
The flatten-maven-plugin can produce correct poms for deployment,
with all properties resolved; despite maven prints the ha
04.02.2020, 23:32, "Jason Young" :
>
> Not what you're looking for, but maybe useful: We use one plugin that will
> skip whole projects that have not changed WRT a given Git branch:
> https://github.com/vackosar/gitflow-incremental-builder. With careful
> configuration, this is an effective shor
Ha, only after completing the script (even though a slow one)
I discovered that maven rebuilds modules even if
an artifact of the same version already exists in artifact
repository.
I hoped maven, in case a non -SNAPSHOT artifact
found in an artifact repository will just use it
and won't build the
Thomas Broyer, Enrico Olivelli,
I consider the whole directory where the module's
pom.xml resides, excluding the target/ dir,
as the input, and the final module artifacts as
the output.
Even if some plugins allow sources outside the
pom.xml's directory (out of curiosity, is it possible?),
it is a
03.02.2020, 00:15, "Enrico Olivelli" :
> (Apologises for top posting )
>
> This thread is about a bunch of requested features (cache and parallel
> executions of mojos) that we have been discussing on dev@ mailing list.
> As said in this thread the first show stopper for Maven is that we do not
Hello.
In order to speed up the build of a multi-module project, I'd like to reuse
artifacts of modules that haven't changed.
Manual versioning is tedious and error-prone.
Is it possible to automatically assign versions to modules computed as a
hash-of( hash-of(module sources) + hashes of all d
I want, for unchanged parts of the project, to reuse artifacts
produced by previous builds, and only rebuild the changed parts.
Imagine a project with hundreds of modules stored in a single
git repository, whose full build with tests takes 3 hours.
A developer creates a ticket branch, changes cou
Hello.
In order to speed up the build of a big multi-module project,
I'd like to reuse the artifacts of modules that haven't changed.
Manual versioning is tedious and error-prone.
Is it possible to automatically assign versions so that
versions only change if module sources or dependencies change
18 matches
Mail list logo
