Hi,
The vote has passed with the following result:
+1: Jason Van Zyl, Herve Boutemy, Slawomir Jaranoswski, Olivier Lamy
+0: --
-1: --
PMC quorum: reached
I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.
T
+1
On Tue, 31 May 2022 at 21:26, Tamás Cservenák wrote:
> Howdy,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12351791
>
> There are still some issues left in JIRA:
> https://issues.apache.org/jira/projects/MINDEXER/
>
> Staging re
+1
- build ok
- sign ok by key 0xD53C5C58A3E173D18AEDF6E993450DF2DF9A3FA3
wt., 31 maj 2022 o 19:57 Andreas Dangel napisał(a):
> Hi,
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351350&styleName=Text&projectId=12317621
>
> There are still a couple
+1
- build ok from source-release.zip
- sig ok by key 0x29BEA2A645F2D6CED7FB12E02B172E3E156466E8
wt., 31 maj 2022 o 13:26 Tamás Cservenák napisał(a):
> Howdy,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12351791
>
> There are sti
Le jeu. 2 juin 2022 à 11:47, Stuart McCulloch a écrit :
> Sorry, I was just struggling to see where exposing JSR330 has negatively
> impacted users in practice (ie excluding anything related to exposing CDI)
>
> For the CDI API sure, when that was exposed we didn't anticipate that the
> CDI spec
Sorry, I was just struggling to see where exposing JSR330 has negatively
impacted users in practice (ie excluding anything related to exposing CDI)
For the CDI API sure, when that was exposed we didn't anticipate that the
CDI spec would evolve how it did - so removing that is logical - but when
th
@Stuart: api validating or enforcing classloader in mojo need workarounds
since you will use javax.inject from maven and not from your mojo
container/code (embedding an OSGi container can have this issue in some
cases without much hack but most container using classloaders will hit it,
I hit it at
Maybe design document and later with PoC API, implementation is something
that we missed and You can help here to solve this problem for users, based
on real case from You?
Br
Sylwester
czw., 2 cze 2022, 10:57 użytkownik Romain Manni-Bucau
napisał:
> Hi Stuart,
>
> Not really, they relate to c
Could you highlight which one was specifically an issue with JSR330 (ie. an
actual issue, not a theoretical one) and not the CDI API as I must have
missed it?
On Thu, 2 Jun 2022, 09:57 Romain Manni-Bucau, wrote:
> Hi Stuart,
>
> Not really, they relate to cdi or atinject spec and explain why we
Hi Stuart,
Not really, they relate to cdi or atinject spec and explain why we must not
expose it to plugins - and more generally how exposing standard or
mainstream API does not reach our isolation goal for plugins.
Concretely our maven-core extension.xml file should not list any
javax/jakarta pac
Thanks - afaict those all relate to the CDI API which was previously only
added so people could use the @Typed annotation during early migration away
from Plexus specifics (this is not required by the container, it's an
optional dependency)
As mentioned before I only know of one external extension
+1
Reproducible Build checked: reference build was done with JDK 8 on *nix
Regards,
Hervé
Le mercredi 1 juin 2022, 23:01:47 CEST Olivier Lamy a écrit :
> +1
>
> On Wed, 1 Jun 2022 at 03:57, Andreas Dangel wrote:
> > Hi,
> >
> > We solved 15 issues:
> >
> > https://issues.apache.org/jira/sec
Hi
Sorry for the delay.
Here what I found back but an be worth checking other project mailing lists
since it often leads to dirty workarounds:
- https://lists.apache.org/thread/wlocsqglzsn18g3o4vc8721gm3nmn99x
- https://lists.apache.org/thread/d9rhh61yy1mtorcc7n6v903rs24md649
- https://lists.apa
13 matches
Mail list logo
