Possible component upgrades report - Wildfly
by thofman＠redhat.com
Generated at 01:48:32 SGT 2020-04-19
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.squareup.okhttp3:okhttp:3.9.0 -> 3.9.1 (Central)
com.sun.activation:jakarta.activation:1.2.1 -> 1.2.2 (Central)
com.sun.istack:istack-commons-runtime:3.0.10 -> 3.0.11 (Central)
com.sun.xml.fastinfoset:FastInfoset:1.2.13 -> 1.2.18 (Central)
io.opentracing.contrib:opentracing-interceptors:0.0.4 -> 0.0.5 (Central)
io.opentracing.contrib:opentracing-tracerresolver:0.1.5 -> 0.1.8 (Central)
io.reactivex.rxjava2:rxjava:2.2.5 -> 2.2.19 (Central)
io.smallrye:smallrye-metrics:2.4.0 -> 2.4.1 (Central)
io.undertow.js:undertow-js:1.0.2.Final -> 1.0.3.Final (Central)
joda-time:joda-time:2.9.7 -> 2.9.9 (Central)
net.bytebuddy:byte-buddy:1.9.11 -> 1.9.16 (Central)
org.apache.activemq:activemq-artemis-native:1.0.0 -> 1.0.1 (Central)
org.apache.activemq:artemis-amqp-protocol:2.10.1 -> 2.11.0 (Central)
org.apache.avro:avro:1.7.6 -> 1.7.7 (Central)
org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.3.0 -> 3.3.1 (Central)
org.apache.james:apache-mime4j:0.6 -> 0.6.1 (Central)
org.apache.myfaces.core:myfaces-api:2.3.1 -> 2.3.6 (Central)
org.apache.openjpa:openjpa-kernel:2.4.2 -> 2.4.3 (Central)
org.apache.qpid:proton-j:0.33.2 -> 0.33.4 (Central)
org.apache.santuario:xmlsec:2.1.4 -> 2.1.5 (Central)
org.apache.ws.xmlschema:xmlschema-core:2.2.4 -> 2.2.5 (Central)
org.bouncycastle:bcmail-jdk15on:1.62 -> 1.65 (Central)
org.codehaus.jettison:jettison:1.4.0 -> 1.4.1 (Central)
org.eclipse.microprofile.rest.client:microprofile-rest-client-api:1.4.0 -> 1.4.1 (Central)
org.eclipse.persistence:eclipselink:2.7.3 -> 2.7.6 (Central)
org.hibernate:hibernate-search-backend-jms:5.10.7.Final -> 5.10.9.Final (Central)
org.infinispan:infinispan-cachestore-jdbc:9.4.18.Final -> 9.4.19.Final (Central)
org.jboss.activemq.artemis.integration:artemis-wildfly-integration:1.0.2 -> 1.0.2-wildfly-1 (JBossPublic)
org.jboss.arquillian.container:arquillian-container-test-spi:1.4.0.Final -> 1.4.1.Final (Central)
org.jboss.narayana:jbosstxbridge:5.10.1.Final -> 5.10.4.Final (Central)
org.jboss.security:jbossxacml:2.0.8.Final -> 2.0.9.Final (JBossPublic)
org.wildfly.galleon-plugins:wildfly-config-gen:4.2.4.Final -> 4.2.6.Final (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
33 items
Report generated by Maven Dependency Updater
https://github.com/jboss-set/maven-dependency-updater
4 years, 7 months
WildFly 19.1 release
by Brian Stansberry
It's been a month since WildFly 19 was released and at this point our
recent practice has been to do a micro release to fix important bugs that
have been resolved since the major. We're about ready to do that, but this
time Flavia Rainone has one feature -- support for the Same-Site cookie
attribute[1] -- about ready to go and I'd like to get that in the hands of
WildFly users quickly. So instead of calling this next release 19.0.1,
since it has one new feature we'd call it 19.1.0. Otherwise it's the usual
types of fixes we put into our micros. The JIRA page for the version[2]
shows the expected contents.
I expect we'll do 19.1.0 next week.
[1] https://issues.redhat.com/browse/WFLY-13003
[2] https://issues.redhat.com/projects/WFLY/versions/12345176
Best regards,
Brian
4 years, 7 months
WFCORE-4150 - Support automatically adding and updating credentials in a credential store
by Jean-Frederic Mesnil
With WFCORE-4150[1], we have added a new feature to automatically add and update credentials in a credential store.
This new RFE has been enabled in WildFly Core 12.0.0.Beta1 that was released last week.
However for users to be able to use this feature, we must update the subsystems API and XML Schemas to expose this new feature.
This require to bump the version of existing XSD schemas to reference the new namespace "urn:wildfly:credential-reference:1.1" (instead of the previous "urn:wildfly:credential-reference:1.0”).
Concerned extensions are:
* clustering
* datasources
* resource-adapters
* agroal
* mail
* messaging-activemq
* undertow
We need to update ALL use of credential-reference in our subsystems to provide a consistent user experience to our users.
Farah already did most of the work for it in https://github.com/wildfly/wildfly/pull/12538.
I’d like to get all component leads for the impacted subsystems to review her PR so we can merge it early in the release cycle of WildFly 20.
Could the component leads for these subsystems (I’ve put you in CC if you are concerned) review Farah PR and ack/nack it before the end of this week, please?
Thanks for you help,
Jeff
[1] https://issues.jboss.org/browse/WFCORE-4150
--
Jeff Mesnil
Principal Software Engineer
Red Hat
http://jmesnil.net/
4 years, 7 months
Possible component upgrades report - Wildfly
by thofman＠redhat.com
Generated at 01:58:26 SGT 2020-04-12
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.squareup.okhttp3:okhttp:3.9.0 -> 3.9.1 (Central)
com.sun.activation:jakarta.activation:1.2.1 -> 1.2.2 (Central)
com.sun.istack:istack-commons-runtime:3.0.10 -> 3.0.11 (Central)
com.sun.xml.fastinfoset:FastInfoset:1.2.13 -> 1.2.18 (Central)
io.opentracing.contrib:opentracing-interceptors:0.0.4 -> 0.0.5 (Central)
io.opentracing.contrib:opentracing-tracerresolver:0.1.5 -> 0.1.8 (Central)
io.reactivex.rxjava2:rxjava:2.2.5 -> 2.2.19 (Central)
io.smallrye:smallrye-metrics:2.4.0 -> 2.4.1 (Central)
io.undertow.js:undertow-js:1.0.2.Final -> 1.0.3.Final (Central)
joda-time:joda-time:2.9.7 -> 2.9.9 (Central)
net.bytebuddy:byte-buddy:1.9.11 -> 1.9.16 (Central)
org.apache.activemq:activemq-artemis-native:1.0.0 -> 1.0.1 (Central)
org.apache.activemq:artemis-amqp-protocol:2.10.1 -> 2.11.0 (Central)
org.apache.avro:avro:1.7.6 -> 1.7.7 (Central)
org.apache.cxf.xjc-utils:cxf-xjc-runtime:3.3.0 -> 3.3.1 (Central)
org.apache.james:apache-mime4j:0.6 -> 0.6.1 (Central)
org.apache.myfaces.core:myfaces-api:2.3.1 -> 2.3.6 (Central)
org.apache.openjpa:openjpa-kernel:2.4.2 -> 2.4.3 (Central)
org.apache.qpid:proton-j:0.33.2 -> 0.33.4 (Central)
org.apache.santuario:xmlsec:2.1.4 -> 2.1.5 (Central)
org.apache.ws.xmlschema:xmlschema-core:2.2.4 -> 2.2.5 (Central)
org.bouncycastle:bcmail-jdk15on:1.62 -> 1.65 (Central)
org.codehaus.jettison:jettison:1.4.0 -> 1.4.1 (Central)
org.eclipse:yasson:1.0.5 -> 1.0.7 (Central)
org.eclipse.microprofile.rest.client:microprofile-rest-client-api:1.4.0 -> 1.4.1 (Central)
org.eclipse.persistence:eclipselink:2.7.3 -> 2.7.6 (Central)
org.hibernate:hibernate-search-backend-jms:5.10.7.Final -> 5.10.9.Final (Central)
org.jboss:jboss-ejb-client:4.0.31.Final -> 4.0.32.Final (Central)
org.jboss.activemq.artemis.integration:artemis-wildfly-integration:1.0.2 -> 1.0.2-wildfly-1 (JBossPublic)
org.jboss.arquillian.container:arquillian-container-test-spi:1.4.0.Final -> 1.4.1.Final (Central)
org.jboss.narayana:jbosstxbridge:5.10.1.Final -> 5.10.4.Final (Central)
org.jboss.security:jbossxacml:2.0.8.Final -> 2.0.9.Final (JBossPublic)
org.reactivestreams:reactive-streams:1.0.2 -> 1.0.3 (Central)
org.wildfly.galleon-plugins:wildfly-config-gen:4.2.4.Final -> 4.2.5.Final (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
35 items
Report generated by Maven Dependency Updater
https://github.com/jboss-set/maven-dependency-updater
4 years, 7 months
Key Dates for WildFly 20
by Brian Stansberry
I hope this message finds everyone safe and well!
I wanted to let the community know the dates we're working toward for
producing WildFly 20.
Here are the key dates:
- Fri, May 15 — PRs ready to merge for all features coming in via
WildFly Core
- Tue, May 19 — All features ready for merge
- Wed, May 20 — WildFly 20 Beta. No new features after this date.
- Fri, May 29 — All changes for WildFly Core ready
- Tue, Jun 2 — All changes for WildFly ready
- Thu, Jun 4 — WildFly 20 Final released
These may shift around a bit as we adapt to whatever comes our way with the
coronavirus situation.
WildFly Core should continue to produce betas every couple of weeks.
Best regards,
Brian
4 years, 7 months
