I've met Nicolai yesterday, we'll probably start soonish. It's not sure if the
group is complete, but at some moment we just need to start. Joining later is
of course still a possibility.
Robert
-Original Message-
From: Martin Desruisseaux
Sent: vrijdag 1 november 2024 11:41
To: dev@m
n Thu, Oct 24, 2024 at 1:18 PM Robert Scholte wrote:
>
> Inline responses...
>
> -Original Message-
> From: Martin Desruisseaux
> Sent: donderdag 24 oktober 2024 12:38
> To: dev@maven.apache.org
> Subject: Re: [DISCUSS] Merge JPMS work in upcoming
> maven-compi
-Original Message-
From: Martin Desruisseaux
Sent: donderdag 24 oktober 2024 13:38
To: dev@maven.apache.org
Subject: Re: [DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2
Le 2024-10-24 à 13 h 17, Robert Scholte a écrit :
(about automatic modules)
> What
Inline responses...
-Original Message-
From: Martin Desruisseaux
Sent: donderdag 24 oktober 2024 12:38
To: dev@maven.apache.org
Subject: Re: [DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2
Le 2024-10-24 à 12 h 07, Robert Scholte a écrit :
>
> Can you expla
Can you explain the problem you're trying to solve?
In particular I don't understand the need for modular-jar and classpath-jar, as
currently both classpath and modulepath are already build up correctly based on
the module descriptors.
Thanks,
Robert
-Original Message-
From: Martin Desr
s and tool integrations
Hi Robert,
Not sure to understand your response :)
My question was, "Why wouldn't this group have open/public visibility?"
A lot of people can be interested, not participating directly but maybe reading
what is happening.
Olivier
On Mon, 21 Oct 2024 at 1
amy
Sent: zondag 20 oktober 2024 21:52
To: Maven Developers List
Subject: Re: Module paths and tool integrations
Why not a public group especially if the scope is opensoure tools?
And by the way you are mentioning this on a public mailing list.
On Sun, 20 Oct 2024 at 11:39 pm, Robert Scholte
wr
s and tool integrations
I would be interested in joining. I have a Java persistence annotation library
for RDF that is in dire needs of updating and having such information would me
most helpful.
Claude
On Thu, Oct 17, 2024 at 8:28 AM Robert Scholte wrote:
> Hi,
>
>
>
> Dur
Hi,
During Devoxx Nicolai Parlog shared his concerns about how different tools
solve the modulepath/classpath in their own way (And he has a compliment:
Maven does it correct).
We were able to talk with the Jetbrains developers that are responsible for
Java/Maven integration and we're setting
icant changes in history with every major release of
Maven
I think skipping 9 Java versions between Maven 3 and 4 is a big deal and has
never happened before 😁
Java 17 will be required for Maven 4.
Also Maven 4: extensions where you can use pom.conf or pom.yml etc.
On Mon, 23 Sept 2024, 10:53 R
significant changes in history with every major release of
Maven
Hello Robert,
The subject piques my curiosity. Do you already know if there'll be a video
available of your presentation?
Kind regards,
Kevin
Le lun. 23 sept. 2024, 21:59, Robert Scholte a écrit :
> I'm glad I asked
, 10:53:48 CEST Robert Scholte a écrit :
> Hi all,
>
>
>
> Within 2 weeks I will do a talk with Maarten about Maven 4.
>
> Part of that are some slides about previous major releases that should
> clearly explain why it was a major release at not the next minor.
&g
Hi all,
Within 2 weeks I will do a talk with Maarten about Maven 4.
Part of that are some slides about previous major releases that should
clearly explain why it was a major release at not the next minor.
In short I came with this list:
M1 -> M2: (breaking change, migration required)
Key code is here:
https://github.com/apache/maven/blob/master/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1367-L1431
The CliRequest contains all the original arguments,
MavenExecutionRequest transforms these values and can be accessed via
MavenSession.
I don't see anything
Regarding #1 you need to be more precise.
The jigsaw-team also thought it would be easy to extend the pom for
this.
However, in the end I discovered there's no need to do this.
The plexus-java library has code which you feed the module descriptor
and all jars and it is able to decide if they be
This is already a huge improvement as imported boms now hides this
information.
I do see room for more improvements, though (even though they could be
considering as minor as this already solves a critical issue)
From another example I picked one of the longest lines:
2.16.1
Suppose you
Hi David,
I just noticed that
https://wiki.openjdk.java.net/display/quality/Quality+Outreach the Maven
status for Java17 should be green.
Confirmed via
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/master/
We used to test for LTS, current and next ea, but it seems the set h
Hi all,
as of now, Karl Heinz is the new chairman of the Apache Maven project.
I've done it for quite some time with a lot of pleasure.
I will also reduce my activities on this project, but will still be
involved as PMC member.
thanks,
Robert
-
The Maven PMC invited Sławomir to become a committer and he has accepted
it.
Enjoy improving Apache Maven!
thanks,
Robert
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@ma
ship something to users that we know to work, and that
we can easily prove to still work after we change it.
Thanks,
Maarten
On 11/12/2021 13:43, Robert Scholte wrote:
It was marked for Maven 4, and part of the improvements was test automation,
which was now possible because it became pa
vendredi 10 décembre 2021, 10:40:41 CET Robert Scholte a écrit :
I need more time.
e.g. it looks like type=source doesn't use the Java sourcefile to
download the wrapper.
now that the plugin and wrapper are combined in one project, the ITs are
incomplete.
They should call both the wrapper-
t history confirms:
https://github.com/apache/maven-wrapper/commit/570bc50afe07bff696a097cd7746d01b00e70337
Don't hesitate to create a Jira issue and corresponding fix to add .java
support for Windows: future 3.1.0 will have one more fix over previous 0.5.6
Regards,
Hervé
Le vendredi 10
I need more time.
e.g. it looks like type=source doesn't use the Java sourcefile to
download the wrapper.
now that the plugin and wrapper are combined in one project, the ITs are
incomplete.
They should call both the wrapper-goal and something like 'mvnw
--version' to ensure it is working (thi
With mvn verify -Prun-its all ITs fail on my system. This should work
out-of-the-box, so I'll need to investigate the issue.
And I'm pretty sure we can remove the cli package: you can't pass System
properties to Maven, only arguments. And they should be passed as is to
mvn.
IT's should confir
t;
Aan: "Maven Developers List" ; "Robert Scholte"
Verzonden: 10-11-2021 08:43:39
Onderwerp: Re: Eat our own dogfood
Apache used to operate Gump for this purpose, back on the days of Ant and
Maven 1.x.
-
T
This should be done as part of Mavens own build.
Don't rely on uploaded versions, there's always a gap where another job
could have uploaded a different version.
If things start to fail, it could be hard to reproduce it.
It should be the one that has been built and stashed, so you can unstash
a
Keep in mind that the pom.xml is language agnostic, it describes
configuration that makes sense for any programming language.
Hence, the pom should not be extended with Java specific features.
Maven supports extensions, with seems like a better fit.
Configuring an extension is not standardized ye
We're in an awkward situation.
It looks like that of all the 3.8.x releases, the first (3.8.1) is the
most stable one.
The subtitle of Maven 3.8.2 was "Fixes and non-invasive backports from
Maven 4.0.0-alpha-1."
Looking back it looks like the backports weren't that non-invasive, and
we have uni
+1
-- Origineel bericht --
Van: "Michael Osipov"
Aan: dev@maven.apache.org
Verzonden: 29-9-2021 19:01:39
Onderwerp: Re: [VOTE] Release Apache Maven version 3.8.3
Am 2021-09-27 um 21:17 schrieb Michael Osipov:
Hi,
We solved 18 issues:
https://issues.apache.org/jira/secure/ReleaseNote.
+1
-- Origineel bericht --
Van: "Andreas Dangel"
Aan: "Maven Developers List"
Verzonden: 6-9-2021 20:56:25
Onderwerp: [VOTE] Release Apache Maven PMD Plugin version 3.15.0
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349432&styleName=Text&
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 pr
Hi,
The vote has passed with the following result:
+1 : Hervé BOUTEMY, Robert Scholte, Arnaud Héritier, Karl Heinz
Marbaise, Sylwester Lachiewicz
PMC quorum: .reached
I will promote the artifacts to the central repo.
-- Origineel bericht --
Van: "Robert Scholte"
A
+1
-- Origineel bericht --
Van: "Hervé BOUTEMY"
Aan: "Maven Developers List"
Verzonden: 5-9-2021 11:38:24
Onderwerp: [VOTE] Release Apache Maven WAR Plugin version 3.3.2
Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121&version=12348574
+1
-- Origineel bericht --
Van: "Robert Scholte"
Aan: "Maven Developers List"
Verzonden: 4-9-2021 10:57:36
Onderwerp: [VOTE] Release Apache Maven Javadoc Plugin version 3.3.1
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projec
Hi,
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12347807&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317529%20AND%20resolution%20%3D%20Unresolved%20ORDER%20B
I left a few thouhts there a while ago.
Cheers,
Falko
Am 31.08.2021 um 22:50 schrieb Robert Scholte:
Hi,
I see quite some Maven extensions that rely on configuration.
There's no convention for this, so they all pick their own format and
location.
Looking at the build-cache it seem
Hi,
I see quite some Maven extensions that rely on configuration.
There's no convention for this, so they all pick their own format and
location.
Looking at the build-cache it seems there's again configuration
required.
I think with Maven 4 we should make it possible to add a
configuration-b
On Twitter started a similar discussion, they should have joined to have
a more complete view on this topic.
Here's[1] where it all started:
Robert
[1] https://twitter.com/JonathanGiles/status/1427748493678956544
-- Origineel bericht --
Van: "Enno Thieleke"
Aan: "Maven Developers List
FYI: A discussion has started on core-libs-dev mailinglist[1] about
extending java.util.Properties with methods to store properties files
in a reproducible way.
If you have any comments, subscribe to the mailinglist[2] or ask me to
drop the comments.
thanks,
Robert
[1]
https://mail.openjdk.
'll take the maven-plugin-plugin for a ride.
>
>
> Maarten
>
> On 17/08/2021 19:28, Robert Scholte wrote:
>> With JDK 17 appearing soon we should at least release those plugins
>> that depend on ASM.[1]
>> Even though optional, I'll release both the maven-comp
With JDK 17 appearing soon we should at least release those plugins that depend
on ASM.[1]
Even though optional, I'll release both the maven-compiler-plugin and
maven-javadoc-plugin too.
I could use some help with the other plugins too, including verifying if there
are PRs worth adding and the
any project settings.
Or are we mixing up terms here?
NPM does the same, too.
On Mon, 9 Aug 2021, 16:35 Robert Scholte, wrote:
> I'll add it, but it doesn't match the order of GIT[1] as mentioned by
> Michael.
> Maybe there should be a list of other comparable tool
Looking only at the log, both writers existed before it was promoted from the
sandbox in 2007.
Counter was introduced by Karl Heinz while refactoring.
It could very well be there's a better solution for it right now.
I would expect enough coverage by ITs to confirm that.
Robert
On 9-8-2021 16:35:
breaking change, but for maven 4, this seems
reasonable to me.
Am So., 8. Aug. 2021 um 11:48 Uhr schrieb Robert Scholte :
>
> During a discussion with Michael we noticed there's something odd about the
> names of some flags and the order of inheritance.
>
> I've tried to
+1
On 4-8-2021 22:02:18, Michael Osipov wrote:
Hi,
We solved 68 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12349965
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20
During a discussion with Michael we noticed there's something odd about the
names of some flags and the order of inheritance.
I've tried to explain it on a separate wiki page[1] together with the first 3
options how we could fix it.
Please have a look at it and share your thoughts.
thanks,
Robe
Thinks to keep in mind when trying to log for a specific execution of a plugin:
- loggers use the classname as identifier, so you need to know when to the
execution starts and ends.
- plugins can call Maven Core code, most likely you want this to be logged as
part of the plugin execution.
- multi
the impact.
Robert
On 31-7-2021 16:08:36, Michael Osipov wrote:
Am 2021-07-31 um 11:22 schrieb Robert Scholte:
> Right, it is suspend, I misinterpreted the description of server.
>
> Can we introduce an environment variable for it, so CI servers can set it to
> 0?
Let me summarize
might be slow.
M
Am 2021-07-30 um 18:31 schrieb Robert Scholte:
> I wonder if this is a realistic issue. In the cases I know with the
> batch-mode the interactive part is skipped and code falls back to defaults.
> If there are issues, they're more much likely to happen in the inter
build is halted, but more importantly will continue
>*automatically* after it. Just like waiting for a network resource which
>might be slow.
>
>M
>
>Am 2021-07-30 um 18:31 schrieb Robert Scholte:
>> I wonder if this is a realistic issue. In the cases I know with the
>> batch-m
raction with the suspended VM. Both does not make sense.
>>
>> Note: Colors are easier now. They now work just like people are used
>> with grep --color...
>>
>> Am 2021-07-27 um 16:27 schrieb Robert Scholte:
>>> batch mode means no interaction, but the debu
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 w
Hi,
The vote has passed with the following result:
+1 : Hervé BOUTEMY, Michael Osipov, Robert Scholte, Arnaud Héritier
PMC quorum: reached
I will promote the artifacts to the central repo.
On 26-7-2021 23:17:57, Robert Scholte wrote:
Hi,
We solved 37 issues:
https://issues.apache.org/jira
+1
On 26-7-2021 23:17:57, Robert Scholte wrote:
Hi,
We solved 37 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12346527&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=proje
, but if you *only* want to disable colors, you
should use -Dstyle.color=never
Robert
On 27-7-2021 13:56:45, Michael Osipov wrote:
OK, let me sum up what you are proposing:
Am 2021-07-27 um 12:39 schrieb Robert Scholte:
> I actually like the idea of renaming --debug/-X to --verbose/-X a
I actually like the idea of renaming --debug/-X to --verbose/-X and we're
actually lucky.
When renaming we can add a message that --debug for logging at debug level has
been renamed to --verbose.
Due to the nature of debugging (waiting until remote debugger is attached) the
message will be visib
Hi,
We solved 37 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12346527&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317520%20AND%20resolution%20%3D%20Unresolved%20ORDER%20B
ot;, family: "windows"
Is there a better way to get the exact information?
thanks,
Robert
On 19-7-2021 16:20:43, Dalibor Topic wrote:
On 16.07.2021 10:55, Robert Scholte wrote:
> Hi Rory,
>
> thanks for the update.
> We're having 2 issues related to javadoc, one based o
Hi Rory,
I noticed. That means we'll need to adjust our plugin based on the comments
from Jonathan.
thanks,
Robert
On 19-7-2021 09:40:16, Rory O'Donnell wrote:
Hi Robert,
Bug was closed as not an issue, see Jonathan's comments in the bug.
Rgsd,Rory
On 16/07/2021 12:18, Rober
lugin/job/master/site/dist-tool-master-jobs.html
On 16-7-2021 13:38:53, Robert Scholte wrote:
Could this be the issue?
[Jira] No Jira site is configured for this project. This must be a project
configuration error
@Gavin, could you configure this like it was done with ci-builds? Especially
Hi Lee,
next time could you use the maven users list for these kind of questions?
The dev-list is meant for Maven committer discussions.
To answer your question: no, that is not possible.
Toolchain is defined at Maven level, so any maven-plugin or maven-extension can
use it.
This implies that it
Please create a PR for
https://github.com/apache/maven-toolchains-plugin/blob/master/src/site/apt/index.apt.vm
thanks,
Robert
On 17-7-2021 02:44:32, leerho wrote:
The docs page for the maven-toolchains-plugin
has 4
non-working links:
user mailing list ->
https://maven.apache.org/plugins/maven-to
+1
On 17-7-2021 09:45:20, Michael Osipov wrote:
Am 2021-07-14 um 13:41 schrieb Michael Osipov:
> Hi,
>
> We solved 9 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12348391
>
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.o
Could this be the issue?
[Jira] No Jira site is configured for this project. This must be a project
configuration error
@Gavin, could you configure this like it was done with ci-builds? Especially
the credentials seem to be an issue for me.
thanks,
Robert
On 16-7-2021 12:49:30, Robert Scholte
On 16/07/2021 11:46, Rory O'Donnell wrote:
> Hi Robert,
>
> Can you log a couple of bugs, refer to the closed bugs and send the IDs ?
>
> Thanks,Rory
>
> On 16/07/2021 09:55, Robert Scholte wrote:
>> Hi Rory,
>>
>> thanks for the update.
>> We'
Hi Rory,
thanks for the update.
We're having 2 issues related to javadoc, one based on JDK 17-ea+30, the other
one on Oracle OpenJDK 11.0.11 on Windows.
The issue with JDK 17 has to do with stdout and errout.
The maven-javadoc-plugin has a flag to fail on warning, which means: if
something is w
can just add it from the plugins management admin panel.
>
> You just search the missing keyword on jenkins.io to find the plugin
> implementing the missing command.
>
> We should probably document these needs somewhere.
>
> Arnaud
>
> Le ven. 16 juil. 2021 à 10:02, Robe
Robert
On 16-7-2021 09:52:15, Gavin McDonald wrote:
Thanks Robert,
I believe those are a result of missing plugins Ansicolor and Timestamper.
Both now installed
HTH
On Fri, Jul 16, 2021 at 9:31 AM Robert Scholte wrote:
> Okay, that makes sense.
> Jobs have been picked up, just require
FAILURE
I've looked into our Jenkins scripts and and can't find these options. So I
assume these are some globally defined scripts that needs to be repaired.
thanks,
Robert
On 15-7-2021 11:18:34, Gavin McDonald wrote:
Hi
On Thu, Jul 15, 2021 at 11:08 AM Robert Scholte
wrote:
&g
In case you haven't noticed: all Windows nodes are offline.
Robert
On 15-7-2021 10:29:31, Robert Scholte wrote:
Our scripts use the labels ubuntu and Windows to distinguish the OS.
Is it safe to add ubuntu to the maven nodes?
thanks,
Robert
On 15-7-2021 10:06:37, Gavin McDonald wrote:
T
Our scripts use the labels ubuntu and Windows to distinguish the OS.
Is it safe to add ubuntu to the maven nodes?
thanks,
Robert
On 15-7-2021 10:06:37, Gavin McDonald wrote:
Thanks All,
Jobs have been migrated.
Please test and report any issues ASAP to INFRA jira.
https://ci-maven.apache.org
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 projec
Hi,
The vote has passed with the following result:
+1 : Elliotte Rusty Harold, Hervé BOUTEMY, Sylwester Lachiewicz, Robert
Scholte, Michael Osipov, Tamás Cservenák, Arnaud Héritier
PMC quorum: reached
I will promote the artifacts to the central repo.
On 8-7-2021 14:34:19, Robert Scholte
+1
On 8-7-2021 14:34:19, Robert Scholte wrote:
Hi,
We solved 12 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12341375&styleName=Text
There are no issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHAR
Hi,
We solved 12 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12341375&styleName=Text
There are no issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20component%20%3D%20maven-dependency-tree%20AND%20resolutio
Dependency resolution is the heart of Maven and there are only a few that dare
to touch that code.
Answering this is not that easy without good investigation.
I expect that simply removing the exclusions from the cache key will cause
issues.
It might require an extra abstraction layer where GAV
One thing to keep in mind is filtering/interpolation of ${some-key}
-expressions.
But I think it is possible to do it without temporary folder.
Robert
On 2-7-2021 07:18:14, Cai, Eric wrote:
We have a large web project and there is large numbers of dependencies. When we
run "mvn war:war", it us
Should we postpone the alpha-1 release because of this?
For me the most important reason for alpha-1 is to get confirmation that builds
won't be broken due to build/consumer.
But if users simply look at buildtime and due to some slower result don't care
for the other changes, then we shouldn't do
It is probably easier to do a backport of maven-shared-utils with the
vulnerability fix.
Robert
On 27-6-2021 00:48:00, Michael Osipov wrote:
Folks,
I have now back ported a lot of issues to maven-3.8.x which aren't
related to resume, producer/consumer, etc. Many are just an output of
Resolver u
by users of log4j for testing, this name does make
sense to me, similar to spring-test.
Robert
On 22-6-2021 23:20:11, Ralph Goers wrote:
> On Jun 22, 2021, at 11:16 AM, Robert Scholte wrote:
>
> If I understand correctly you want both log4j-core main classes and test
> cl
change was done on June 22 2020:
https://github.com/apache/maven/commit/bdec668de9c600165bb69c95b6ea0625d9f74fb0
before that point in time, there is no issue, isn't it?
then I imagine MNG-5669 and MNG-6824 are safe to cherry pick?
Regards,
Hervé
Le mercredi 23 juin 2021, 11:10:18 CEST R
I would avoid cherrypicking any commit related to the DefaultModelBuilder, this
is just not the same class anymore.
Also don't try to add fixes that has been done with Java 8 features.
To make your life easier I would focus on regressions only.
So I would at least NOT try to include:
- MNG-5669
If I understand correctly you want both log4j-core main classes and test
classes be distributed as modularized jars.
To me with JPMS you should move the modularized test-classes to a separate
Maven module as a first citizen artifact.
That should make it a lot easier.
It should also make the separ
+1
On 14-6-2021 10:46:34, Michael Osipov wrote:
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12350167
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolu
AFAIK the --add-opens is only useful when using the module path. Maven itself
and the plugins use the classpath, so I would like to have an example to better
understand your issue.
thanks,
Robert
On 15-6-2021 18:43:35, Guillaume Nodet wrote:
Hi everyone !
There are some small incompatibilities
There was a regression issue with JAnsi which has now been fixed.
Let's try the latest SNAPSHOT for a week to see if we hit any blockers.
If not, I'll do the release next weekend.
thanks,
Robert
On 29-5-2021 14:58:17, Robert Scholte wrote:
If there are no objections, I'll do t
I don't understand why INFRA-21954 was closed, the issue is still occurring.
I've changed INFRA-21690 to blocker, but still no response.
Robert
On 7-6-2021 15:32:29, Benjamin Marwell wrote:
I also opened
https://issues.apache.org/jira/browse/INFRA-21954
#asfinfra on slack
On Mon, 7 Jun 2021, 1
Well, where is the need for additional namespaces and how they be handled?
The reader has a strict mode, should it fail or ignore unknown tags?
I am aware of one request: adding a namespace on plugins configuration (to
validate its content), however the configuration-element is part of the maven
The title suggest it should me moved completely from the Maven codebase, but I
think there's no alternative for Maven Core, as we need quite a huge set of
features. I don't think there's another tool that can keep the model, reader,
writers, mergers, validators and xsd in sync. If you want to re
Someone needs to implement #563525[1]
I've had the confirmation that increasing source/target of Java makes sense.
thanks,
Robert
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=563525
On 29-5-2021 16:07:50, Gary Gregory wrote:
Hi All,
How do I use a @Parameter on a NIO Path?
I don't a plac
If there are no objections, I'll do the release next week.
Robert
On 23-5-2021 11:43:54, Martin Kanters wrote:
Hi all,
With MNG-6915 [1] being merged yesterday, all Jansi-related PRs are merged.
AFAIK there is nothing pressing left for the Maven 4.0.0-alpha-1 release,
or am I missing something?
Hi,
On behalf of the Apache Maven PMC I am pleased to announce that
Guillaume Nodet has been voted in as new Apache Maven committer
and he has accepted this invitation.
Welcome on board and have a lot of fun!
Thanks,
Robert Scholte
g an
uploaded pom rather than the local one. To make it clear why, what about -o
builds? What does "uploaded" really mean?
But yes, the two-poms stepping stone makes it clear why the bump, that's a
big departure from the past.
Cheers,
Fred.
On Sun, 23 May 2021 at 22:58, Robert Scho
TLDR; Most things will still work, but some things will break.
Maven 4 is the preparation for Maven 5, where we will be able to introduce a
new pom model. To keep the Maven eco system stable, it must be possible to
upload model 4.0.0 compatible poms to remote repositories, especially to
Central
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 proj
Hi,
The vote has passed with the following result:
+1 : Robert Scholte, Hervé BOUTEMY, Frederik Boster, Arnaud Héritier, Michael
Osipov
PMC quorum: reached
I will promote the artifacts to the central repo.
On 18-5-2021 20:43:37, Robert Scholte wrote:
Hi,
We solved 28 issues:
https
Dear all,
I need some extra votes in order to release this.
thanks,
Robert
On 18-5-2021 20:43:37, Robert Scholte wrote:
Hi,
We solved 28 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12346637&styleName=Text
There are still a couple of issues
+1
On 18-5-2021 20:43:37, Robert Scholte wrote:
Hi,
We solved 28 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12346637&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20
Hi,
We solved 28 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12346637&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317529%20AND%20resolution%20%3D%20Unresolved%20ORDER%20B
The codebase of Maven is over 15 years old and you can clearly see that it has
evolved over the years. This implies that sometimes we've decided to move
classes from one jar to the other.
On the classpath this is not an issue and as Maven is using only the classpath
to run there is no issue here
1 - 100 of 2562 matches
Mail list logo
