-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
Upgrade Guava from 11.0.1 to latest
-
Jenkins core is using Guava 11.0.1, which was released on January 9, 2012. Jenkins core would like to upgrade to Guava 30.1.1, which was released on March 19, 2021. Plugins must be prepared to be compatible with both Guava 11 and Guava 30 in advance of this core transition.
Ideally, such plugins would be prepared by rewriting usages of Guava to native Java Platform functionality whenever possible. For example, instead of using ImmutableList, try Collections#unmodifiableList. Instead of using Joiner, try String#join or Collectors#joining.
If the plugin must use Guava, then limit usage to the set of methods that are present in both Guava 11 and Guava 30.
- is duplicated by
-
JENKINS-63755 Any plans to update guava in Jenkins Core?
-
- Closed
-
- links to
[JENKINS-65988] Upgrade Guava from 11.0.1 to latest
| Epic Child |
New:
|
| Link |
New:
This issue is duplicated by |
| Epic Child |
New:
|
| Epic Child |
New:
|
| Epic Child |
New:
|
| Epic Child |
New:
|
| Epic Child |
New:
|
| Description |
Original:
Guava is version 11.0.1 in Jenkins Core. This version is from 2012. Keeping dependencies updated is important.
Ideally, we should also look into how we can make such a bump easier next time. |
New:
Guava is version 11.0.1 in Jenkins Core. This version is from 2012. Keeping dependencies updated is important.
Ideally, we should also look into how we can make such a bump easier next time. |
| Epic Child |
New:
|
Basil Crow
made changes -
| Description |
Original:
Guava is version 11.0.1 in Jenkins Core. This version is from 2012. Keeping dependencies updated is important.
Ideally, we should also look into how we can make such a bump easier next time. |
New:
Jenkins core is using [Guava 11.0.1|https://github.com/google/guava/releases/tag/v11.0.1], which was released on January 9, 2012. Jenkins core would like to upgrade to [Guava 30.1.1|https://github.com/google/guava/releases/tag/v30.1.1], which was released on March 19, 2021. Plugins must be prepared to be compatible with both Guava 11 and Guava 30 in advance of this core transition.
Ideally, such plugins would be prepared by rewriting usages of Guava to native Java Platform functionality whenever possible. For example, instead of using {{ImmutableList}}, try {{Collections#unmodifiableList}}. Instead of using {{Joiner}}, try {{String#join}} or {{Collectors#joining}}. If the plugin must use Guava, then limit usage to the set of methods that are present in both Guava 11 and Guava 30. |