+1
Delany
On Sat, 12 Jul 2025 at 20:58, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 14 issues:
> https://github.com/apache/maven/issues?q=milestone%3A3.9.11
>
> Changes since the last release:
> https://github.com/apache/maven/compare/maven-3.9.10...maven-3.9.11
&
+1
Delany
On Sun, 1 Jun 2025 at 21:22, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 36 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12355010
>
> There are still a couple of issues left in JIRA:
>
> https://iss
I can confirm the buildplan plugin indicates the correct order with v0.3.
Thanks again!
Delany
On Thu, 29 May 2025 at 11:01, Sergey Chernov wrote:
> Hey, Delany.
>
> > I'm running with this extension going forward. I don't use the build
> cache (yet) so that's not
o the prepare-package phase.
As the documentation says, the phases have been switched around.
But can you make it work with the buildplan-maven-plugin:list-phases goal
so I can actually see which phases runs when, or is that up to this plugin
to figure out?
Kind regards,
Delany
On Wed, 28 May 2
+1
This resolves the -pl switch issue for me: project with shade plugin waits
for transitive dependencies to build before building
Delany
On Mon, 19 May 2025 at 20:36, Slawomir Jaranowski
wrote:
> Hi,
>
> We have resolved 32 issues
>
> https://issues.apache.org/jira/issues/?jq
I was also thinking the ability of a community to vote and move forward
with whatever the result
is more important than the result itself. Disputing *this* vote slows
getting to the next one.
Its not even the kind of vote that would change the direction of the
project.
Delany
On Fri, 23 May
My gut says the last occurrence should set the value, not the first.
At least that's how dependency versions are managed in the POM inheritance.
Other configuration systems like ini files override with subsequent values.
Is it too late to change?
Delany
On Mon, 17 Mar 2025 at 21:43, Karl
, e.g. [1/3].
Delany
On Fri, 7 Mar 2025 at 20:30, Delany wrote:
> +1
>
> Delany
>
>
> On Wed, 5 Mar 2025 at 13:17, Guillaume Nodet wrote:
>
>> We solved 108 issues since rc-2.
>> https://issues.apache.org/jira/projects/MNG/versions/12355493
>&
+1
Delany
On Wed, 5 Mar 2025 at 13:17, Guillaume Nodet wrote:
> We solved 108 issues since rc-2.
> https://issues.apache.org/jira/projects/MNG/versions/12355493
>
> Staging repositories:
> https://repository.apache.org/content/repositories/maven-2278/
> https://dis
Ok thanks that's the issue. But is it my problem? Its not obvious how to
remediate.
So I offer this fix https://github.com/apache/maven-archiver/pull/86/files
Delany
On Sun, 19 Jan 2025 at 15:47, Jorge Solórzano wrote:
> This is due to a limitation of MS-DOS time limitation in z
01-01T00:00:02Z date?
I'm guessing the change was made in Maven Archiver 3.6.1 > 3.6.3
If this can't be reverted what do I need to do to make my build work again?
Thanks,
Delany
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:3.3.0:process
(
ptors/*.descriptor
Changing my vote to +1
Delany
On Mon, 16 Dec 2024 at 09:28, Guillaume Nodet wrote:
> Could you raise an issue, provide the full stack trace, and eventually a
> way to reproduce the problem please ?
>
> Le lun. 16 déc. 2024 à 08:15, Delany a é
ink how to avoid it.
Google takes me to
https://maven.apache.org/ref/4-LATEST/maven-impl/apidocs/org/apache/maven/internal/impl/model/DefaultInterpolator.html
Delany
On Sat, 14 Dec 2024 at 02:01, Guillaume Nodet wrote:
> We solved 38 issues since rc-1.
> https://issues.apache.org/jira/projects/MN
erns are exaggerated.
Delany
On Thu, 12 Dec 2024, 14:21 Elliotte Rusty Harold,
wrote:
> On Thu, Dec 12, 2024 at 9:15 AM Christoph Läubrich
> wrote:
> >
> > I just wanted to note with Eclipse moved form Bugzilla > Github it was
> > done the following way:
> >
>
Hi. Two issues came up:
I use this archived plugin to ensure consistent filenames (if there's an
alternative please let me know!)
com.github.ngeor
yak4j-filename-conventions-maven-plugin
org.codehaus.plexus
plexus-utils
able to host project code like Maven. Just
a thought.
Delany
On Tue, 22 Oct 2024 at 19:11, Matt Nelson wrote:
> I think the user experience for everyone but the most active members may
> regress by moving issues to GH. Maven has a lot of repositories(100+) and
> almost as many jira projects
What about an empty .mvn/maven.config file?
Delany
On Wed, 25 Sept 2024 at 08:41, Richard Eckart de Castilho
wrote:
> Please do not make us have to create an empty directory just to please
> the build tool...
>
> -- Richard
>
> > On 24. Sep 2024, at 23:06, Tamás Cserven
Hi Gnodet,
I notice `mvn validate` now takes 50s when on Maven 3.9.9 it took 16s. Is
this expected? (I assume both respect my --threads=1C switch)
First comment on the issue suggested faster builds
https://issues.apache.org/jira/browse/MNG-5666
Kind regards,
Delany
Hi Gnodet,
Re: https://issues.apache.org/jira/browse/MNG-8052
putting the ordinal at the beginning like
1000:after:integration-test
reads easier than in square brackets like
after:integration-test[1000]
Less syntax to remember, no?
And then https://issues.apache.org/jira/browse/MNG-7804
It seems
+1
Delany
On Fri, 30 Aug 2024 at 15:43, Tamás Cservenák wrote:
> Howdy,
>
> We solved 56 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354939
>
> There are still a couple of issues left in JIRA:
>
> https://iss
hese
mojos to a new plugin?
Delany
On Thu, 15 Aug 2024 at 17:49, Elliotte Rusty Harold
wrote:
> No, it seems to be a proposal for a new core plugin, not just
> reorganzing the git repo. I predict if someone tries that we'll still
> have all the old plugins plus the new maven-
What about the full "Maven Project Module"? Then there's no confusion about
Maven being a modularized Java application.
Intellij could adopt the same convention "Intellij IDEA Project Module".
Delany
On Mon, 5 Aug 2024 at 14:29, Jeff Jensen
wrote:
> Additionally,
+1
Delany
On Tue, 16 Apr 2024 at 23:14, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12354551
>
> There are still a couple of issues left in JIRA:
>
> https://iss
If a pom says it has a dependency "2.4.1-SNAPSHOT" then
I don't want the validation failing in offline mode because
"2.4.1-20240322.141808-12 has not been downloaded".
Delany
On Tue, 26 Mar 2024 at 16:15, Tamás Cservenák wrote:
> Delany,
>
> What do you mean b
m looking for a button to push that will say "All SNAPSHOT versions are
equal". And you can add to that "from any repository".
I get why you wouldn't want to introduce that though. Thanks for answering.
Delany
On Tue, 26 Mar 2024 at 10:49, Tamás Cservenák wrote:
> Howdy,
, just
not that specific one.
I thought changing the updatePolicy to NEVER would solve this, but the new
enforcer (which now uses resolver) fails nonetheless.
Is there a way to get resolver to treat all snapshots as equal in offline
mode? Is there a reason this isn't the default?
Thanks,
Delany
+1
On Thu, 21 Sept 2023, 21:53 Slawomir Jaranowski,
wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12353341
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3
I tested v3.5.0 with an updated jdependency, which worked fine on jdk21-ea.
Delany
On Tue, 19 Sept 2023 at 13:16, Guillaume Nodet wrote:
> Have you tried the current master for this plugin ?
> Can I just go ahead and release it in the current state or is there
> anything to fix first
Hi all,
JDK21 reaches general availability today. Could someone provide another
release of the shade plugin to support it?
Kind regards,
Delany
Listed as "won't do"
https://issues.apache.org/jira/browse/MNG-5773
Is it possible as a future XSD change, or should I rather pursue an
enforcer rule? Or both?
Delany
On Wed, 2 Aug 2023 at 18:22, Michael Osipov wrote:
> This is known, search JIRA and Ple
The format is
<code><name>value</name></code>.
Thanks,
Delany
+1
Delany
On Wed, 26 Jul 2023 at 12:09, Tamás Cservenák wrote:
> Howdy,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12353369
>
> There are still a couple of issues left in JIRA:
>
> https://iss
You might be interested in https://basepom.github.io/
Delany
On Wed, 28 Jun 2023 at 08:40, Geoffrey De Smet
wrote:
> *Summary
> *
>
> Specifying the Java version (11, 17, ...)
> and latest maven plugin versions (compiler 3.11.0, surefire 3.1.2,
> failsafe, ...)
> in every
+1
On Fri, 23 Jun 2023 at 15:34, Tamás Cservenák wrote:
> Howdy,
>
> We solved 22 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12353255
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%
t required.
With Maven tracking the latest LTS JDK I wonder how many fingers would be
freed from plugging up the JDK8 dyke.
Delany
On Fri, 9 Jun 2023 at 10:58, Olivier Lamy wrote:
> this jdk discussion could be ended if someone could say we need jdk17
> as a minimum because we really need
y shading, etc, etc.
Suffice to say there are issues.
Delany
On Tue, 6 Jun 2023 at 14:34, Jeremy Landis wrote:
> Delany,
>
> "You need toolchains if your code needs the JAXB classes removed in JDK11.
> Delany"
>
> That isn't accurate. You do not need toolchains f
You need toolchains if your code needs the JAXB classes removed in JDK11.
Delany
On Tue, 6 Jun 2023 at 01:54, Henning Schmiedehausen <
henn...@schmiedehausen.org> wrote:
> To get this discussion a bit more back to actual substance:
>
> Do you still need toolchains with JDK 1
Your inclination to ignore points of the debate doesn't do your own
arguments any justice.
Multiple times it's been explained that raising the required runtime JDK in
Maven 4 will not prevent you from
- building with a lower JDK (via toolchains)
- targeting a lower JDK (via the release property)
-
a
new project you should choose Maven"
Delany
On Sat, 3 Jun 2023 at 23:05, Hunter C Payne
wrote:
> Folks who think like that have been using Scala or Kotlin for at least 5
> years by now. If you are still writing Java, it isn't for new features.
> Hunter
>
> PS If you w
ot robots and yes its "sexier" and more "satisfying" to work with JDK17.
Ignoring that fact is itself irrational.
Delany
On Sat, 3 Jun 2023 at 11:46, Hervé Boutemy wrote:
> +1
>
> I really don't what benefit we get from going to Java 17
>
> I perfectly
Excuse my ignorance but what do customer requirements have to do with the
build tool's required JDK?
Delany
On Wed, 31 May 2023 at 13:57, Elliotte Rusty Harold
wrote:
> On Wed, May 31, 2023 at 8:30 AM Guillaume Nodet wrote:
>
> > I think with those improvements, requiring
blem.
I have chosen to get the latest features with the tradeoff of having to
deal with new issues.
This way the window for change is widened to include real world scenarios
and one settles these sorts of issues sooner.
Delany
On Sun, 28 May 2023 at 22:58, Henning Schmiedehausen <
henn...@schmiedeh
Hi Tamas,
I'm still getting locking issues with maven-surefire-plugin:3.1.0
I assumed these were resolved in
https://issues.apache.org/jira/browse/MRESOLVER-346 which i believe made it
into Maven 3.9.2, so switched back to Maven 3.9.0
What was the previous default value of aether.syncContext.name
Premature send :()
Basically I don't know how to test shared components, so I dont vote on
those.
What about some way to run maven where it only runs to bootstrap another
version of maven? Wrapper could possibly do this.
Delany
On Fri, 12 May 2023 at 12:25, Delany wrote:
> Well wha
Well what is the reason people don't vote? I just think we need to make it
easier to actually test the releases.
My system is setup to vote on plugins that I use. Obviously I don't vote on
plugins I don't use.
stage
stage
+1
On Tue, 9 May 2023 at 18:48, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317825&version=12352115
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%
What is the value of having a separate plugin repository, even when
dependencies of those plugin are drawn from the standard repository?
Kind regards,
Delany
+1
"The Maven Plugin Tools contains the necessary tools to generate
rebarbative content like descriptor, help and documentation."
Rebarbative means unattractive and objectionable.
On Tue, 18 Apr 2023 at 18:32, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 10 issues:
>
> https://issues.apache.
+1
On Tue, 18 Apr 2023 at 17:09, Michael Osipov wrote:
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12352856
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project+%3D+MCHE
ult-cli of goal
org.apache.maven.plugins:maven-help-plugin:3.4.0:effective-settings failed:
Cannot invoke "org.codehaus.plexus.util.xml.Xpp3Dom.getDom()" because
"configuration" is null
Is this now a bug in the help plugin?
Regards,
Delany
+1
On Sat, 1 Apr 2023 at 23:13, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12352877
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20
Thanks Sławomir
+1 from me
Delany
On Tue, 28 Mar 2023 at 01:09, Slawomir Jaranowski
wrote:
> Please try: https://github.com/delanym/MINVOKER-283/pull/1
>
> wt., 28 mar 2023 o 00:36 Delany napisał(a):
>
> > 3.5.0 wasn't working because of
> > https://issues.apache
3.5.0 wasn't working because of
https://issues.apache.org/jira/browse/MINVOKER-328
There's a reproducer on the issue (with wrong issue number)
On Tue, 28 Mar 2023, 00:32 Slawomir Jaranowski,
wrote:
> wt., 28 mar 2023 o 00:23 Delany napisał(a):
>
> > -1
> >
-1
Fine on jdk11. On jdk17:
[INFO] java.lang.NoClassDefFoundError: Could not initialize class
org.codehaus.groovy.vmplugin.v7.Java7
[INFO] at
org.codehaus.groovy.vmplugin.VMPluginFactory.(VMPluginFactory.java:43)
[INFO] at
org.codehaus.groovy.reflection.GroovyClassValueFactory.(GroovyClassValue
on't be able to find it
> * the wrapper plugin does not support the new mvnd distributions with m39
> / m40 qualifiers, please raise a JIRA issue for that
>
>
> Le jeu. 23 mars 2023 à 14:46, Delany a écrit
> :
>
> > What should URL can I use for
> >
> >
>
What should URL can I use for
https://maven.apache.org/wrapper/maven-wrapper-plugin/wrapper-mojo.html#mvndversion
?
The github link is broken.
Kind regards,
Delany
On Thu, 23 Mar 2023 at 12:22, Guillaume Nodet wrote:
> I've staged a candidate release at
> https://dist.apach
aume Nodet wrote:
> Do you have a small project to reproduce the problem ?
> The violation looks legit if you haven't specified a version for the
> surefire plugin.
>
> Le mer. 15 mars 2023 à 19:21, Delany a écrit
> :
>
> > Build fails
> >
> > org.apache.
Build fails
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-enforcer-plugin:3.2.1:enforce (fail) on
project t1000:
Rule 0: org.apache.maven.enforcer.rules.RequirePluginVersions failed with
message:
Some plugins are missing valid version
+1
I want my colleagues to care about the compiler warnings so I turned off
that new Maven internal deprecation warning
-Dorg.slf4j.simpleLogger.log.org.apache.maven.plugin.internal.DeprecatedCoreExpressionValidator=error
On Wed, 15 Mar 2023 at 12:14, Tamás Cservenák wrote:
> Howdy,
>
> We sol
Maven complains about an absent pom. Why does it not try to resolve from
the staging repo?
I set it up in settings.xml
stage
stage
staging
Maven Staging
https://repository.apache.org/content/repositorie
+1
Delany
On Sat, 11 Mar 2023 at 11:09, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12352998
>
> There are still a couple of issues left in JIRA:
>
> https://iss
t off?
Another point is that if you can't easily rebuild with -e on to replicate
your problem you've got a bigger problem than lots of log output.
Delany
On Fri, 24 Feb 2023 at 15:15, Romain Manni-Bucau
wrote:
> Hi Elliotte,
>
> I agree -e should be the default, I don't
In the spirit of your elephant analogy, what is deserving of INFO level
logging?
On Thu, 23 Feb 2023 at 14:11, Elliotte Rusty Harold
wrote:
> On Wed, Feb 22, 2023 at 11:51 AM Romain Manni-Bucau
> wrote:
> >
> > Eliotte I kind of fail to follow your reasoning because it literally
> means
> > do
Another example of excessive logging prompting one to find the root cause:
On Mon, 6 Feb 2023 at 15:03, James Agnew wrote:
> Just to close the loop in case anyone finds this post.
>
> I had discounted the idea that a version range was the cause because I went
> over all of the POMs in my project
You're arguing based on principles, but my experience suggests otherwise.
Some real life examples:
https://issues.apache.org/jira/browse/MENFORCER-462
https://issues.apache.org/jira/browse/MNG-7214
I would not have noticed or logged either of these issues without logging.
Its because they were log
I wouldn't miss a thing past line 2. Since its all ERROR I have no control
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile
(default-compile) on project error_prone_core: Compilation failure
[ERROR]
/git/error-prone/core/src/main/java/com/google/errorpro
the simple logger properties.
Delany
On Mon, 20 Feb 2023 at 16:46, Christoph Läubrich
wrote:
> Well you can just reduce it to a single '.' who cares WHAT is download
> and where it is placed and from where... now put a line break after say
> 50 dots
>
>
> Am 20.
+1
Delany
On Tue, 14 Feb 2023 at 10:51, Guillaume Nodet wrote:
> Hi,
> I'd like to release Apache Maven Compiler Plugin 3.11.0
>
> 7 issues fixed
> https://issues.apache.org/jira/projects/MCOMPILER/versions/12351444
>
> draft github release notes (sadly only for people
+1
Delany
On Fri, 10 Feb 2023 at 11:21, Olivier Lamy wrote:
> Hi,
> I'd like to release Apache Maven Surefire 3.0.0-M9
> We fixed 4 issues.
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12352730
>
> Staging repo:
> http
be off by default, not on by default.
The only way to do that is to allow multiple properties as in
https://issues.apache.org/jira/browse/MNG-3328
I'm just reminding this issue is 16 years old with over 100 watchers
Kind regards,
Delany
On Thu, 2 Feb 2023 at 09:02, Tamás Cservenák wrote:
+1 with 3.9.0
Delany
On Sun, 5 Feb 2023 at 14:50, Michael Osipov wrote:
> Am 2023-02-04 um 10:12 schrieb Michael Osipov:
> > Hi,
> >
> > We solved 10 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12351555
&
ng, it just seems
about time for an xpath function.
"snapshots repository update interval:
$#{/project/repositories/repository[id="maven-releases"]/snapshots/updatePolicy/text()}"
Thanks,
Delany
+1
Delany
On Tue, 31 Jan 2023 at 12:37, Tamás Cservenák wrote:
> Howdy,
>
> We solved 95 issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.0
>
> There are still some open issues left in JIRA:
>
> https://is
Ok, thanks
+1
Delany
On Sun, 29 Jan 2023 at 21:25, Guillaume Nodet wrote:
> Yes, I already reported and provided a fix on netty.
>https://github.com/netty/netty/pull/12911
> So recent netty versions don't have this problem anymore.
>
> Le dim. 29 janv. 2023 à 19:59
Hi Romain. As far as I know executions are not required.
The relationship: plugin > goals is valid against
https://maven.apache.org/maven-v4_0_0.xsd
Delany
On Sun, 29 Jan 2023 at 16:40, Romain Manni-Bucau
wrote:
> +1
>
> @Delany netty bom looks incorrect (misses execution(s).
&g
+1
Delany
On Sat, 28 Jan 2023 at 23:39, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 44 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12352857
>
> There are still a couple of issues left in JIRA:
>
> https://iss
22)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:143)
Delany
On Fri, 27 Jan 2023 at 19:11, Guillaume Nodet wrote:
> I've staged a release candidate at [1]. The distributions are available at
> [2].
> The release notes are available at [3] for JIRA and [4
reproduce it?
> Or full stack.
>
>
> czw., 26 sty 2023 o 19:21 Delany napisał(a):
>
> > Thank you for this. My build on 3.8.7 is failing though:
> >
> > [ERROR] org.apache.maven.cli.MavenCli - Rule 0:
> > org.apache.maven.enforcer.rules.RequirePluginV
Hi Tamas,
Will you create a staging for 3.9.0?
I don't see anything at
https://repository.apache.org/content/repositories/staging/org/apache/maven/maven/
Delany
On Thu, 19 Jan 2023 at 11:03, Tamás Cservenák wrote:
> Howdy,
>
> The 3.9.0 changelist:
>
> https://issues.apache.
ecause the return value of
"org.apache.maven.model.Profile.getReporting()" is null
Delany
On Thu, 26 Jan 2023 at 19:56, Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 40 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=1
What problem is caused from skipping a patch version number?
If it applies to Maven, should it apply to everyone? ie https://semver.org/
Thanks
Delany
On Sat, 14 Jan 2023, 14:56 Elliotte Rusty Harold,
wrote:
> -1
>
> The version number's wrong. This should be 1.9.3.
>
> On
till need the plugin though?
Delany
On Mon, 12 Dec 2022 at 15:19, Guillaume Nodet wrote:
> I've staged a release candidate at:
> https://repository.apache.org/content/repositories/maven-1835
>
> Source distributions:
>
> https://dist.apache.org/repos/dist/dev/maven/mav
nt mention which bug - suffice to say there are such edge cases.
Delany
On Thu, 17 Nov 2022 at 21:01, Romain Manni-Bucau
wrote:
> Le jeu. 17 nov. 2022 à 19:16, Arnaud Héritier a
> écrit :
>
> > install is a source of issues if you are in a multi-module project, you
> > swi
Thanks for explaining
Delany
On Tue, 8 Nov 2022 at 13:08, Guillaume Nodet wrote:
> There are known issues that will be fixed in the next milestone. This
> problem in particular has already been fixed in [1].
> The flatten plugin is still relevant, as the goal for maven 4.0
Hi. I noticed the vote passed for alpha-2, but I'm still getting this
issue. Can someone comment?
Is the flatten plugin still relevant in Maven 4?
Thanks,
Delany
On Thu, 20 Oct 2022 at 09:26, Delany wrote:
> hi. I just changed .mvn/wrapper/maven-wrapper.properties to
> distributionU
ile:/home/sol/.m2/repository/commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent:
null]]
Regards,
Delany
On Sat, 15 Oct 2022 at 02:19, Guillaume Nodet wrote:
> I've staged a release c
Can I answer that? Because devs are principled, and the thought of the
build changing source is anathema.
In practice it happens with versions, release, sortpom plugins so why not
format too.
Personally I draw the line at commit time.
But crickey, in Golang you cant even save an incorrectly formatt
le PR to banish the problem once and for all, what are my
options?
Kind regards,
Delany
( I'm specifically thinking of
https://issues.apache.org/jira/browse/MNG-2751 )
Just to add, IntelliJ's tooltip links to
https://maven.apache.org/ref/2.2.1/maven-model/maven.html
Where is it getting v2.2.1 from?
The plugin depends on v3.1.1 (
https://github.com/apache/maven-shade-plugin/blob/maven-shade-plugin-3.3.0/pom.xml
)
Delany
On Tue, 6 Sept 2022 at 15:35, Romain
-test
software.amazon.awssdk:ecr
And it builds!
How can this situation be improved?
Kind regards,
Delany
On Tue, 6 Sept 2022 at 13:25, tison wrote:
> Thank you!
>
> Best,
> tison.
>
>
> Karl Heinz Marbaise 于2022年9月6日周二 17:44写道：
>
> > Hi,
> >
> > I will try
no announcement about the m-install-p v3.0.1 release.
Delany
On Thu, 4 Aug 2022 at 14:00, Michael Osipov wrote:
> Am 2022-08-04 um 13:32 schrieb Delany:
> > So you're saying the only way I can know is to run it or interrogate the
> > code?
> > There's no menti
So you're saying the only way I can know is to run it or interrogate the
code?
There's no mention of this in the release notes at
https://github.com/apache/maven-deploy-plugin/releases/tag/maven-deploy-plugin-3.0.0
m-install-p doesn't issue a warning like m-deploy-p does
Kind
loud-opensource-java/issues/2312
Thanks,
Delany
Using mvnd with toolchains doesn't improve the situation, in fact
toolchains seem to invalidate any benefit of using mvnd.
Even if this was resolved, is it fair to require mvnd?
Delany
On Sat, 23 Jul 2022 at 10:17, Mark Derricutt wrote:
> Is that due to cold starting the JVM each tim
I tried toolchains but dropped it because of the exorbitant performance
costs.
A multi-module build that normally built in 3:50 took 10:34, and that's
with toolchaining only maven-compiler-plugin.
Delany
On Sat, 23 Jul 2022 at 00:21, Benjamin Marwell wrote:
> KH just released a
ther build system to avoid doing the
inevitable is just making more work.
What little I know, I appreciate the bold move to JDK17 and I guess it'll
pay off in the long run. Who knows what's next around the corner.
Regards,
Delany
On Tue, 19 Jul 2022 at 20:39, Elliotte Rusty Harold
wro
Hi Markus,
How will this be different from
https://khmarbaise.github.io/iterator-maven-plugin/iterator-mojo.html ?
Kind regards,
Delany
On Sun, 17 Jul 2022 at 19:36, Markus Karg wrote:
> Dear Maven Developers,
>
>
>
> today I'd like to propose a new core feature of Ma
https://www.mojohaus.org/keytool/keytool-maven-plugin/plugin-info.html
On Mon, 13 Jun 2022 at 14:09, Graham Leggett
wrote:
> Hi all,
>
> I find myself yet again fixing a bug in an application where client
> certificates don’t work, as the constructors for the code work for the
> trivial case on
+1
JDK11 on *nix
Delany
On Fri, 13 May 2022 at 08:11, Herve Boutemy wrote:
> here is my +1
>
> Reproducible Build confirmed: reference done with JDK 8 on *nix
>
> I need more votes, please
>
> On 2022/05/08 09:28:32 Hervé BOUTEMY wrote:
> > Hi,
> >
>
Hi. Is there integration between the wrapper and the upcoming mvnd?
Thanks,
Delany
On Sun, 8 May 2022 at 11:29, Hervé BOUTEMY wrote:
> Hi,
>
> We solved 14 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350929&styleName=Text&projectId=12
1 - 100 of 113 matches
Mail list logo
