Vaadin 25: Compilation failure (package javax.annotation does not exist)

[javier-godoy]

Describe the bug

[ERROR] MenuItemDto.java:[25,24] package javax.annotation does not exist
[ERROR] MenuItemDto.java:[30,6] cannot find symbol
[ERROR] symbol: class Nullable
[ERROR] location: class com.flowingcode.addons.applayout.endpoint.MenuItemDto

Expected behavior

mvn clean compile -Pv25

Minimal reproducible example

No response

Add-on Version

6.1.1-SNAPSHOT

Vaadin Version

25.0.0

Additional information

No response

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Fix Javadoc warnings #130
• Align demos with the structure of AddonStarter #128
• Vaadin 25: demo not showing in full height as expected #144
• Fixed and Reveals #135

🔗 Related PRs

#122 - Update to 24.4.4 [merged]
FlowingCode/CommonsDemo#122 - feat: add compatibility with Vaadin 25 [merged]

👤 Suggested Assignees

• javier-godoy
• paodb
• mlopezFC

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[javier-godoy]

The annotation was available via a transitive dependency of hilla. The use of @Nullable was added in ee61017 (#76)

In Vaadin 24 the annotation was available via transitive dependencies of flow-server and reflections,

[javier-godoy]

Since version 6.x is NOT compatible with Vaadin 23, it should have been jakarta @Nullable (which was already available). Note that hilla does not check the fully qualified name of the annotation, so anything named "Nullable" works.