Skip to content

Migrate from javax.inject/annotation to jakarta.inject/annotation#1255

Merged
HannesWell merged 1 commit intoeclipse-platform:masterfrom
HannesWell:javax-to-jakarta
Oct 30, 2023
Merged

Migrate from javax.inject/annotation to jakarta.inject/annotation#1255
HannesWell merged 1 commit intoeclipse-platform:masterfrom
HannesWell:javax-to-jakarta

Conversation

@HannesWell
Copy link
Copy Markdown
Member

@HannesWell HannesWell marked this pull request as draft October 28, 2023 17:09
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Oct 28, 2023

Test Results

     900 files  ±0       900 suites  ±0   1h 37m 58s ⏱️ + 5m 18s
  7 450 tests ±0    7 294 ✔️ +1  156 💤 ±0  0  - 1 
23 499 runs  ±0  22 981 ✔️ +1  518 💤 ±0  0  - 1 

Results for commit 038bbd6. ± Comparison against base commit 2ddad73.

♻️ This comment has been updated with latest results.

@HannesWell HannesWell marked this pull request as ready for review October 28, 2023 17:12
@mickaelistria
Copy link
Copy Markdown
Contributor

If not already done (the change is too big to easily ensure it),can we keep 1 small test with javax.inject to ensure backward-compatibility?

@HannesWell
Copy link
Copy Markdown
Member Author

If not already done (the change is too big to easily ensure it),can we keep 1 small test with javax.inject to ensure backward-compatibility?

The org.eclipse.e4.core.tests, which seem to test most of the injector and associated classes are currently still using the javax annotations. My suggestion is to just duplicate all the tests into a second test-plugin org.eclipse.e4.core.javax.tests that duplicates the tests as they are (using javax) and then the 'original' tests are migrated to the jakarta annotations as well.
When removing javax support the project org.eclipse.e4.core.javax.tests can then be deleted too.
But that is the in eclipse.platform and we could completely eclipse.platform.ui.

@laeubi
Copy link
Copy Markdown
Contributor

laeubi commented Oct 29, 2023

My suggestion is to just duplicate all the tests into a second test-plugin

Do we really need a seperate plugin or is a dedicated package sufficient?

@HannesWell
Copy link
Copy Markdown
Member Author

My suggestion is to just duplicate all the tests into a second test-plugin

Do we really need a seperate plugin or is a dedicated package sufficient?

I'm currently working on making the javax annotations optional and therefore would like to have for the jakarta-annotations tests a test-runtime (at least with Tycho) that does not contain the javax-annotations to verify if that really works.

@HannesWell HannesWell force-pushed the javax-to-jakarta branch 3 times, most recently from e688d69 to 6e3ad29 Compare October 29, 2023 17:43
@HannesWell
Copy link
Copy Markdown
Member Author

If not already done (the change is too big to easily ensure it),can we keep 1 small test with javax.inject to ensure backward-compatibility?

The org.eclipse.e4.core.tests, which seem to test most of the injector and associated classes are currently still using the javax annotations. My suggestion is to just duplicate all the tests into a second test-plugin org.eclipse.e4.core.javax.tests that duplicates the tests as they are (using javax) and then the 'original' tests are migrated to the jakarta annotations as well. When removing javax support the project org.eclipse.e4.core.javax.tests can then be deleted too. But that is the in eclipse.platform and we could completely eclipse.platform.ui.

I have now created eclipse-platform/eclipse.platform#791 for that purpose.

@mickaelistria
Copy link
Copy Markdown
Contributor

I have now created eclipse-platform/eclipse.platform#791 for that purpose.

Thanks!

@HannesWell HannesWell merged commit 6b2c1d1 into eclipse-platform:master Oct 30, 2023
@HannesWell HannesWell deleted the javax-to-jakarta branch October 3, 2024 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants