Hi Jon,
I think you could use the verifier-plugin for checking file existence.
https://maven.apache.org/plugins/maven-verifier-plugin/verify-mojo.html
Am So., 2. Feb. 2020 um 17:55 Uhr schrieb Jon Harper :
>
> Hi list,
>
> I would like to use maven-enforcer-plugin to ensure that javadocs are
>
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
(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
have a clear definition of input and outputs for
Le dim. 2 févr. 2020 à 17:48, Anton Vodonosov a
écrit :
> 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
Hello Anton,
If I understand you correctly, you do not want to build all modules of the
maven build, only those that has changed.
As long as you are building in development shell or IDE the result of last
build is still there and maven will only recompile sources that are newer than
their
Hi,
Unfortunately release 3.0.1 never got published due to a failed vote in August
last year:
https://lists.apache.org/list.html?d...@maven.apache.org:lte=12M:%5BVOTE%5D%20Release%20Maven%20Project%20Info%20Reports%20Plugin%20version%203.0.1
Hi list,
I would like to package a multimodule project (jar of each submodule)
and then create one aggregated javadoc jar attached to root pom.
The best solution I came up with is using the following command line
$ mvn package javadoc:aggregate-jar
It uses the fact that aggregate-jar is
Hi list,
I would like to use maven-enforcer-plugin to ensure that javadocs are
attached in release mode before installing. That's because I use
$ mvn package javadoc:aggregate-jar deploy
to build, so if someone forgets to call the aggregate-jar goal, the
release will be missing the javadoc.
I
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
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
Hi,
On 01.02.20 16:08, Anton Vodonosov wrote:
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.
Can you explain more in detail what you exactly mean and what kind
11 matches
Mail list logo