slawekjaranowski opened a new pull request, #15:
URL: https://github.com/apache/maven-xinclude-extension/pull/15
(no comment)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
gnodet commented on PR #12:
URL:
https://github.com/apache/maven-hocon-extension/pull/12#issuecomment-2503057895
@dependabot recreate
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
gnodet merged PR #11:
URL: https://github.com/apache/maven-hocon-extension/pull/11
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@maven
gnodet merged PR #10:
URL: https://github.com/apache/maven-hocon-extension/pull/10
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@maven
gnodet merged PR #13:
URL: https://github.com/apache/maven-hocon-extension/pull/13
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@maven
gnodet commented on PR #12:
URL:
https://github.com/apache/maven-xinclude-extension/pull/12#issuecomment-2503055744
@dependabot recreate
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the speci
gnodet merged PR #10:
URL: https://github.com/apache/maven-xinclude-extension/pull/10
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@ma
gnodet merged PR #13:
URL: https://github.com/apache/maven-xinclude-extension/pull/13
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@ma
gnodet merged PR #11:
URL: https://github.com/apache/maven-xinclude-extension/pull/11
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@ma
gnodet merged PR #14:
URL: https://github.com/apache/maven-xinclude-extension/pull/14
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@ma
+1 (NB)
Successfully tested on a 61 module internal app suite. Notables:
* AnsiConsole removal caused a docker-maven-plugin CNFE and thankfully it
has a recent release fixing that.
* Exposed a Spring GraphQL schema classpath file search configuration
issue, worked around by overriding the default
Cancelling this vote, let's rename the package and cut a new release.
Le mar. 26 nov. 2024 à 11:50, Guillaume Nodet a écrit :
> Hi,
>
> This release mainly updates to Maven 4.0.0-beta-5 (the API is compatible
> with rc-1) and align the groupId.
>
> Release notes (visibility is limited to committ
Yes, you already pointed to those. I don't really think they apply to our
libraries.
The reason is that they are usually used as direct dependencies of Maven
plugins, which do not share classloaders, so the risk of ending up with the
same library from two different coordinates is very minimal.
Fur
The issue occurs because now both version 3 and 4 jars can show up in
the classpath, and then it might as well be random which one comes
first and is loaded. If JPMS is in play, split packages can prevent
the app from running at all.
See https://jlbp.dev/JLBP-6
On Tue, Nov 26, 2024 at 1:53 PM Gui
+1
tested on an internal project
I am still not fan of all warnings related to imports but I don't see a
better solution to make developers aware of conflicts and their risks
On Tue, Nov 26, 2024 at 1:51 PM Mateusz Gajewski <
mateusz.gajew...@starburstdata.com> wrote:
> +1 nb, tested on Trino
>
Btw, this is a major version bump because the re are incompatible changes,
so I’m not really sur how not changing the groupId will really help. You
may limit the chances you end up with 2 different artifacts, but it won’t
reduce the chances of having the wrong one.
Guillau
+1 nb, tested on Trino
On Tue, Nov 26, 2024 at 1:26 PM Guillaume Nodet wrote:
> +1
>
> Le lun. 25 nov. 2024 à 12:50, Tamás Cservenák a
> écrit :
>
> > Howdy,
> >
> > We solved 46 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12355164
> >
> >
+1
Le lun. 25 nov. 2024 à 12:50, Tamás Cservenák a
écrit :
> Howdy,
>
> We solved 46 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12355164
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%
I can revert the groupId change as the package is fine, so I don't see why
we'd need to change it.
Le mar. 26 nov. 2024 à 13:05, Elliotte Rusty Harold a
écrit :
> -1
>
> Changing the group ID without simultaneously changing the package name
> is a recipe for classpath conflicts and hard to diag
-1
Changing the group ID without simultaneously changing the package name
is a recipe for classpath conflicts and hard to diagnose bugs at
runtime.
On Tue, Nov 26, 2024 at 10:51 AM Guillaume Nodet wrote:
>
> Hi,
>
> This release mainly updates to Maven 4.0.0-beta-5 (the API is compatible
> with
Hi,
This release mainly updates to Maven 4.0.0-beta-5 (the API is compatible
with rc-1) and align the groupId.
Release notes (visibility is limited to committers):
https://github.com/apache/maven-archiver/releases/edit/untagged-c2daca1bd952f3aa7e9f
Gist of the above for non committers:
https://g
Hey,
Note: mvnd 1.x wraps Maven 3.9.x and 2.x wraps Maven 4.x.
This release provides distributions based on Apache Maven 4.0.0-rc-1.
Note that the above release is still under vote, so this release will be
cancelled if 4.0.0-rc-1 is not voted.
The release candidate is here:
https://dist.apache.o
Le mar. 26 nov. 2024 à 07:30, Delany a écrit :
> 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
>
>
23 matches
Mail list logo
