Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Any changes to runwar need backported into this branch
Runwar
Uses master / develop branches
Uses Jakarta servlet spec (jakarta.servlet.)
Uses undertow 3.x
Uses new versions of
Tuckey
RegexPathInfoFilter
All new dev goes here
CommandBox will need to decide which runwar version to use based on the CF Engine and swap out the runwar JAR path on the fly.
For BoxLang, we’ll start by having the commandbox-boxlang module do this so it works on any CommandBox version. Then we’ll modify the next version of CommandBox to detect a flag in box.json for CFEngines to denote when to use the jakarta spec. BoxLang and Adobe CF 2025 will use this flag.
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
We will have 2 builds of Runwar from here on out:
Runwar Legacy
uses the
master-legacybranchuses Java EE servlet spec (
javax.servlet.)uses Undertow 2.x
Any changes to runwar need backported into this branch
Runwar
Uses
master/developbranchesUses Jakarta servlet spec (
jakarta.servlet.)Uses undertow 3.x
Uses new versions of
Tuckey
RegexPathInfoFilter
All new dev goes here
CommandBox will need to decide which runwar version to use based on the CF Engine and swap out the runwar JAR path on the fly.
For BoxLang, we’ll start by having the
commandbox-boxlangmodule do this so it works on any CommandBox version. Then we’ll modify the next version of CommandBox to detect a flag in box.json for CFEngines to denote when to use the jakarta spec. BoxLang and Adobe CF 2025 will use this flag.