11:05 a.m.
New subject: Jandex update proposals [Was:] Possible component upgrades report - Wildfly_Core
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 Report
Following repositories were searched:
- Central https://repo1.maven.org/maven2/
- JBossPublic
https://repository.jboss.org/nexus/content/repositories/public/
Possible Component Upgrades
GAVNew VersionRepositorySince
org.bouncycastle:bcjmail-jdk18on:1.73 1.75 Central new
1 items
Generated on 2023-06-23
Report generated by Maven Dependency Updater
<https://github.com/jboss-set/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 Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
11:21 a.m.
New subject: Jandex update proposals [Was:] Possible component upgrades report - Wildfly_Core
Hi Brian,
IIRC, we discussed something similar with Tomas a few weeks ago and one of the suggested
ideas was be to report the « micro » upgrade (as it is done now) as well as the « latest »
upgrade (regardless of the major/minor/micro bump).
That would give us info on "safe" upgrades with the micro and how far we are
from the head of the component.
In Jandex case, the « latest » would be 3.1.2.
What do you think?
Best regards,
Jeff
On 28 Jun 2023, at 18:05, Brian Stansberry
<brian.stansberry(a)redhat.com> 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 Report
Following repositories were searched:
• Central https://repo1.maven.org/maven2/
• JBossPublic https://repository.jboss.org/nexus/content/repositories/public/
Possible Component UpgradesGAV New Version Repository
Sinceorg.bouncycastle:bcjmail-jdk18on:1.73 1.75 Central new
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 Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
_______________________________________________
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
--
Jeff Mesnil
Engineer @ Red Hat JBoss EAP
http://jmesnil.net/
11:33 a.m.
New subject: Jandex update proposals [Was:] Possible component upgrades report - Wildfly_Core
If that's doable, sure, that's ideal, although I somewhat prefer it to be
<<configurable>> and <<latest>>, not <<hard coded to
micro>> and latest.
"Configurable" meaning as described in
https://github.com/jboss-set/maven-dependency-updater#configuration. I
think being able to get proposals for minors for some projects is good,
even if we are not on the latest major.
If we can only have one item per GA though, for Jandex I think it should be
MINOR not MICRO. Same applies if having more than 1 will take a significant
time to implement.
On Wed, Jun 28, 2023 at 11:21 AM Jeff Mesnil <jmesnil(a)redhat.com> wrote:
Hi Brian,
IIRC, we discussed something similar with Tomas a few weeks ago and one of
the suggested ideas was be to report the « micro » upgrade (as it is done
now) as well as the « latest » upgrade (regardless of the major/minor/micro
bump).
That would give us info on "safe" upgrades with the micro and how far we
are from the head of the component.
In Jandex case, the « latest » would be 3.1.2.
What do you think?
Best regards,
Jeff
> On 28 Jun 2023, at 18:05, Brian Stansberry <brian.stansberry(a)redhat.com>
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 Report
> Following repositories were searched:
> • Central https://repo1.maven.org/maven2/
> • JBossPublic
https://repository.jboss.org/nexus/content/repositories/public/
> Possible Component UpgradesGAV New Version Repository
Sinceorg.bouncycastle:bcjmail-jdk18on:1.73 1.75 Central new
> 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 Stansberry
> Principal Architect, Red Hat JBoss EAP
> He/Him/His
> _______________________________________________
> 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
--
Jeff Mesnil
Engineer @ Red Hat JBoss EAP
http://jmesnil.net/
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
2:54 a.m.
New subject: Jandex update proposals [Was:] Possible component upgrades report - Wildfly_Core
Hi Brian and Jeff,
I'm going to start working on this.
The small problem with the configurable approach is that considering
the number of components we watch it's hard to come up with good
configuration. Currently default is to follow micro, and if somebody
tells me that specific component should be following minor I can set
it, but I have to have that feedback... The follow micro by default
could be changed too however.
If you wanted to have write access to configuration yourselves I can
add you to the gitlab repo, but feel free to just ping me to do any
changes.
I think we can report <<configuratble>> and <<latest>>, or even
<<micro>> and <<minor>> and <<latest>>, but the
reports are gonna get
that much longer, making it harder to notice relevant / important
upgrades.
I will see how it looks and if I can make it readable.
In any case I'm grateful for any feedback to make this more useful -
thanks!
On Wed, 2023-06-28 at 11:33 -0500, Brian Stansberry wrote:
If that's doable, sure, that's ideal, although I somewhat
prefer it
to be <<configurable>> and <<latest>>, not <<hard coded to
micro>>
and latest. "Configurable" meaning as described
in https://github.com/jboss-set/maven-dependency-updater#configuration
. I think being able to get proposals for minors for some projects is
good, even if we are not on the latest major.
If we can only have one item per GA though, for Jandex I think it
should be MINOR not MICRO. Same applies if having more than 1 will
take a significant time to implement.
On Wed, Jun 28, 2023 at 11:21 AM Jeff Mesnil <jmesnil(a)redhat.com>
wrote:
> Hi Brian,
>
> IIRC, we discussed something similar with Tomas a few weeks ago and
> one of the suggested ideas was be to report the « micro » upgrade
> (as it is done now) as well as the « latest » upgrade (regardless
> of the major/minor/micro bump).
>
> That would give us info on "safe" upgrades with the micro and how
> far we are from the head of the component.
>
> In Jandex case, the « latest » would be 3.1.2.
>
> What do you think?
>
> Best regards,
> Jeff
>
>
> > On 28 Jun 2023, at 18:05, Brian Stansberry
> <brian.stansberry(a)redhat.com> 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 Report
> > Following repositories were searched:
> > • Central https://repo1.maven.org/maven2/
> > • JBossPublic
> https://repository.jboss.org/nexus/content/repositories/public/
> > Possible Component UpgradesGAV New Version Repository
> Sinceorg.bouncycastle:bcjmail-jdk18on:1.73 1.75 Central new
> > 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 Stansberry
> > Principal Architect, Red Hat JBoss EAP
> > He/Him/His
> > _______________________________________________
> > 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
>
>
> --
> Jeff Mesnil
> Engineer @ Red Hat JBoss EAP
> http://jmesnil.net/
>
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
3:10 a.m.
New subject: Jandex update proposals [Was:] Possible component upgrades report - Wildfly_Core
Hello!
The configuration for wildfly is currently
here: https://gitlab.cee.redhat.com/jboss-set/dependency-alignment-config...
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
11:05 a.m.
New subject: Jandex update proposals [Was:] Possible component upgrades report - Wildfly_Core
Excellent, thank you Tomas! Knowing where to maintain this is good. I don't
think there's been much call for config changes, but if there are it's
better if we're not always asking you to do them, beyond code review and
merging if you want to keep merging in your own hands.
On Thu, Jun 29, 2023 at 3:10 AM Tomas Hofman <thofman(a)redhat.com> wrote:
Hello!
The configuration for wildfly is currently here:
https://gitlab.cee.redhat.com/jboss-set/dependency-alignment-configs/-/bl...
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 Report
Following repositories were searched:
- Central https://repo1.maven.org/maven2/
- JBossPublic
https://repository.jboss.org/nexus/content/repositories/public/
Possible Component Upgrades
GAVNew VersionRepositorySince
org.bouncycastle:bcjmail-jdk18on:1.73 1.75 Central new
1 items
Generated on 2023-06-23
Report generated by Maven Dependency Updater
<https://github.com/jboss-set/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 Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
8:18 a.m.
New subject: Jandex update proposals [Was:] Possible component upgrades report - Wildfly_Core
Hello Brian and Jeff,
posting a preview of updated report. (The jandex dep was intentionally
downgraded for testing.)
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
io.smallrye:jandex:3.0.43.0.5Centralnew
↳ Minor upgrade3.1.2Central2023-06-30
commons-cli:commons-cli:1.4
↳ Minor upgrade1.5.0Central2023-06-30
org.aesh:aesh:2.4
↳ Minor upgrade2.7Central2023-06-30
org.aesh:readline:2.2
↳ Minor upgrade2.4Central2023-06-30
org.apache.logging.log4j:log4j-api:2.19.0
↳ Minor upgrade2.20.0Central2023-06-30
org.apache.maven.resolver:maven-resolver-api:1.1.1
↳ Minor upgrade1.9.13Central2023-06-30
org.apache.maven:maven-resolver-provider:3.5.4
↳ Minor upgrade3.9.3Central2023-06-30
org.fusesource.jansi:jansi:1.18
↳ Very latest2.4.0Central2023-06-30
org.glassfish:jakarta.json:1.1.6
↳ Very latest2.0.1Central2023-06-30
org.jboss.logging:jboss-logging:3.4.3.Final
↳ Minor upgrade3.5.2.FinalCentral2023-06-30
org.jboss.threads:jboss-threads:2.4.0.Final
↳ Very latest3.5.0.FinalCentral2023-06-30
org.wildfly.galleon-plugins:wildfly-config-gen:6.3.3.Final
↳ Minor upgrade6.4.2.FinalCentral2023-06-30
12 items
Generated on 2023-06-30
Report generated by Maven Dependency Updater
8:28 a.m.
New subject: Jandex update proposals [Was:] Possible component upgrades report - Wildfly_Core
Nice! I like your idea of using shading to distinguish the categories. Once
I recognized you did that, my brain could immediately focus and put the
others in the background.
The length seems pretty reasonable, although the full WF report
likely would be much longer. That could be a good thing though, as there
may be quite a lot of components where we've fallen further behind than we
need to.
On Fri, Jun 30, 2023 at 8:18 AM Tomas Hofman <thofman(a)redhat.com> wrote:
Hello Brian and Jeff,
posting a preview of updated report. (The jandex dep was intentionally
downgraded for testing.)
Component Upgrade Report
Following repositories were searched:
- Central https://repo1.maven.org/maven2/
- JBossPublic
https://repository.jboss.org/nexus/content/repositories/public/
Possible Component Upgrades
GAVNew VersionRepositorySince
io.smallrye:jandex:3.0.4 3.0.5 Central new
↳ Minor upgrade 3.1.2 Central 2023-06-30
commons-cli:commons-cli:1.4
↳ Minor upgrade 1.5.0 Central 2023-06-30
org.aesh:aesh:2.4
↳ Minor upgrade 2.7 Central 2023-06-30
org.aesh:readline:2.2
↳ Minor upgrade 2.4 Central 2023-06-30
org.apache.logging.log4j:log4j-api:2.19.0
↳ Minor upgrade 2.20.0 Central 2023-06-30
org.apache.maven.resolver:maven-resolver-api:1.1.1
↳ Minor upgrade 1.9.13 Central 2023-06-30
org.apache.maven:maven-resolver-provider:3.5.4
↳ Minor upgrade 3.9.3 Central 2023-06-30
org.fusesource.jansi:jansi:1.18
↳ Very latest 2.4.0 Central 2023-06-30
org.glassfish:jakarta.json:1.1.6
↳ Very latest 2.0.1 Central 2023-06-30
org.jboss.logging:jboss-logging:3.4.3.Final
↳ Minor upgrade 3.5.2.Final Central 2023-06-30
org.jboss.threads:jboss-threads:2.4.0.Final
↳ Very latest 3.5.0.Final Central 2023-06-30
org.wildfly.galleon-plugins:wildfly-config-gen:6.3.3.Final
↳ Minor upgrade 6.4.2.Final Central 2023-06-30
12 items
Generated on 2023-06-30
Report generated by Maven Dependency Updater
<https://github.com/jboss-set/maven-dependency-updater>
<https://github.com/jboss-set/maven-dependency-updater>
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
522
days inactive
529
days old
8 comments
4 participants
participants (4)
-
Brian Stansberry -
Jeff Mesnil -
thofman＠redhat.com -
Tomas Hofman