Hi Robert,
thanks for you reply. I'll keep an eye out for these improvements.
Another obstacle to my use case is that when running
$ mvn package javadoc:aggregate-jar install
the install phase doesn't continue where package finished, instead it
starts over.
Is there a way to tell maven to run
Hi Team,
While creating a maven project in Eclipse (Oxygen 3A). we are getting the below
error ion pom.xml file.
[cid:image001.png@01D5DB4A.8DE781C0]
With below error description:
Errors occurred during the build.
Errors running builder 'Maven Project Builder' on project Name.
Could not
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
The Maven team is pleased to announce the release of the Apache Maven
PMD Plugin, version 3.13.0
A Maven plugin for the PMD toolkit, that produces a report on both code
rule violations and detected copy and paste
fragments, as well as being able to fail the build based on these metrics.
Hi Jon,
it is bothering me for a while that Maven is not yet capable to see that a fork
is not required (in most cases) when it is executed as part of a lifecycle.
Introducing x-no-fork goals is a fast workaround, but it is probably time to do
this properly.
Also plugins should be improved to
The Apache Maven team is pleased to announce the release of the Maven Parent
POMs Version 34.
Maven Parent POMs include Maven Parent POM itself, but also Maven Plugins
Parent POM, Maven Shared Components Parent POM, Maven Skins Parent POM and
Maven Doxia Tools Parent POM.
Hi,
I think I found the reason.
In the verify phase, I am executing errorprone, which uses the
maven-compiler-plugin.
Although I compile to target/classes-ep (instead of target/classes),
somehow this seems to un-append artifacts.
I think that the execution of an addition compilation should not
Hi all,
since today my ear-plugin configuration does not work anymore and
stops with an exception.
I pull in a dependency (type war) from another module in the same
reactor. I also pull the same dependency in again with a classifier
and another type to be used with the maven-assembly-plugin.
Hi Benjamin,
thank you for your answer. But I don't see any option to check that
the artifact are attached in the verify plugin.
The problem is that the files can be present in the target folder but
not attached if you have not run the goal in the same maven invocation
as the one doing "install".