Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excavator: Allow Java 17 language features in all modules #7306

Open
wants to merge 9 commits into
base: develop
Choose a base branch
from

Conversation

svc-excavator-bot
Copy link
Collaborator

@svc-excavator-bot svc-excavator-bot commented Oct 1, 2024

excavator is a bot for automating changes across repositories.

Changes produced by the roomba/java-17-library-target check.

To enable or disable this check, please contact the maintainers of Excavator.

Also upgrade all references from javax to jakarta.

@tillyow
Copy link
Contributor

tillyow commented Oct 4, 2024

Needs a Jakarta migration, blocked

@@ -1518,7 +1518,7 @@ private SingleBatchSweeper getSingleShardSweeper(SettableFuture<MultiTableSweepQ
*/
private TimelockService createStickyLockService() {
AtomicLong lockToken = new AtomicLong(0);
Set<LockDescriptor> requestedLocks = new ConcurrentHashSet<>();
Set<LockDescriptor> requestedLocks = ConcurrentHashMap.newKeySet();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note this code change - only for tests though.

@fsamuel-bs
Copy link
Contributor

Documenting for my future self:

  • upgrading to java 17 fails because we use some dropwizard extensions in tests that use reflection
  • upgrading to later dropwizard requires javax -> jakarta migration
  • we rely on some dependencies (from Cassandra 2.x) which still use javax, and not sure we can migrate them
  • currently last build is failing because we're not finding in the test runtime classpath jakarta.el classes.

@@ -96,7 +96,7 @@ public Set<String> getSupportedAnnotationTypes() {

@Override
public SourceVersion getSupportedSourceVersion() {
return SourceVersion.RELEASE_11;
return SourceVersion.RELEASE_17;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can update this to return SourceVersion.latestSupported(); e.g. https://github.com/palantir/delegate-processors/blob/43e5fed7e639e1162e4ccc53e177f4abf3d08915/delegate-processors/src/main/java/com/palantir/delegate/processors/DelegateProcessor.java#L68-L71
that way we don't have to think about it for each upgrade. I'd propose making this sort of change onto develop, so we can rebase the jdk-17 bump and keep it minimal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants