>> Regarding javax: No, this was not the free decision of the Jakarta EE WG,
>> this was the SOLE CHOICE we had due to Oracle, as they forbid ALL changes
>> to the javax namespace, so the were FORCED to rename the workspace. Believe
>> me, nobody in the Jakarta EE WG thought that this is a good
urally different.
>
> -Markus
>
>
> -Ursprüngliche Nachricht-
> Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> Gesendet: Montag, 28. Dezember 2020 17:14
> An: Maven Developers List
> Betreff: Re: Maven 4 / @Inject
>
> Le lun. 28 déc. 2020 à 16:44, Ma
-Ursprüngliche Nachricht-
Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet: Montag, 28. Dezember 2020 17:14
An: Maven Developers List
Betreff: Re: Maven 4 / @Inject
Le lun. 28 déc. 2020 à 16:44, Markus KARG a écrit :
> I don't like the idea of simply keeping javax "an
> Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
> Gesendet: Montag, 28. Dezember 2020 16:16
> An: Maven Developers List
> Betreff: Re: Maven 4 / @Inject
>
> We can also freeze it, jsr330 never moved and will likely never move (since
> it is the most of the overlapping of u
lternative.
-Markus
-Ursprüngliche Nachricht-
Von: Romain Manni-Bucau [mailto:rmannibu...@gmail.com]
Gesendet: Montag, 28. Dezember 2020 16:16
An: Maven Developers List
Betreff: Re: Maven 4 / @Inject
We can also freeze it, jsr330 never moved and will likely never move (since
it i
er classes nor interfaces nor even new parameters.
>
> I would like that Maven 4 accepts both (old and new namespace).
>
> -Markus
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: Michael Osipov [mailto:micha...@apache.org]
> Gesendet: Montag, 28. Dezember 2020 14:59
apache.org]
Gesendet: Montag, 28. Dezember 2020 14:59
An: dev@maven.apache.org
Betreff: Re: Maven 4 / @Inject
Am 2020-12-28 um 14:56 schrieb Markus KARG:
> We are used to "import javax.inject.*" in Maven, but that namespace if
dead
> since Jakarta EE 9. Since November the new nam
If you think about such a change - Maven 4 should support both namespaces
with warning about deprecating javax.inject.
In this way developers will have more time and possibility to switch their
plugins/extensions to new namespaces.
Finally Maven 5 can support only new namespaces.
pon., 28 gru
I agree javax will stay for years and doing any breaking change today would
just be bad for end users, that said we can already encourage plugins to
not use it and log a warning in maven plugin plugin.
For maven core we don't care much since we can change it when we want, it
will just impact
Am 2020-12-28 um 14:56 schrieb Markus KARG:
We are used to "import javax.inject.*" in Maven, but that namespace if dead
since Jakarta EE 9. Since November the new namespace is released "import
jakarta.inject.*". I wonder if Maven 4 really still wants to stick with the
dead namespace instead, or
We are used to "import javax.inject.*" in Maven, but that namespace if dead
since Jakarta EE 9. Since November the new namespace is released "import
jakarta.inject.*". I wonder if Maven 4 really still wants to stick with the
dead namespace instead, or whether it makes sense that we adopt the new
11 matches
Mail list logo
