WildFly 36 Schedule
by Brian Stansberry
Hello,
Work is well underway on WildFly 36. These are the dates we're planning for
releasing 36 Beta and Final:
36 Beta
Freeze (PRs ready deadline) - Wed Mar 19
Tag/deploy of main WildFly bits - Wed Mar 26
Other deliverables, announcement - Thu Mar 27
36 Final
Freeze (PRs ready deadline) - Wed Apr 2
Complete merging - Mon Apr 7
Buffer day - Tue Apr 8
Tag/deploy of main WildFly bits - Wed …
[View More]Apr 9
Other deliverables, announcement - Thu Apr 10
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
[View Less]
1 week
Request for feature team: run WildFly from JBang
by Jeff Mesnil
Hi,
I’ve opened a proposal[1] to be able to build and run WildFly application from JBang[2]
The goal of this proposal is to be able to quickly prototype WildFly applications from a single .java file with no need to set up a Maven project, configure any plugins, etc.
TL;DR copy the file myapp.java:
///usr/bin/env jbang "$0" "$@" ; exit $?
//JAVA 17+
//DEPS org.wildfly.bom:wildfly-expansion:${wildfly.version:35.0.1.Final}@pom)
//DEPS org.wildfly.glow:wildfly-glow:1.3.2.Final
//DEPS jakarta.ws.…
[View More]rs:jakarta.ws.rs-api
//DEPS jakarta.enterprise:jakarta.enterprise.cdi-api
import jakarta.enterprise.context.ApplicationScoped;
import jakarta.ws.rs.GET;
import jakarta.ws.rs.Path;
import jakarta.ws.rs.ApplicationPath;
import jakarta.ws.rs.core.Application;
@ApplicationPath("/")
public class myapp extends Application {
@Path("/hello")
@ApplicationScoped
public static class Hello {
@GET
public String sayHello() {
return "Hello, WildFly!";
}
}
}
You would then run `jbang run my app.java` et voila! You have your code running in a WildFly server with all required capabilities as a Web archive.
The implementation is well under way and only impacts the WildFly Glow project.
The PR[3] for WildFly glow has also some documentation with working examples to prototype a simple Web application, a MicroProfile application, and a Chat bot based on an Ollama model.
This is an experimental feature.
I’m looking for volunteers to provide an outside perspective on this feature.
If you are interested by this proposal, please have a look at the proposal, the PR in Glow
Thanks,
Jeff
[1] https://github.com/wildfly/wildfly-proposals/pull/689
[2] https://www.jbang.dev/
[3] https://github.com/wildfly/wildfly-glow/pull/113
--
Jeff Mesnil
Engineer @ Red Hat
http://jmesnil.net/
[View Less]
3 weeks, 1 day
Use of the 'org.wildfly' groupId
by Brian Stansberry
Currently we have a number of different repos publishing artifacts using
the 'org.wildfly' groupId with no further namespacing.
Going forward I don't think we should allow any other new repos to do that.
It leads to administrative hassles, e.g. with setting things up in Nexus.
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
1 month
