[wildfly-dev] Possible component upgrades report - Wildfly Core

[Brian Stansberry]

On Sun, Oct 20, 2019 at 3:50 AM <thofman at redhat.com> wrote:

> Generated at 16:49:31 SGT 2019-10-20
>
> Searched in following repositories:
>
> * Central: https://repo1.maven.org/maven2/
> * JBossPublic:
> https://repository.jboss.org/nexus/content/repositories/public/
>
> Possible upgrades:
>
> com.jcraft:jsch:0.1.54 -> 0.1.55 (Central)
> com.jcraft:jzlib:1.1.1 -> 1.1.3 (Central)
> org.apache.httpcomponents:httpclient:4.5.4 -> 4.5.10 (Central)
> org.apache.httpcomponents:httpcore:4.4.5 -> 4.4.12 (Central)
> org.apache.maven:maven-resolver-provider:3.5.0 -> 3.5.4 (Central)
> org.apache.maven.resolver:maven-resolver-api:1.1.0 -> 1.1.1 (Central)
> org.codehaus.plexus:plexus-utils:3.1.0 -> 3.1.1 (Central)
>

https://github.com/wildfly/wildfly-core/pull/3993 is for the 3 above


> org.eclipse.jgit:org.eclipse.jgit:5.0.2.201807311906-r ->
> 5.0.3.201809091024-r (Central)
> org.jboss.remotingjmx:remoting-jmx:3.0.3.Final -> 3.0.4.CR1-SNAPSHOT
> (JBossPublic)
>

Looks like the tool needs a tweak to ignore -SNAPSHOT, and also to ignore
CR and RC versions. (The report for full wildfly includes a line with an RC
version.)

> org.jboss.slf4j:slf4j-jboss-logmanager:1.0.3.GA -> 1.0.4.GA (Central)
> org.jboss.spec.javax.security.auth.message:jboss-jaspi-api_1.1_spec:2.0.1.Final
> -> 2.0.2.CR1-SNAPSHOT (JBossPublic)
> org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec:2.0.0.Final ->
> 2.0.2.CR1-SNAPSHOT (JBossPublic)
> org.slf4j:jcl-over-slf4j:1.7.22.jbossorg-1 -> 1.7.28 (Central)
>
> 13 items
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>


-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20191020/dd3268e5/attachment.html