Alternatively, you could consider mcs [1] (Maven Central Search).
MCS lets you search on coordinates (exact or partial) or on class name.
It will print out the matching results from the Maven Central index as
offered by Sonatype. If you provide a Sonatype API access token, MCS can
also report
On 18/12/2023 21:38, mark.yagnatin...@barclays.com.INVALID wrote:
I'm not the original asker but this kind of answer tends to annoy me.
Yes, there is no "official" release timeline, you're obviously not going to
promise anything, all this is (hopefully?) clear, BUT!
You no doubt have GUESSES. A
On 28/01/2022 14:52, Tamás Cservenák wrote:
Howdy,
We'd like to get some feedback from anyone who implemented, maintained or
plans to implement a Maven Plugin (Mojo):
Did any of you see a Maven Plugin that is NOT implemented in Java (but uses
Ant or Beanshell scripting)?
If I recall correctl
Personally, I don't use it, and I never used it in the past.
For better reach, would it be useful to tweet a poll about it from the
@ASFMavenProject handle?
Thanks,
Maarten
On 17/10/2021 11:56, Michael Osipov wrote:
Hi Users,
are there any Maven users who use Maven SCM Hg provider directl
IIRC, that's how JaCoCo Maven Plugin [1] works as well: you have to
configure two executions. The first one sets up the Java agent, the
other one processes the collected data and writes a report.
That's not to say "this is the way", but people may already be used to
this kind of setup.
HTH,
Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.
On Mon, Aug 2, 2021 at 7:16 PM Maarten Mulders
wrote:
Hi Andres,
Guess you're looking for MessageBuilder interface, which lives in
maven-shared-utils. There are two
Hi Andres,
Guess you're looking for MessageBuilder interface, which lives in
maven-shared-utils. There are two implementations, the
PlainMessageBuilder and AnsiMessageBuilder. The latter one generates the
colours on the terminal.
HTH,
Maarten
On 02/08/2021 16:47, Andres Almiray wrote:
Hel
On 22/05/2021 02:47, jerg wrote:
I tried to extract common Code of a Server-Client Project by turning my Project
into a multi-module Project.
1. I'm unsure if this is the right approach for that Problem. I'd be happy to
hear about ways to do this better.
2. I encountered a problem where i coul
The Apache Maven team is pleased to announce the release of the Apache
Maven Shared Utils, version 3.3.4.
This project aims to be a functional replacement for plexus-utils in Maven.
https://maven.apache.org/shared/maven-shared-utils/
You should specify the version in your project's plugin conf
Hi Alexander,
Regardless of how you do it, please know that all options will give you
a snapshot of what will eventually become Maven 4. That means: our
integration tests pass, but there may be known and unknown bugs. Use at
your own risk :-).
Having said that, you have several options:
(1)
Hi Andres,
If its just about deploying the modules to a remote repo, you could set
the skip property of the maven-deploy-plugin. I've applied that trick in
a Maven plug-in I've made [1]; their integration tests don't need to be
in Central, but all other modules should. In this scenario, the
i
rom into its cache ? That is, where do I
find the original 2.3.3 so that
I can change it to 2.3.4 ?
On 2020/11/18 11:39:05, Maarten Mulders wrote:
> Hello Chris,>
>
> By issuing mvn help:effective-pom -Dverbose=true, you can inspect the >
> "effective POM".
Hello Chris,
By issuing mvn help:effective-pom -Dverbose=true, you can inspect the
"effective POM". It will show you where the version of the Error Prone
is selected:
2.3.3
(you may need to scroll a bit, it's pretty much near the top of the output)
The version of Error Prone is sel
ure it.
>
> mf
>
>
> On 2020/07/12 19:48:45, Tamás Cservenák wrote:
>> Technically, plugin version comes from packaging mappings, not the
>> super-pom, but yes, Maarten is right that in this case maven version
>> "tells" version of plugin to be used.
&g
Hi Martin,
Your super simplistic POM does not specify a parent, and as such it
inherits from the default POM that ships with Maven 3.6.3.
Using mvn help:effective-pom -Dverbose=true you can see how the
effective model for your project builds up, and there you'll find that
version 2.2 is determine
But I, for one, wouldn't
trust on that assumption alone.
Cheers,
Maarten
[1] https://twitter.com/royvanrijn/status/803902527360159744
On December 23, 2019 at 14:53, Mark Prins wrote:
On 21-12-19 21:02, Maarten Mulders wrote:
Maybe this can help you:
https://github.com/portofrotterdam/v
Maybe this can help you:
https://github.com/portofrotterdam/versiondebt-plugin
As far as I can see, it doesn't allow you to configure "what is old". It
does tell you how old dependencies are.
Important disclaimer at the end of the page: it isn't maintained on a
regular basis.
Cheers,
Maarten
Also cross-posting from StackOverflow [1], where I just answered your
question:
There is a dedicated Spring Boot Maven Plugin [2] that also allows you
to repackage your application. Its repackage goal automatically
activates during the package phase, so you don't even need to define an
execu
I've recently had the same line of thought...
Many projects publishing "release candidates" or "milestone releases". I
understand
this is great for having feedback from their user base, but sometimes
I'd rather use
a "stable" version. Although this brings a new question to the table:
who deter
Hi list,
I'm using the Maven Release Plugin together with Git for version
control. I would like to achieve the following. When I create a release
on master, say version 1.5.0, I would like to have both a tag and a new
branch - starting at that tag. The branch would be there to release
fix-rel
20 matches
Mail list logo