You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a discussion starter: "what do we plan with jakarta namespace"?
Guice released "transitional" 6.0.0 (supporting both, javax and jakarta) and 7.0.0 (supporting jakarta only).
Apps using sisu built from the scratch may want to choose jakarta, while Maven (due legacy, especially 4.x) may want to "sit tight" on javax still.... (just to note, supporting newer bytecode is doable with "external asm").
The text was updated successfully, but these errors were encountered:
Supporting jakarta annotations would be great.
The Eclipse E4 Dependency Injector is currently capable to handle both, jakarta and javax annotations and is prepared to handle the absence of javax annotations in the runtime (jakarta absence would of course be possible). Just in case you want to use a similar strategy: eclipse-platform/eclipse.platform#792
The question is how to implement this in the SpaceModule and ClassFinder? Does the user need to select one of both, or should there be scanned for both?
Just a discussion starter: "what do we plan with jakarta namespace"?
Guice released "transitional" 6.0.0 (supporting both, javax and jakarta) and 7.0.0 (supporting jakarta only).
Apps using sisu built from the scratch may want to choose jakarta, while Maven (due legacy, especially 4.x) may want to "sit tight" on javax still.... (just to note, supporting newer bytecode is doable with "external asm").
The text was updated successfully, but these errors were encountered: