Howdy,
Basil's issue is made me realize:
o.c.p:p-u 4.x that depends on
-> o.c.p:p-xml 4 that depends on
-> o.a.m:m-api-xml that depends on
-> o.a.m:m-api-meta
This means that p-u pulls in new Maven4 API bits.
Hence, Maven 3 plugin, that is built against maven-plugin-api 3.x, if
switched to p-u 4,
I raised this issue in
https://github.com/jenkinsci/maven-hpi-plugin/pull/490#issuecomment-1557970717
but did not receive a response.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-
Howdy,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12348840
There are still some issues in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20%22Ant%20Tasks%22
Adding my last 5 cents and will stop here:
- as you know, my goal is to push through the door latest Maven 3.x (3.9.5)
and Resolver 1.x (1.9.16)
- in a moment that happens, declare Maven 3.x and Resolver 1.x "bugfix
only" -- and we should focus on Maven 4
- hence, for this, simplest would be to de
I disagree here (or would like to have us be very cautious here):
- the reason why p-u XML bits are exported are Modello generated models
only (as they may have fiels like Xpp3Dom and generated IO classes uses XML
bits as well)
- plugins should remain capable to interact with Modello generated mod
On Tue, Jul 25, 2023 at 8:57 PM Slawomir Jaranowski
wrote:
> It is very magical that we export classes but not export artifact
> which contains those classes ...
>
>
So, just to clear up:
For ref http://takari.io/book/91-maven-classloading.html
In relation to
https://github.com/apache/maven/blo
+1
On Fri, 8 Sept 2023 at 03:40, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12353576
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%
+1
On Thu, Sep 7, 2023 at 7:40 PM Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12353576
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20
+1
pt., 8 wrz 2023, 07:59 użytkownik Herve Boutemy
napisał:
> +1
>
> Reproducible Build ok: reference build done with JDK 17 on *nix with umask
> 022
>
> Regards,
>
> Hervé
>
> On 2023/09/07 17:39:48 Slawomir Jaranowski wrote:
> > Hi,
> >
> > We solved 2 issues:
> >
> https://issues.apache.org/j
Thanks, I will create an IT for it.
Good idea to describe the migration from plexus 3.x to 4.x.
pt., 8 wrz 2023 o 10:26 Guillaume Nodet napisał(a):
> I've raised MNG-7873.
> Slawomir, do you think you could create an IT for that ?
> I'll try to provide a fix asap, but a clean IT would make sure
I've raised MNG-7873.
Slawomir, do you think you could create an IT for that ?
I'll try to provide a fix asap, but a clean IT would make sure the problem
is actually fixed.
I think we should also update the plexus-utils release notes with some more
information about the migration to 4.x when using
I think we need to expose the missing class before cutting a release, see
https://lists.apache.org/thread/ltd1g1dbv0lqqdw5q941gmrkfyn6m87m
I've raised MNG-7873 for that.
Le jeu. 7 sept. 2023, 16:18, Tamás Cservenák a écrit :
> Howdy,
>
> Just a heads up, that am targeting following releases:
>
12 matches
Mail list logo
