August 2023 - wildfly-dev - Jboss List Archives

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

8 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - elytron-web:master

by thofman＠redhat.com

8 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

8 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

8 months, 3 weeks

1
0
0 / 0

WildFly 29.0.1 freeze dates

by Paul Ferraro

Hello all, We are planning to tag a 29.0.1 release of WildFly on Thursday, 24 August 2023. To ensure a smooth release, the 29.x branch will freeze on Tuesday, 22 August 2023, necessitating a wildfly-core 21.x branch freeze on Sunday, 20 August 2023. Please open any pull requests against the 29.x branch and ensure that associated WFLY JIRA issues use 29.0.1.Final as the Fix Version. For WildFly Core fixes, please open pull requests against the 21.x branch and ensure that associated WFCORE JIRA issues use 21.1.1.Final as the Fix Version. For both projects, pull requests should also link to any new or already merged pull requests against the respective main branches. Note that micro-releases are limited to critical fixes, component upgrades containing critical fixes, and low-risk fixes requested by the community. Feel free to let me know if you have any questions or concerns. Thanks, Paul Ferraro

8 months, 3 weeks

1
0
0 / 0

JRE Support

by Brian Stansberry

Ever since we integrated the Eclipse Compiler for Java for compiling JSPs many years ago, an important goal for WildFly has been that we run on a JRE. If we break that we can count on our users noticing and reporting a bug, e.g. [1]. But AFAIK, there's no longer any clear meaning of what a JRE is, unlike in the SE 8 and earlier days. I don't believe there's any minimal set of JPMS modules that an SE distribution must provide to be called a "JRE"; it seems like it's up to the various distributions that provide a JRE dist to choose their own set. (If I'm wrong about this I'd love to know as that would be very helpful.) Where this matters is when we get proposed changes to add a module dependency for a module in the 'jdk.*' namespace. For example, see [2]. When we see that we need to do some thinking about whether adding that dependency means WF will no longer run on a JRE. But that thinking begs the question of "what is a JRE". To help with this I've created a spreadsheet showing what modules are available in the SE 11 and SE 17 variants of 3 different "JRE" distributions -- Eclipse Temurin, IBM Semeru and the OpenJDK packages available in the Fedora 38 repo. https://docs.google.com/spreadsheets/d/1DSCWOv2-tK8mhDz3yE_ysBdyaPew1nCrY... It would be good if we can get some data for SE 21 in there as well, before it goes GA. If anyone wants edit access to that document, please ping me offline with the email address you'd use to log into google. Hopefully that data can be helpful when evaluating proposed additions of 'jdk.*' namespace modules. [1] https://issues.redhat.com/browse/WFLY-18296 [2] https://github.com/wildfly/wildfly/pull/17097 Best regards, Brian

8 months, 4 weeks

1
0
0 / 0

CDI Extension issue in wildfly 26.1.3

by Ramamoorthy Krishna Reddy

I'm upgrading project from WF12 to W26.1.3. I was able to build and deploy to my local dev and don't see any issues. When it moved to higher environment I'm getting following error, "(DeploymentScanner-threads - 1) WFLYCTL0013: Operation (\"deploy\") failed - address: ([(\"deployment\" => \"ContentStream.war\")]) - failure description: {\"WFLYCTL0080: Failed services\" => {\"jboss.deployment.unit.\\\"ContentStream.war\\\".WeldStartService\" => \"Failed to start service\n Caused by: org.jboss.weld.exceptions.DeploymentException: Exception List with 2 exceptions:\nException 0 :\norg.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type MetadataResultService with qualifiers @Default\n at injection point [UnbackedAnnotatedField] @Inject private com.test.metadata.rest.MetadataResultResourceV1.metadataResultService\n\nException 1 :\norg.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type PingDetailService with qualifiers @Default\n at injection point [UnbackedAnnotatedField] @Inject com.test.ping.rest.PingDetailResourceV1.pingDetailService\n\n\"}}", "logtype":"wildfly-main-filteredlog", Please find the piece of code here, import javax.inject.Inject; @Path("/v1/ping") @Api(value = "/v1/ping", tags = "Ping Details") public class PingDetailResourceV1 extends CommonResource { /** The ProductDetailService. */ @Inject PingDetailService pingDetailService; Please suggest me if I'm missing something here. Thanks, Ram

8 months, 4 weeks

2
2
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

8 months, 4 weeks

1
0
0 / 0

Possible component upgrades report - elytron-web:master

by thofman＠redhat.com

8 months, 4 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev August 2023