On Wed, 22 Mar 2023 at 17:13, Tamás Cservenák <[email protected]> wrote: > > Olivier, > > you are wrong on multiple topics here, please read this: > https://eclipse-foundation.blog/2019/05/03/jakarta-ee-java-trademarks/
Yes I know this page. It says " The Agreement does allow for modification and evolution under a new namespace, such as jakarta. It is expected that all future evolution and innovation will not use the javax namespace. " So I'm just saying specifications are here https://github.com/jakartaee/specifications/tree/master/dependency-injection I do not really use deprecated in the Java technical way but more in the historical way and about the future of dependency injection. version 2.0 is here so version 1.0 is dead/legacy now. The future is with the new namespace, nothing related to living in Jakarta EE or not. As far I can see those packages are not part of the standard jdk distribution and managed here https://github.com/jakartaee/specifications/ > > - nothing is "deprecated", merely Eclipse led community agreed (broadly > spoken, maybe "was nudged by Oracle") to move to jakarta namespace, to be > able to evolve/modify APIs > - BUT, we use artifact > https://repo.maven.apache.org/maven2/javax/inject/javax.inject/1/ since > 2010 in it's unmodified form > - AND, we do not impose (plan nor want) any change to it ("we" -> guice, > sisu or maven), we just use it "as is" > - we are not in any way in relation to Java EE or Jakarta EE > - strictly spoken, Sisu implements original JSR330 spec and that's it > > So to recap: > - in Maven ecosystem Plexus Components ARE deprecated is there any technical deprecated flag somewhere? > - in Maven ecosystem JSR330 is NOT deprecated > - javax.inject namespace is NOT deprecated (unless you live in Jakarta EE > space and are pulled by community/gravity) > > Thanks > T > > On Wed, Mar 22, 2023 at 1:43 AM Olivier Lamy <[email protected]> wrote: > > > The issue with the title `Drop plexus legacy` doesn't look to have a > > correct title. > > The code is moving to use javax.inject namespace. > > As far I can see this package is deprecated and now replaced with > > jakarta.inject. > > So it looks like moving to something else which is already deprecated. > > maybe find a more appropriate title. or just keep the current code and > > later move to jakarta.inject when it will be supported.. > > > > > > On Tue, 21 Mar 2023 at 22:10, Tamás Cservenák <[email protected]> wrote: > > > > > > Howdy, > > > > > > NOTE: > > > This release depends on maven-filtering-3.3.1: > > > https://lists.apache.org/thread/8459pzrrjzmo6gpn0wzykmdp9t109xc7 > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1898/ > > > > > > > > > We solved 8 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827&version=12352140 > > > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/projects/MRESOURCES/issues > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1899/ > > > > > > Source release checksum(s): > > > > > 47598a6c1775405679aa111fc6aa48fc331c182a2c7847297d24289671e03ee109781c760cd5afcc54639a34bd8b74ecebeab4fec4d659e1d0f90accecaa754c > > > > > > Staging site: > > > https://maven.apache.org/plugins-archives/maven-resources-plugin-LATEST/ > > > > > > Guide to testing staged releases: > > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > Vote open for 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
