Possible component upgrades report - Wildfly
by thofman＠redhat.com
Generated at 01:51:45 SGT 2020-02-09
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.fasterxml.jackson.core:jackson-annotations:2.10.1 -> 2.10.2 (Central)
com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:2.10.1 -> 2.10.2.1 (Central)
com.google.code.gson:gson:2.8.2 -> 2.8.6 (Central)
com.netflix.hystrix:hystrix-core:1.5.12 -> 1.5.18 (Central)
com.squareup.okhttp3:okhttp:3.9.0 -> 3.9.1 (Central)
com.sun.xml.fastinfoset:FastInfoset:1.2.13 -> 1.2.17 (Central)
io.jaegertracing:jaeger-client:0.34.1 -> 0.34.2 (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:rxjava:1.2.0 -> 1.2.10 (Central)
io.reactivex.rxjava2:rxjava:2.2.5 -> 2.2.17 (Central)
io.smallrye:smallrye-jwt:2.0.12 -> 2.0.13 (Central)
io.smallrye:smallrye-metrics:2.3.2 -> 2.3.3 (Central)
io.smallrye:smallrye-opentracing:1.3.0 -> 1.3.3 (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.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.3 (Central)
org.apache.ws.xmlschema:xmlschema-core:2.2.4 -> 2.2.5 (Central)
org.cryptacular:cryptacular:1.2.0 -> 1.2.4 (Central)
org.eclipse:yasson:1.0.5 -> 1.0.6 (Central)
org.eclipse.microprofile.rest.client:microprofile-rest-client-api:1.3.2 -> 1.3.4 (Central)
org.eclipse.persistence:eclipselink:2.7.3 -> 2.7.6 (Central)
org.hdrhistogram:HdrHistogram:2.1.9 -> 2.1.12 (Central)
org.hibernate:hibernate-search-backend-jms:5.10.7.Final -> 5.10.8.Final (Central)
org.jasypt:jasypt:1.9.2 -> 1.9.3 (Central)
org.jboss:jboss-ejb-client:4.0.28.Final -> 4.0.29.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.jboss.spec.javax.faces:jboss-jsf-api_2.3_spec:3.0.0.SP01 -> 3.0.0.SP1 (Central)
org.opensaml:opensaml-core:3.3.0 -> 3.3.1 (Central)
org.reactivestreams:reactive-streams:1.0.2 -> 1.0.3 (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
41 items
Report generated by Maven Dependency Updater
https://github.com/jboss-set/maven-dependency-updater
4 years, 9 months
WildFly Elytron - Module Structure
by Darran Lofthouse
At some point in the future we are going to need to consider a migration to
Jakarta EE 9 so I just wanted to raise some ideas as to how we may choose
to structure the project.
As it stands today our 1.x releases are being used for WildFly and in each
release we are maintaining compatibility of the public API against the
previous releases. We have also started with our 2.0.x releases where some
compatibility has been broken to clean up inter package dependencies, we
were planning to tag this as .Final for Quarkus.
If we are going to switch to Jakarta EE 9 which means new packages for the
specifications that feels like we should handle that with a major version
bump. My first idea was we move master to 3.x and insert a new 2.0.x
release which maintains compatibility with 1.x other than the Jakarta
changes but considering other requirements on us that would lead us to: -
* Elytron 1.x - Jakarta EE 8
* Elytron 2.x - Jakarta EE 9
* Elytron 3.x - Jakarta EE 8
* Elytron 4.x - Jakarta EE 9
So instead to simplify our versioning I was going to consider we pull the
spec related modules out into their own projects: -
wildfly-elytron-ee and wildfly-elytron-mp
This would mean our Elytron release streams would become: -
* Elytron 1.x - Jakarta EE 8
* Elytron 2.x - No Jakarta modules, compatible with 1.x.
* Elytron 3.x - No Jakarta modules, some breaking changes.
The new modules would then align with Elytron 2.x and handle the move to
Jakarta EE 9 within their own version ranges.
Regards,
Darran Lofthouse.
4 years, 9 months
WildFly Community Space Replacement
by James Perkins
Hello All,
We are in a position where we need to change the community space for
WildFly, currently located at https://developer.jboss.org/en/wildfly/. On
2020-03-1 this community space will become read-only.
We've got 3 areas we need to move.
1. Forums/Q&A
2. Wiki/FAQ
3. Articles
1. Forums/Q&A
My preference here is we would use Stack Overflow, specifically the wildfly
tag <https://stackoverflow.com/questions/tagged/wildfly>. It seems the
forums is really more Q&A than anything.
If we want to keep the forum and Q&A separate we could use Stack Overflow
for the Q&A and Google Groups for the forum. Though I don't really see much
difference between the forum and Q&A.
2. Wiki/FAQ
For this we could use GitHub Wiki here. For details see
https://help.github.com/en/github/building-a-strong-community/about-wikis.
3. Articles
I don't know how often articles get created, but it doesn't look like
often. My suggestion would be that we just use wildfly.org for this. These
seem to be akin to blog posts.
Another option could be better as without knowing the structure of how
wildfly.org is a bit of ask for the community to write an article/blog post.
Any other options or suggestions on any of these points are welcome.
Not required but I would also like to open for discussion moving the
wildfly-dev mailing list to Google Groups. What are others opinions on
this? It seems to get fairly low traffic as of now.
--
James R. Perkins
JBoss by Red Hat
4 years, 9 months
Possible component upgrades report - Wildfly
by thofman＠redhat.com
Generated at 01:49:11 SGT 2020-02-02
Searched in following repositories:
* Central: https://repo1.maven.org/maven2/
* JBossPublic: https://repository.jboss.org/nexus/content/repositories/public/
Possible upgrades:
com.fasterxml.jackson.core:jackson-annotations:2.10.1 -> 2.10.2 (Central)
com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:2.10.1 -> 2.10.2.1 (Central)
com.google.code.gson:gson:2.8.2 -> 2.8.6 (Central)
com.netflix.hystrix:hystrix-core:1.5.12 -> 1.5.18 (Central)
com.squareup.okhttp3:okhttp:3.9.0 -> 3.9.1 (Central)
com.sun.xml.fastinfoset:FastInfoset:1.2.13 -> 1.2.17 (Central)
io.jaegertracing:jaeger-client:0.34.1 -> 0.34.2 (Central)
io.netty:netty-all:4.1.42.Final -> 4.1.45.Final (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:rxjava:1.2.0 -> 1.2.10 (Central)
io.reactivex.rxjava2:rxjava:2.2.5 -> 2.2.17 (Central)
io.smallrye:smallrye-metrics:2.3.2 -> 2.3.3 (Central)
io.smallrye:smallrye-opentracing:1.3.0 -> 1.3.3 (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.avro:avro:1.7.6 -> 1.7.7 (Central)
org.apache.cxf:cxf-core:3.3.4 -> 3.3.5 (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.3 (Central)
org.apache.ws.xmlschema:xmlschema-core:2.2.4 -> 2.2.5 (Central)
org.cryptacular:cryptacular:1.2.0 -> 1.2.3 (Central)
org.eclipse:yasson:1.0.5 -> 1.0.6 (Central)
org.eclipse.microprofile.opentracing:microprofile-opentracing-api:1.3.1 -> 1.3.2 (Central)
org.eclipse.microprofile.rest.client:microprofile-rest-client-api:1.3.2 -> 1.3.4 (Central)
org.eclipse.persistence:eclipselink:2.7.3 -> 2.7.6 (Central)
org.hdrhistogram:HdrHistogram:2.1.9 -> 2.1.12 (Central)
org.hibernate:hibernate-search-backend-jms:5.10.7.Final -> 5.10.8.Final (Central)
org.jasypt:jasypt:1.9.2 -> 1.9.3 (Central)
org.jboss:jboss-ejb-client:4.0.28.Final -> 4.0.29.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.jboss.spec.javax.faces:jboss-jsf-api_2.3_spec:3.0.0.SP01 -> 3.0.0.SP1 (Central)
org.opensaml:opensaml-core:3.3.0 -> 3.3.1 (Central)
org.reactivestreams:reactive-streams:1.0.2 -> 1.0.3 (Central)
org.wildfly.galleon-plugins:wildfly-config-gen:4.2.3.Final -> 4.2.4.Final (Central)
xalan:serializer:2.7.1.jbossorg-4 -> 2.7.2 (Central)
44 items
Report generated by Maven Dependency Updater
https://github.com/jboss-set/maven-dependency-updater
4 years, 9 months