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
> a
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.
Any
un-append artifacts from the project build, should it?
Ben
Am Mo., 3. Feb. 2020 um 11:08 Uhr schrieb Benjamin Marwell :
>
> 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
Great quiz!
I got 12/14 because I was a bit lazy in the beginning.
Forgot my twitter handle, please add @bmarwell - thanks!
If you had some experience with wrong or mixed dependency versions, it
is pretty straightforward.
But if you never had these problems, it is very hard to solve!
Thanks for
Hi everyone,
In a project, I currently configured three executions of the maven
compiler plugin.
1. proc:only, generate annotations for org.immutable
2. proc:only, generate annotations for hibernate-static-metamodel (not
all modules)
3. proc:none, i.e. compile everything.
For this to work, I hav
Hi Ankit,
the appassembler-maven-plugin [1] is maintained by mojohaus, they have
a different mailing list on google groups:
https://www.mojohaus.org/mail-lists.html
HTH
Ben
[1] https://www.mojohaus.org/appassembler/appassembler-maven-plugin/
Am Do., 4. Juni 2020 um 00:46 Uhr schrieb Ankit Tomar
Well, if the Dependency version changed with the target java Bytecode
version, you could create a multirelease jar and manage the dependencies
via profiles.
But that would seem not feasible to me.
What's your use case?
Or maybe you could refactor that class(es) into modules instead?
Best regards
Well, you could write your own plugin which has checkstyle as a dependency.
But it might be the easiest to just create a PR for the checkstyle plugin.
The checkstyle plugin is maintained by maven. So why not just create a
feature request?
Also, where do you want to execute the "new goal"? In the m
other ways to use Checkstyle.
>
> I find it very useful, though although it's complicated to set it up in its
> current Avatar.
>
> Regards,
> Linus.
>
>
>
>
> On Thu, 25 Jun 2020, 11:56 Benjamin Marwell, wrote:
>
> > Well, you could write your own plu
You need at least java 9 for http/2. Java 11 is a current LTS release which
supports h2.
Is there anything in the transport code preventing h2 transport?
Ben
On Fri, 23 Oct 2020, 11:28 Olivier Lamy, wrote:
> There is some effort started here
> https://github.com/jetty-project/jetty-maven-
While TLS 1.3 and ALPN (and ciphers) may have been backported, I am not
aware of http2 being backported to Java 8. Even if it was, it would not be
part of EVERY JVM implementation, eg Eclipse OpenJ9.
On Sun, 25 Oct 2020, 09:52 Michael Osipov, wrote:
> Am 2020-10-24 um 14:25 schrieb Benja
9+ and it will
connect via http/2.
I am sorry this caused confusion, but I did not like your response which
did sound "aggressive" to me. I will therefore not contribute to this
project soon.
On Sun, 25 Oct 2020, 19:54 Michael Osipov, wrote:
> Am 2020-10-25 um 19:09 schrieb Benjami
Hi Thomas,
I tested your configuration and found the same issue – however, it may
not be an issue after all.
You configured your javadoc plugin as part of the reporting section.
This usually requires the compile goal.
Even if you add the jar goal to the default build->plugin section, it
will sti
rd. I
> set up the minimal project to get this figured out, but I lost.
>
> Looking at https://maven.apache.org/plugins/maven-javadoc-plugin/usage.html,
> there is even no hint on suddenly requiring „compile“ starting with version
> 1.1.0. Still the site issue drives me nuts, too.
>
&
Hi Tim,
this lines makes me wonder:
> [ERROR] no reactor project: my project>
I think this means that will only work with
dependencies from the same reactor project. Thus your
"group_id:artifact_id of the single dependency of my project" seems to
be a foreign project?
But then from the goal d
And:
BUILD SUCCESS
So I think you found a bug where module sources are not being added to
the javadoc source path AND there is a misleading error message.
Would you kindly open two issues?
Am Mi., 28. Okt. 2020 um 20:18 Uhr schrieb Benjamin Marwell
:
>
> Hi Tim,
>
> this lines mak
Hi Alexander,
this is an old thread, but no one has replied yet.
While I think this is possible – what are you trying to achieve?
Or in other words: WHY do you need the dependencies unpacked? What do
you do with them?
Regards,
Ben
On 2020/08/19 18:23:06, Alexander Broekhuis wrote:
> Hi all,
>
or give me a hint, what I could have done wrong?
>
> kind regards,
>
> Thomas
>
> > Am 28.10.2020 um 20:05 schrieb Benjamin Marwell :
> >
> > Hi Thomas,
> >
> > no worry, that is as easy to fix as the previous one.
> >
> > Read carefully:
&
or „compile“ running before the „test-javadoc“ goal. No way to get
> it working during „mvn site“ though!
>
> kind regards
>
> Thomas
>
> Am 29.10.2020 um 15:57 schrieb Benjamin Marwell :
>
> Hi Thomas,
>
> | Exit code: 2 - javadoc: error - No source files for package de
Well, if central supported h2 push, that would be a benefit!
E.g. request shiro-web.jar and all the other dependencies would be pushed:
shiro-core.jar/.pom etc.
Maven would need to figure out which one it needed, so it doesn't
redownload existing artifacts.
So, no (or only marginal) gain without
Hi Michael,
I do not think it is necessary to download ALL of them serially. H2
Server push might become a big advantage as already mentioned.
e.g. if requesting a pom, it might push the jar and its dependencies
right away with it.
THAT would probably save a lot of connections (and time).
The onl
Hi Volker,
the issue you opened at github is correct [2].
The plugin actually needs to retrieve the password from the settings, like
the wagon plugin does [1].
HTH with your upstream issue.
[1]:
https://github.com/mojohaus/wagon-maven-plugin/blob/5701bacc30828fee63c54a33536e5054ea453fc3/src/
The Maven team is pleased to announce the release of the Apache Maven JLink
Plugin, version 3.1.0
The JLink Plugin is intended to create a Modular Java Run-Time Images via
jlink.
https://maven.apache.org/plugins/maven-jlink-plugin/
You should specify the version in your project's plugin configur
Hi Andrea,
looking at the maven-compiler-plugin, it uses plexus-java 0.9.10 which
in turn uses an old 6.x asm version.
Try adding a more recent version of plexus-java (which uses asm 9.0)
and see if that works.
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
15
up of one minor version to
> plexus-java 0.9.11.
> I also tried to update asm with:
>
>
>org.ow2.asm
> asm
> 9.1
>
>
> so pexus-java 0.9.10 and asm latest but I got the same original error.
> Andr
ks, the
> second doesn't, in my multi-module project with a parent module plus 8
> child modules it fails on the second module with 'mvn clean compile' from
> the parent.
>
> I hope it helps.
> Andrea
>
> Il giorno mar 9 feb 2021 alle ore 21:46 Benjamin Marwell
/torakiki/testme/pull/1
This will probably make it into one of the next versions of the
compiler plugin, if you would rather want to wait.
Best regards,
- Ben
Am Mi., 10. Feb. 2021 um 14:33 Uhr schrieb Benjamin Marwell
:
>
> Hi Andrea,
>
> thank you very much! I can confirm that thi
s child1 module is actually missing from
> the module path. Is there anything misconfigred?
> Andrea
>
>
>
>
> Il giorno gio 11 feb 2021 alle ore 08:42 Benjamin Marwell <
> bmarw...@apache.org> ha scritto:
>
> > Hi Andrea,
> >
> > Robert was sure the
Hi Antoine,
That's probably a typical YMMV question.
>From my experience with surefire, I'd say rather stick with the 2.x
versions as long as you don't need an explicit feature of the 3.x Milestone
version.
If something doesn't work or is missing, open up a ticket or ask on this
list.
If you find
Hi Zos,
you probably want to write
@project.version@
for your artifact. It will get replaced with the version number of the
enclosing module.
It is listed in the usage page (as a side note):
https://maven.apache.org/plugins/maven-invoker-plugin/usage.html
Here is a random example of one of the
Hi,
you need to use https URLs in your repositories. http URLs are now
blocked by default.
That should resolve the issue you are having.
You should take a look at your $HOME/.m2/settings.xml, as well as
potential occurrences of repository tags in your pom.xml files.
Best regards,
Ben
Am Mo., 3.
://maven.restlet.org is expired.
But other than that, this is how you bypass the http block.
HTH
Am Di., 4. Mai 2021 um 15:42 Uhr schrieb Mark H. Wood :
>
> On Tue, May 04, 2021 at 12:29:20PM +0200, Benjamin Marwell wrote:
> > you need to use https URLs in your repositories. http URLs are now
&g
Can you run the same with -X? This will give more information.
You might want to try -DgeneratePom=true, although this should be the default.
Am Mi., 2. Juni 2021 um 08:19 Uhr schrieb Zos ROTHKO :
>
> Hello
>
> I want to deploy a file using the command below
>
> mvn org.apache.maven.plugins:maven-
Just FYI,
IBM, Zulu, Oracle and Microsoft are giving extended support to paying
customers until the 2030s. I guess maven plugins will stay on 1.8 for quite
a while, but that's just a guess.
At least most libraries haven't moved to Java 11 yet (and afaik won't move
to Java 11 in the near future).
ses soon and perhaps I too can just say that no
> longer will any of the libraries I build be Java 1.7 compatible, so if one
> of those clients needs it, they can get their server upgraded or "too bad"
> - man that'd be great!
>
> Cheers,
> Rick
>
> E-mail: han
Can be found in the repository guide:
https://maven.apache.org/guides/mini/guide-proxies.html
And in the settings reference:
https://maven.apache.org/settings.html
It is referenced in the configuration guide as link:
https://maven.apache.org/settings.html
In case I missed a reference, PRs are we
Hi Sandeep,
yesterday almost everyone had problems getting artifacts from maven
central, it should be resolved by now.
My guess is that a lot of developers pushed their updated artifacts
b/c of the log4j2 issue.
If you have a in internal build server and cannot accept downtimes,
you can install a
Hi,
The Mojo team is pleased to announce the release of the
taglist-maven-plugin version 3.0.0.
The Taglist Maven Plugin generates a report on various tags found in
the code, like @todo or //TODO tags.
https://www.mojohaus.org/taglist-maven-plugin/
To get this update, simply specify the version
Yes, it's using the javac compilers default.
It may differ depending on the JVM. OpenJ9, for example, will use up to 25%
of your memory by default. Others may use something between 64M and 512M.
Be aware that maxmem will only work if fork is set to true:
https://maven.apache.org/plugins/maven-comp
Thanks everyone involved, and thank you to Brian Demers for starting this
project in the first place!
On Sat, 14 May 2022, 16:07 Hervé Boutemy, wrote:
> The Apache Maven team is pleased to announce the release of the Apache
> Maven
> Wrapper, version 3.1.1.
>
> The Maven Wrapper is an easy wa
Haven't seen a discussion in Slack or on the mailing list, so I guess no.
But I like the idea. Be aware that there are still Junit3 tests iirc.
Updating would be a breaking change, but that's okay for the upcoming Maven
4 release.
On Fri, 12 Aug 2022, 01:37 Vladimir V. Bychkov, wrote:
> H
There are two approaches for your issue.
First of all, you can try to use caches, so you don't need to download
dependencies over and over again. There are also settings which might help,
see the system properties in WAGON-545 [1]. E.g. retries and timeouts.
But.
To me it sounds from your descrip
Hi,
doesn't look odd the moment you know plugin authors can name configuration
elements anything they want. They could call it , but that doesn't
make it an UFO.
That said, spotbugs seems to use the findbugs artifact as a dependency in a
plugin like manner. They just choose to call it that way.
Maybe.
Some plugins, like jreleaser, just use Map. There's not
enough information for validation.
The other configuration (using POJOs) could probably be validated. However,
it's quite a bit of work (reflection, XML parsing).
If you're interested, why not just start a POC using an extension or a
Which version of Maven are you using?
Can you give us a relevant snippet of your pom.xml to reproduce the issue?
On Mon, 17 Apr 2023, 17:07 Sirisha Alla, wrote:
> Hi All,
>
> I am using surefire 3.0.0 with Junit 5 (Jupiter-engine). However, I am
> stumbling in to the Null Pointer Exception and
Hello everyone!
First of all thank you everyone working on the build cache plugin! It
is amazing!
At least some of the following questions seem to be of interest to
most users and might end up on the documentation, So here's a few
things which came to my mind.
1.) Considering I always require P
Am Mo., 12. Juni 2023 um 12:08 Uhr schrieb Olivier Lamy :
> On Mon, 12 Jun 2023 at 18:53, Benjamin Marwell wrote:
> >
> > Hello everyone!
> >
> > First of all thank you everyone working on the build cache plugin! It
> > is amazing!
> >
> > At least s
If you browse their repo, you can see that 4.2.1 is indeed missing:
https://repository-master.mulesoft.org/nexus/content/repositories/releases/org/mule/tests/mule-tests/
Just use dependencyManagement to override the version or exclude it
(if it is transitive) from its parent dependency and add it
Hi,
Disabling parallel put works for me.
https://maven.apache.org/resolver/configuration.html
On Fri, 27 Oct 2023, 20:08 Tamás Cservenák, wrote:
> Howdy,
>
> Are you sure you have to disable use of http-continue? Isn't this something
> "legacy" or hack that you try to carry on maybe?
>
> Is i
Hi Joseph!
Not really sure what you mean by "keep java's version in sync".
Since you said "-version option on my project", I am guessing you have
a CLI app and you want to report the version which you specify in your
pom.xml file.
Now to do that and have it working with your project, here are the
The Apache Maven team is pleased to announce the release of the Apache
Maven JLink Plugin, version 3.2.0
The JLink Plugin is intended to create modular Java Run-Time Images via jlink.
https://maven.apache.org/plugins/maven-jlink-plugin/
You should specify the version in your project's plugin con
Hi Maven Devs/Users/Committers and PMC members!
After several discussions on the mailing lists, I would like to
start a vote in favour of setting the minimal Java bytecode target
of Maven-Core 4 to 17 and hence require Java 17 for Maven 4.
This is a procedural majority vote [1*]:
You can also vot
Hi all,
the vote has passed with the following result:
PMC +1: Anders Hammar, Arnaud Héritier, Benjamin Marwell, Guillaume
Nodet, Hervé Boutemy, Karl Heinz Marbaise, Konrad Windszus, ,Maarten
Mulders, Olivier Lamy, Romain Manni-Bucau, Sylwester Lachiewicz, Tamás
Cservenák
PMC majority quorum
+1 (binding)
Thanks!
Question to the -1 voters: Please do share a reason for downvotes. I
am eager to know why you think we should not update to Java 21.
Am Mi., 30. Apr. 2025 um 15:12 Uhr schrieb Matthias Bünger
:
>
> Hi everyone,
> over the last years we had several discussions about lifting
Yes, and other plugins did this as well, eg:
https://github.com/linux-china/toolchains-maven-plugin
However, as much as I love this idea, they lack one problem:
They often don't work in corporate environments (or so I heard). In some
envs it's enough to specify a proxy, some corps have their own J
Hello Tommy,
kindly stay on topic. It is about retiring an existing plugin, not
looking for a replacement.
Thank you very much for your understanding
Am Do., 13. Feb. 2025 um 11:28 Uhr schrieb Tommy :
>
> Hello fellow JVM Platform nerds!
>
> If you want to generate good looking (IMHO :-)) PDF do
+1
On Sat, 22 Feb 2025, 09:45 Matthias Bünger,
wrote:
> Good morning everybody,
> ten days ago I started a discussion about the Maven PDF plugin, asking
> who is using it, if people have switched over to other tools and what
> everybody is thinking about archiving the plugin. You can read the
57 matches
Mail list logo