It is not clear to me what the problem is.
As you shade antlr4 code, and they are only used by your own code,
there's no need for exports or requirements, so I don't see why the
module descriptor would be an issue.
... unless it is a cross-(Maven)module and you need to use these classes
in a
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 3.3.1
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
See the vote[1]
I'll remove the github tag to prevent more confusion
thanks,
Robert
[1]
https://lists.apache.org/thread.html/rb9f899586cf49fefffc291b028a14b5fa8e22797d79d2362bcdfb58c%40%3Cdev.maven.apache.org%3E
-- Origineel bericht --
Van: "Philipp Dallig"
Aan:
The Apache Maven team is pleased to announce the release of the Apache Maven
Enforcer Plugin and Extension, version 3.0.0
The Enforcer plugin is the Loving Iron Fist of Maven and provides goals to
control certain environmental constraints such as Maven version, JDK version
and OS family along
The Apache Maven team is pleased to announce the release of the Apache Maven
Dependency Tree, version 3.1.0
This library contains a tree-based API for resolution of Maven project
dependencies.
https://maven.apache.org/shared/maven-dependency-tree/
You should specify the version in your
In case of modules, javadoc requires a compiles module descriptor, so try 'mvn
compile javadoc:javadoc'
Robert
On 4-6-2021 05:42:11, Alex Orlov wrote:
Hi all,
I have a sample project with two jpms modules. It is a maven project with one
parent and two child modules.
A parent pom:
...
The Apache Maven team is pleased to announce the release of the Apache Maven
Javadoc Plugin, version 3.3.0
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the specified
project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
The Apache Maven team is pleased to announce the release of the Apache Maven
Plugin Tools, version 3.6.1
The Maven Plugin Tools contains the necessary tools to generate rebarbative
content like descriptor, help and documentation. In addition, it provides tools
to write Maven Plugins in
The Apache Maven team is pleased to announce the release of the Apache Maven
JXR Plugin, version 3.1.1
The JXR Plugin produces a cross-reference of the project's sources. The
generated reports make it easier for the user to reference or find specific
lines of code. It is also handy when used
The Apache Maven team is pleased to announce the release of the Apache Maven
Release Plugin, version 3.0.0-M4
(NOTE: This version is still marked as milestone, because not all steps for a
3.0.0 have been finished. That includes removing Maven2 code and deprecated
code plus completing some
The Apache Maven team is pleased to announce the release of the Apache Maven
3.8.1
Apache Maven is a software project management and comprehension tool. Based on
the concept
of a project object model (POM), Maven can manage a project's build, reporting
and documentation
from a central piece of
The Apache Maven team is pleased to announce the first release of the Apache
Maven Scripting Plugin, version 3.0.0
The Maven Scripting Plugin wraps the Scripting API according to JSR223. Add the
scripting engines as dependencies of this plugin on its use.
There's a migration plan for moving plugin from Maven2 to Maven3[1]
As long as these steps haven't been finished, but people expect us to do
releases due to bugfixes or improvements, we must use some pre 3.0.0 as
version, hence the milestones.
For the plugins that are marked as M, most I can
The Parameter annotation only works on the Mojo, not inside the complex object.
What you can do is the following:
private ComplexObject complexObect = new ComplexObject()
@Parameter( property = "acme.name")
private String name;
public void setName( String name ) {
with
NetBeans and did you face a problem? Having steps to reproduce would make
it more real for the NetBeans community to take action.
-jt
po 22. 6. 2020 v 23:18 odesílatel Robert Scholte
napsal:
> Hi,
>
> One of my long standing wishes has made it to the master branch of Maven:
> the suppo
On 25-6-2020 02:03:42, Anton Vodonosov wrote:
Can this work also allow arbitrary property expression in a module ?
Robert Scholte:
Currently only the ci-friendly version placeholders are supported.
Currently, this practice is discouraged because the deployed pom with property
expression
ame parent - the version of the dependency
could be elided if the parent version matched AND that dependency is part of
the reactor.
Robert Scholte:
The parent isn't used to resolve the version. If a dependency is missing a
version, Maven will look up the version by finding the reactor module based on
t
On 23-6-2020 23:20:31, Matthieu BROUILLARD wrote:
Hi Robert,
congrats this looks like a great achievement.
I presume that the consumer pom means the end of the flatten plugin or is
there still some benefit in using flatten plugin?
Robert Scholte:
The flatten-maven-plugin was introduced when
s intended as a base for discussions by Maven developers, users and
related projects, such as IDEs, Repository Managers, CI Servers, etc.
Looking forward for any feedback,
Robert Scholte
Apache Maven project
[1]
https://github.com/apache/maven-integration-testing/tree/master/core-it-suite/src/tes
The Apache Maven team is pleased to announce the release of the Apache Maven
Verifier, version 1.7.2
This library provides a test harness for Maven integration tests.
https://maven.apache.org/shared/maven-verifier/
[https://maven.apache.org/shared/maven-verifier/]
You should specify the
The Apache Maven team is pleased to announce the release of the Apache Maven
Assembly Plugin, version 3.3.0
The Assembly Plugin for Maven enables developers to combine project output into
a single distributable archive that also contains dependencies, modules, site
documentation, and other
The Apache Maven team is pleased to announce the release of the Apache Maven
Verifier, version 1.7.1
This library provides a test harness for Maven integration tests.
https://maven.apache.org/shared/maven-verifier/
[https://maven.apache.org/shared/maven-verifier/]
You should specify the
The Apache Maven team is pleased to announce the release of the Apache Maven
Verifer, version 1.7.0
This library provides a test harness for Maven integration tests.
https://maven.apache.org/shared/maven-verifier/
You should specify the version in your project's plugin configuration:
cuted once (instead of
once per module) if they are invoked from the command line.
Cheers,
Jon
Le mar. 4 févr. 2020 à 18:48, Robert Scholte a
écrit :
> Hi Jon,
>
> it is not possible so start a lifecycle from the middle.
> In case of 'mvn package javadoc:aggregate-jar in
en running
> $ mvn package install
> or even
> $ mvn package package
> everything is done twice.
>
> thanks in advance,
> Jon
>
> On Mon, Feb 3, 2020 at 8:12 PM Robert Scholte wrote:
> >
> > Hi Jon,
> >
> > it is bothering me for a while that Maven
when running
$ mvn package install
or even
$ mvn package package
everything is done twice.
thanks in advance,
Jon
On Mon, Feb 3, 2020 at 8:12 PM Robert Scholte wrote:
>
> Hi Jon,
>
> it is bothering me for a while that Maven is not yet capable to see that a
> fork is not required
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
Try
https://search.maven.org/search?q=fc:com.google.common.util.concurrent.MoreExecutors
On https://search.maven.org/ you can click on Advanced options to see all
possibilities
Robert
On 24-1-2020 20:33:21, Tomo Suzuki wrote:
Hi Maven users,
Does anybody know how to query class names in
My guess is that the problem is not in the pom, but in the commandline.
Looks like your mvn command contains/ends with a character that looks like a
space, but is not.
thanks, Robert
On 7-1-2020 18:30:34, sireindera...@gmail.com wrote:
Adding users group too..
mvn -version
*Apache Maven 3.6.3
Hi,
apart from the awkward project setup (moduleC not pointing to the same parent),
it looks like a potential bug to me.
What Maven does is looking for the dependencies of the listed projects.
You're pointing to the root pom, which has only a dependency on junit, not on
any of the multimodule
The Apache Maven team is pleased to announce the release of the Apache Maven
Artifact Transfer, version 0.12.0
The Maven Artifact Transfer Component is intended as an API to install, deploy
and resolving artifacts in Maven 3.
https://maven.apache.org/shared/maven-artifact-transfer/
You should
The Apache Maven team is pleased to announce the release of the Apache Maven
3.6.3
Apache Maven is a software project management and comprehension tool. Based on
the concept of a project object model (POM), Maven can manage a project's
build, reporting and documentation from a central piece of
If you don't have a repository manager in place to serve your developers (that
is, bound to the internet), then I consider that as a huge risk. Developers
will find other ways to get their libraries, which means you can't know anymore
if they came from a valid and secure location.
A repository
It looks a bit like MRELEASE-798[1] and MRELEASE-962[2]
For the 3.0.0 already a lot of refactoring has been done, so it should be
easier to add such a feature.
I haven't thought about the implementation details, only that some hook or
extension should be able to become part of the release
On Sat, 14 Sep 2019 07:17:16 +0200, Dan Tran wrote:
Still waiting for the maven dev team to chime in if there is possible
solution
Tamás is dev team member :)
I don't know which code is responsible for adding the buildnumer.
Personally I'd like to invest in MNG-5666[1], which should already
, 23 Aug 2019 15:17:23 +0200, Robert Scholte
wrote:
Hi,
The Apache Maven project consist of about 90 (sub)projects. Due to the
small number of volunteers and the huge amount of code to maintain we're
missing enough space to make real progress on all these projects,
including our
Hi,
The Apache Maven project consist of about 90 (sub)projects. Due to the
small number of volunteers and the huge amount of code to maintain we're
missing enough space to make real progress on all these projects,
including our ambitious ideas for the next major version(s) of Maven
Hi,
The vote has passed with the following result:
+1: Anders Hammar, Jesper Udby, Tamás Cservenák, Francois Papon, Gabriel
Belingueres, Karl Heinz Marbaise, Robert Scholte, Tibor Digana
PMC quorum: reached
I will continue with the steps required to retire this library.
On Wed, 07 Aug
+1
On Wed, 07 Aug 2019 21:13:28 +0200, Robert Scholte
wrote:
Hi,
The Apache Maven project consist of about 90 (sub)projects. Due to the
small number of volunteers and the huge amount of code to maintain we're
missing enough space to make real progress on all these projects
As you might have noticed, plugins like maven-surefire-plugin,
maven-failsafe-plugin and maven-dependency-plugin contain ANSI coloring
support, so yes it is possible at mojo-level.
They create a MessageBuilder via MessageUtils[1]. And yes, there are only
a small set of methods available to
Hi,
The Apache Maven project consist of about 90 (sub)projects. Due to the
small number of volunteers and the huge amount of code to maintain we're
missing enough space to make real progress on all these projects,
including our ambitious ideas for the next major version(s) of Maven
The Apache Maven team is pleased to announce the release of the Apache
Maven Toolchains Plugin, version 3.0.0
The Toolchains Plugins allows to share configuration across plugins. For
example to make sure the plugins like compiler, surefire, javadoc,
webstart etc. all use the same JDK for
Hi,
The vote has passed with the following result:
+1: Tibor Digana, James Gough, Sylwester Lachiewicz, Jesper Udby, Enrico
Olivelli, Anders Hammar, Olivier Lamy, gaurav, Francois Papon, Stephen
Connolly, Karl Heinz Marbaise, Brian Fox, Robert Scholte, James Klo, Bernd
Prager
PMC quorum
Hi,
The Apache Maven project consist of about 90 (sub)projects. Due to the small
number of volunteers and the huge amount of code to maintain we're missing
enough space to make real progress on all these projects, including our
ambitious ideas for the next major version(s) of Maven itself.
To
Hi,
The vote has passed with the following result:
+1 (or more): Bruno Borges, Jesper Udby, Anders Hammar, Tibor Digana, Enrico
Olivelli, Manfred Moser, Karl Heinz Marbaise, Olivier Lamy, Sylwester
Lachiewicz, Stephen Connolly, James Gough, Gabriel Belingueres, Hoa Phan,
Robert Scholte
PMC
Hi,
The Apache Maven project consist of about 100 (sub)projects. Due to the small
number of volunteers and the huge amount of code to maintain we're missing
enough space to make real progress on all these projects, including our
ambitious ideas for the next major version(s) of Maven itself.
To
Hi,
The vote has passed with the following result:
+1: Karl Heinz Marbaise, Sylwester Lachiewicz, Manfred Moser, Tibor Digana,
Tamás Cservenák, Hervé BOUTEMY, Robert Scholte
PMC quorum: reached
I will continue with the steps required to retire this library.
On 15-5-2019 22:33:36, Robert
Hi,
The Apache Maven project consist of about 100 (sub)projects. Due to the small
number of volunteers and the huge amount of code to maintain we're missing
enough space to make real progress on all these projects, including our
ambitious ideas for the next major version(s) of Maven itself.
Hi,
The vote has passed with the following result:
+1: Karl Heinz Marbaise, Anders Hammar, Hervé BOUTEMY, Tamás Cservenák, Gabriel
Belingueres, Manfred Moser, Bernd Prager, Enrico Olivelli, Guang Chao, Tibor
Digana, Sylwester Lachiewicz, Robert Scholte
PMC quorum: reached
I will continue
Hi Nick,
it is the latter. The simplest solution is to build and test with the same Java
version and configure all variants with your CI server, especially if you
consider working with multirelease jars ;)
Robert
On 13-5-2019 12:26:42, Nick Stolwijk wrote:
Hello,
I found this old mail about
Hi,
The Apache Maven project consist of about 100 (sub)projects. Due to the small
number of volunteers and the huge amount of code to maintain we're missing
enough space to make real progress on all these projects, including our
ambitious ideas for the next major version(s) of Maven itself.
To
The Apache Maven team is pleased to announce the release of the Apache
Maven Archetype Plugin, version 3.1.0
The Archetype Plugin allows the user to create a Maven project from an
existing template called an archetype.
It also allows the user to create an archetype from an existing project.
Hi,
The vote has passed with the following result:
+1: Anders Hammar, Karl Heinz Marbaise, Manfred Moser, Hervé BOUTEMY, Bernd
Prager , Sylwester Lachiewicz, Robert Scholte
PMC quorem: reached
I will continue with the steps required to retire this plugin.
On 23-4-2019 21:43:18, Robert
Hi,
The Apache Maven project consist of about 100 (sub)projects. Due to the small
number of volunteers and the huge amount of code to maintain we're missing
enough space to make real progress on all these projects, including our
ambitious ideas for the next major version(s) of Maven itself.
To
, Apr 4, 2019 at 11:09 PM Mark Derricutt wrote:
On 5 Apr 2019, at 6:29, Robert Scholte wrote:
If you want to test the jar, you must use the failsafe plugin (or bind
surefire to the integration-test phase)
Can/could failsafe take a toolchain id as config, then you could
configure
additional
t present.
On Apr 4, 2019, at 1:29 PM, Robert Scholte wrote:
The specification you're talking about is the Multi Release Jar, and
especially the last word is important: Jar.
This only works with Jars and with a MANIFEST file containing
Multi-Release: true
Compiling and packaging h
The specification you're talking about is the Multi Release Jar, and
especially the last word is important: Jar.
This only works with Jars and with a MANIFEST file containing
Multi-Release: true
Compiling and packaging has never been the issue, the tricky part is
testing.
If you want to
It seems like you want to improve
https://maven.apache.org/shared/maven-archiver/
thanks,
Robert
On 7-3-2019 14:01:43, Mark Raynsford
wrote:
Hello.
I have a jar file that contains a lot of resources and class files that
compress well, and also a few resources that not only don't compress
well
The Apache Maven team is pleased to announce the release of the Apache Maven
Javadoc Plugin, version 3.1.0
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the specified
project.
https://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your
On Wed, 20 Feb 2019 01:50:14 +0100, dariuscoo...@gmail.com
wrote:
A couple of additional points...
1. It's nice to mark some JIRAs as simple ones for novices to pick up,
but I think such JIRAs aren't motivating enough. If there was a small
"project" of sort, perhaps (only perhaps) one
..."I am trying to reduce the size of fat jar."...
Depending on your project, you might be interested in the
maven-shade-plugin minimizeJar option[1] (e.g. reflection is not detected)
Robert
[1]
https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#minimizeJar
On Wed, 20
each module runs? How would
release:perform differ from normal site?
On Feb 14, 2019, at 10:59 AM, Robert Scholte
wrote:
running 'mvn site' would already show the problem.
One of the things you should do is mention the reports you want to
generate, now all available jxr-reports
running 'mvn site' would already show the problem.
One of the things you should do is mention the reports you want to
generate, now all available jxr-reports are generated, that's probably
more than you want.
not sure what the difference is with the integration test[1] which shows
the
-
[ERROR]
/Users/rgold/projects/eclipse-ee4j/orb-gmbal-pfl/pfl-basic/src/main/java11/org/glassfish/pfl/basic/reflection/Bridge.java:[51,34]
error: cannot find symbol
symbol: class BridgeBase9
[INFO] 1 error
On Feb 12, 2019, at 1:08 PM, Robert Scholte
wrote:
Hi Russ,
There's no way
Hi Russ,
There's no way to configure this, the plugin will do it for you[1]
thanks,
Robert
[1]
https://github.com/apache/maven-compiler-plugin/blob/master/src/main/java/org/apache/maven/plugin/compiler/CompilerMojo.java#L328-L346
On Tue, 12 Feb 2019 18:56:52 +0100, Russell Gold
wrote:
The Apache Maven team is pleased to announce the release of the Apache
Maven Invoker Plugin, version 3.2.0
The Invoker Plugin is used to run a set of Maven projects. The plugin can
determine whether each project execution is successful, and optionally can
verify the output generated from a
01:21, Robert Scholte
wrote:
We might be more explicit in the definition, but it should be
j...@example.com
the mailto: is only an URI scheme for email addresses, but here we
already
know we're working with an email.
Not sure what must done to help you manually fix your team-page.
thanks,
Robrt
O
We might be more explicit in the definition, but it should be
j...@example.com
the mailto: is only an URI scheme for email addresses, but here we already
know we're working with an email.
Not sure what must done to help you manually fix your team-page.
thanks,
Robrt
On Fri, 18 Jan 2019
Please read
https://maven.apache.org/plugins/maven-compiler-plugin/multirelease.html
The tricky thing about MultiRelease JARS is that it only works with JARS,
so surefire won't help you here.
You need to use failsafe for testing with MRJARS.
The concept you-re using is "Single project
Hi,
try to find a plugin which does similar things and have a look at its
sources.
In this case help:evaluate[1]
thanks,
Robert
[1] https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html
On Wed, 26 Dec 2018 22:36:32 +0100, Jochen Wiedmann
wrote:
Hi,
I have written a
amel/camel-core/2.23.0/camel-core-2.23.0.jar.sha1
On Fri, Dec 21, 2018 at 8:23 PM Robert Scholte
wrote:
There are a couple of things happening here.
1. dependencies are checked even though they are downloaded
This ensures that the build doesn't rely on *your* *local* repository.
At
a
On Sat, 22 Dec 2018 23:39:55 +0100, Thomas Broyer
wrote:
https://blog.autsoft.hu/a-confusing-dependency/
Yes, that was the one, thanks!
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands,
In my opinion any commandline argument should *never* have any impact on
the deliverables.
Not by -D arguments nor by activating profiles.
It should always be clear what kind of artifact you're getting.
Reflecting this to your usecase:
mycompanyproject-2.0.0-SNAPSHOT.war, is it based on JPA or
You don't have to worry about parent poms, expectations are these will
stay untouched. Pom optimizations effect non-parent, non-aggregator pom
files.
thanks,
Robert
On Fri, 21 Dec 2018 20:13:48 +0100, Oliver B. Fischer
wrote:
Hi Jörg,
Am 21.12.18 um 18:51 schrieb Jörg Schaible:
There are a couple of things happening here.
1. dependencies are checked even though they are downloaded
This ensures that the build doesn't rely on *your* *local* repository. At
any time anybody should be able to build the project, it even should be
possible that you remove your own local
The Apache Maven team is pleased to announce the release of the Apache
Maven Artifact Transfer, version 0.10.1
The Maven Artifact Transfer Component is intended as an API to install,
deploy and resolve artifacts in Maven 3.
https://maven.apache.org/shared/maven-artifact-transfer/
You
The Apache Maven team is pleased to announce the release of the Apache
Maven Common Artifact Filters, version 3.1.0
This library contains a collection of ready-made filters to control
inclusion/exclusion of artifacts during dependency resolution.
really seems to help me with what I like/need to achieve, expect of
the JDom parser approach that was implemented by Robert Scholte for the
maven-release-plugin version 3.0 - which hasn't been continued nor
released for 2 1/2 years now.
@Robert: I'd really like to pick up Your approach. Looks very
This is a dangerous advice.
Yes, it'll only compile the touched files, but not the source files using
it.
For example method signature changes are not detected and you will hit
that issue at runtime with a NoSuchMethodException, which is too late (and
then Maven is of course the one to
Hi,
that's indeed quite a huge difference, but does this mean that the 55
seconds is only for compilation?
The background about incremental builds is described/discussed in
MCOMPILER-205[1] and Stack Overflow[2].
TLDR; If you change a method signature, you must also compile all classes
Have a look a flatten-maven-plugin[1], which was implemented to rewrite
the pom file.
Robert
[1] https://www.mojohaus.org/flatten-maven-plugin/
On Thu, 29 Nov 2018 17:11:12 +0100, Marc Rohlfs
wrote:
Hi all,
is there a way to rewrite pom.xml files without loosing formatting,
ordering
Right, it is now often solved with the CI server.
However, if somebody implements MINVOKER-100[1], then we could solve it
within the maven-invoker-plugin.
thanks,
Robert
[1] https://issues.apache.org/jira/browse/MINVOKER-100
On Mon, 26 Nov 2018 16:00:46 +0100, Mirko Friedenhagen
wrote:
On Sat, 24 Nov 2018 17:02:02 +0100, Martin Desruisseaux
wrote:
Le 24/11/2018 à 16:39, Robert Scholte a écrit :
**If And Only If** you want to make use of single tool invocation for
all you JPMS modules, then you cannot use Maven, it's architecture
doesn't support it and any plugin trying
On Sat, 24 Nov 2018 15:34:51 +0100, Martin Desruisseaux
wrote:
Le 24/11/2018 à 15:10, Robert Scholte a écrit :
Today I started looking at MJAVADOC-449 again and it seems that just
nobody took serious time to solve this. I've been able to create the
proper commandline by moving some
On Sat, 24 Nov 2018 15:02:08 +0100, Martin Desruisseaux
wrote:
Le 24/11/2018 à 13:53, Robert Scholte a écrit :
With the Java Platform Modular System you'll clearly see different
requirements between library and application developers.
Indeed (e.g. jlink is for application developers
On Sat, 24 Nov 2018 13:28:28 +0100, Martin Desruisseaux
wrote:
Hello Robert
Thanks for your reply.
Le 24/11/2018 à 12:36, Robert Scholte a écrit :
Let me correct this part: there is *no* need to change the folder
structure to work with the Java Platform Modular System. The only
thing you
aven-compiler-plugin-3.8.0. That's it! Maven is the only
tool that had proper integration before the release of Java 9.
The key library which might(/should!) be interesting for you is
Plexus-Java [1], which calculates the modulepath.
For more details, just contact me.
thanks
Robert Scholte
[1]
I think it is a matter of a proper folder structure.
Referring from one version to another is tricky and should be avoided.
This is what we do with Maven[1], current/ uses some htaccess magic.
Robert
[1] https://maven.apache.org/ref/
On Tue, 20 Nov 2018 21:50:30 +0100, Russell Gold
wrote:
Hi,
seems related to MNG-6026[1].
thanks,
Robert
[1] https://issues.apache.org/jira/browse/MNG-6026
On Tue, 20 Nov 2018 12:26:54 +0100, Andrew Todd
wrote:
Hello all,
I am considering writing a Maven plugin to help improve confidence in the
integrity of the Maven artifacts used by a
See https://issues.apache.org/jira/browse/MNG-5588
thanks,
Robert
On Tue, 20 Nov 2018 15:25:35 +0100, Neeraj Mahajan
wrote:
Hi ,
Does anyone know if we have a feature in maven to reuse common plugin
configuration in projects that doesn't share common parent ?
I know in case of
Counter question: where should we improve the documentation?
On Thu, 08 Nov 2018 19:02:03 +0100, Russell Gold
wrote:
Thanks, that was the problem :)
On Nov 7, 2018, at 3:48 PM, Robert Scholte wrote:
Did you specify the requiresDependencyResolution of the @Mojo?
Robert
[1]
https
Did you specify the requiresDependencyResolution of the @Mojo?
Robert
[1]
https://maven.apache.org/plugin-tools/maven-plugin-tools-annotations/index.html#Supported_Annotations
On Tue, 06 Nov 2018 21:24:03 +0100, Russell Gold
wrote:
I am writing a plugin which does post-processing on some
The Apache Maven team is pleased to announce the release of the Apache
Maven Jarsigner Plugin, version 3.0.0
This plugin provides the capability to sign or verify a project artifact
and attachments using jarsigner.
https://maven.apache.org/plugins/maven-jarsigner-plugin/
You should
I could start experimenting with this specific issue.
Maven 3.6.0 has access to a FileTransformer, which can be used to make
remove this attribute and make its value explicit in the pom file.
Robert
On Sat, 03 Nov 2018 12:36:30 +0100, Karl Heinz Marbaise
wrote:
Hi Hervé,
On 03/11/18
The Apache Maven team is pleased to announce the release of the Apache
Maven Jarsigner, version 3.0.0
This component provides some utilities to sign/verify jars/files in your
Mojos.
https://maven.apache.org/shared/maven-jarsigner/
org.apache.maven.shared
maven-jarsigner
We'll need to make it stable first on our CI server[1]
Once that's fixed we can have a look at a release.
Robert
[1]
https://builds.apache.org/job/maven-box/job/maven-jarsigner-plugin/job/master/
On Wed, 24 Oct 2018 15:53:12 +0200, Prange, Benny
wrote:
Hi all,
there is a feature
The Apache Software Foundation has all the required infra.
Please read https://www.apache.org/dev/repository-faq.html
thanks,
Robert
On Fri, 05 Oct 2018 14:58:30 +0200, Eric Barboni wrote:
Hi Maven folks,
Apache NetBeans is under incubation right know and we would like to
publish
it to
The Apache Maven team is pleased to announce the release of the Apache
Maven JXR Plugin, version 3.0.0
The JXR Plugin produces a cross-reference of the project's sources. The
generated reports make it easier for the user to reference or find
specific lines of code.
You can't.
The Java 9 multiple module compilation doesn't fit into the Maven model.
For Maven, every deliverable requires its own pom, hence a separate Maven
module.
You could have a look at Pro[1], an experimental build tool inspired by
Maven and all JPMS features.
thanks,
Robert
[1]
Add them as compile scoped dependencies. The JRE implementation will be
picked up first, so there should be no issues here.
AFAIK this is what the jigsaw team suggests to do. (this is actually not a
buildtool specific issue but a general Java issue)
thanks,
Robert
On Fri, 14 Sep 2018
1 - 100 of 540 matches
Mail list logo
