Re: JPMS module names

2020-10-31 Thread Igal Sapir
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

2020-10-29 Thread Mark Thomas
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

Re: JPMS module names

2020-06-16 Thread Mark Thomas
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

2020-06-16 Thread Raymond Auge
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

2020-06-16 Thread Mark Thomas
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 (