Good questions. First of all, this plugin is CI-agnostic, but it does
require the project to exist in a `git` repository, whether that is in CI
or on your machine. Check the github page I linked to for more instructions
on how it determines what projects in a reactor are considered "changed"
and
Well almost, as far as I understand it's having aggregate-jar-no-fork and
binding it to a submodule that is after all other submodules in the build
plan (a "distribution"- like artifact, or an aggregator that is not the
parent). Unfortunately this changes the artifact in which clients look up
the
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
Well, so we're back to the missing javadoc:aggregate-jar-no-fork :)
On 4-2-2020 19:38:43, Jon Harper wrote:
Hi Robert, thanks again for your answers.
I can't bind the javadoc:aggregate-jar goal to the package phase because
goals with "@Mojo ( aggregator = true )" are only executed once
I have seen similar issues if the maven plugin repository could not be
contacted.
On Tue, Feb 4, 2020 at 6:45 AM Roy, Arnab wrote:
> Hi Team,
>
>
>
> While creating a maven project in Eclipse (Oxygen 3A). we are getting the
> below error ion pom.xml file.
>
>
>
>
>
> With below error
It seems Maven itself never omits re-doing anything except for downloading
artifacts from a remote repository. The command you give to Maven and the
configuration of your projects dictates what it will do, no matter what
happened in the previous build. You _can_ omit projects in a multi-module
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
Hi Robert, thanks again for your answers.
I can't bind the javadoc:aggregate-jar goal to the package phase because
goals with "@Mojo ( aggregator = true )" are only executed once (instead of
once per module) if they are invoked from the command line.
Cheers,
Jon
Le mar. 4 févr. 2020 à 18:48,
Looks like a bug, please create a ticket for it at
https://issues.apache.org/jira/browse/MNG
thanks,
Robert
On 4-2-2020 09:20:12, Jon Harper wrote:
Also a "funny" thing is that running an aggregator mojo between 2
phases in a multimodule project shows the wrong build step numbers:
(In this
Hi Jon,
it is not possible so start a lifecycle from the middle.
In case of 'mvn package javadoc:aggregate-jar install' you should bind the
javadoc:aggregate-jar to the package-phase, and now you can run 'mvn install'.
If you don't want to run it all the time, consider putting the
Also a "funny" thing is that running an aggregator mojo between 2
phases in a multimodule project shows the wrong build step numbers:
(In this example I generated a quick project setup with mvn archetype:
a parent pom with 2 children)
# javadoc:jar is *not* an aggregator mojo, this looks correct
11 matches
Mail list logo
