[tomcat] 01/05: Align JPMS module names with current jakarta expectations

substitute=websocket-api diff --git a/webapps/docs/changelog.xml b/webapps/docs/changelog.xml index 69a36d7..418679c 100644 --- a/webapps/docs/changelog.xml +++ b/webapps/docs/changelog.xml @@ -177,6 +177,9 @@ Improvements to Russian translations. Provided by Azat. (markt) +

[tomcat] 01/04: Align JPMS module names with current jakarta expectations

module names with current jakarta expectations --- res/bnd/el-api.jar.tmp.bnd| 4 ++-- res/bnd/jaspic-api.jar.tmp.bnd| 4 ++-- res/bnd/websocket-api.jar.tmp.bnd | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/res/bnd/el-api.jar.tmp.bnd b/res/bnd/el

Re: JPMS module names

Mark, On Thu, Oct 29, 2020 at 12:43 PM Mark Thomas wrote: > Hi all, > > Just a reminder that this is on the radar. I'll likely be looking to > make these changes early next week as part of the prep for the next > release round (I need to sort this to be able to fix BZ 64849 sensibly). > > Mark >

Re: JPMS module names

Hi all, Just a reminder that this is on the radar. I'll likely be looking to make these changes early next week as part of the prep for the next release round (I need to sort this to be able to fix BZ 64849 sensibly). Mark On 27/10/2020 20:04, Mark Thomas wrote: > Hi all, > > We are starting t

JPMS module names

Hi all, We are starting to get JPMS related bug reports. Resolving the issues is technically simple but depends on us deciding on the names to use for the various modules. The names we choose for our own modules are easy. Generally we are using the same or derivation from the OSGi module name. T

Re: JPMS module names

On 16/06/2020 15:52, Raymond Auge wrote: > > > On Tue, Jun 16, 2020 at 10:43 AM Mark Thomas > wrote: > > On 16/06/2020 15:00, Raymond Auge wrote: > > Hey folks, > > > > I've extrapolated what I found as basis for a rule to create module > > names and

Re: JPMS module names

On Tue, Jun 16, 2020 at 10:43 AM Mark Thomas wrote: > On 16/06/2020 15:00, Raymond Auge wrote: > > Hey folks, > > > > I've extrapolated what I found as basis for a rule to create module > > names and this is what I've come up with: > > > > module.name : > org.apache.${replace;

Re: JPMS module names

On 16/06/2020 15:00, Raymond Auge wrote: > Hey folks, > > I've extrapolated what I found as basis for a rule to create module > names and this is what I've come up with: > > module.name : org.apache.${replace;${Bundle-Name};-;.} > > that is: > - take the `Bundle-Name` value (

JPMS module names

Hey folks, I've extrapolated what I found as basis for a rule to create module names and this is what I've come up with: module.name: org.apache.${replace;${Bundle-Name};-;.} that is: - take the `Bundle-Name` value (which appears to have a consistent format) - replace dashes with dots - prefix w