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
Improve Maven configuration and document known Java/Maven warnings
- Update compiler configuration to use --release 21 instead of source/target
- Fixes 'location of system modules not set' warnings
- Add Known Issues section to README documenting harmless sun.misc.Unsafe warnings
- These warnings come from Maven's bundled Guice, not from our library code
- Warnings are harmless and will be resolved when Maven updates Guice version
Copy file name to clipboardExpand all lines: README.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,4 +125,16 @@ For each `@DynamoMappable` class, the processor generates:
125
125
-**Bidirectional methods**: `toDynamoDbAttributeValue()` and `fromDynamoDbAttributeValue()`
126
126
-**Dependency injection**: Constructor injection for required mappers
127
127
-**Null safety**: Proper null handling throughout mapping logic
128
-
-**Error handling**: Safe parsing with fallback to null values
128
+
-**Error handling**: Safe parsing with fallback to null values
129
+
130
+
## Known Issues
131
+
132
+
### Java/Maven Compatibility Warnings
133
+
134
+
When using Java 21+ with Maven, you may see warnings like:
135
+
```
136
+
WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
137
+
WARNING: sun.misc.Unsafe::staticFieldBase has been called by com.google.inject.internal.aop.HiddenClassDefiner
138
+
```
139
+
140
+
These warnings are **harmless** and come from Google Guice (bundled with Maven), not from this library. They will be resolved when Maven updates to a newer Guice version. The warnings do not affect functionality and can be safely ignored.
0 commit comments