It might need a cleanup. I' going to move it to public GitHub repo, it
doesn't need to be private, and will set Jandex to report minor
versions.
Thanks!
Tomas
On Wed, 2023-06-28 at 11:05 -0500, Brian Stansberry wrote:
Hi Tomas,
Do you know why Jandex 3.1.x isn't on this report? Is it because this
is a different minor version? If so, can we add a configuration
rule[1] for io.smallrye:jandex so it proposes the MICRO stream?
I'm not sure where the config that generates this email is
maintained; otherwise I'd be happy to send up a PR.
Hi Everyone, particularly Ladicek!
Any objections to getting notifications of available minor updates of
Jandex? The Jandex project is run in such a way that minor updates
are likely a good fit for WF and should be suggested.
[1]
https://github.com/jboss-set/maven-dependency-updater#configuration
Best regards,
Brian
On Fri, Jun 23, 2023 at 11:48 AM <thofman(a)redhat.com> wrote:
> Component Upgrade ReportFollowing repositories were searched:
> * Central
https://repo1.maven.org/maven2/
> * JBossPublic
>
https://repository.jboss.org/nexus/content/repositories/public/
> Possible Component UpgradesGAVNew VersionRepositorySince
> org.bouncycastle:bcjmail-jdk18on:1.731.75Centralnew
> 1 items
> Generated on 2023-06-23
> Report generated by Maven Dependency Updater
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
--
Brian StansberryPrincipal Architect, Red Hat JBoss EAP
He/Him/His