The Maven central version of proprot uses an old version of guava which is affected by several vulnerabilities.
<dependencies>
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>23.0</version>
</dependency>
</dependencies>
I see in current master a more recent one is used.
See :
|
<dependency> |
|
<groupId>com.google.guava</groupId> |
|
<artifactId>guava</artifactId> |
|
<version>32.0.1</version> |
|
</dependency> |
|
</dependencies> |
Is there any plan to release a new version ? (maybe overkill for just a simple dependency update )
Waiting a release are available, users can still use a more recent version of guava via dependencyManagement :
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>${guava.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
But with not so much guarantee that there will not have some compatibility issue...
(For that ☝️, this could help a little but this is no more up to date)
The Maven central version of proprot uses an old version of guava which is affected by several vulnerabilities.
I see in current
mastera more recent one is used.See :
elastic-load-balancing-tools/proprot/pom.xml
Lines 82 to 87 in e39fb8a
Is there any plan to release a new version ? (maybe overkill for just a simple dependency update )
Waiting a release are available, users can still use a more recent version of guava via dependencyManagement :
But with not so much guarantee that there will not have some compatibility issue...
(For that ☝️, this could help a little but this is no more up to date)