Other IDs: Java 9 modules and OSGi bundle names.
On Mon, Jun 11, 2018 at 4:28 PM sebb wrote:
> On 11 June 2018 at 21:13, Rob Tompkins wrote:
> >
> >
> >> On Jun 11, 2018, at 3:55 PM, Gary Gregory
> wrote:
> >>
> >> The best IMO is “commons.packageId” for "lang3”.
> >
> > Sounds good….will head
On 11 June 2018 at 21:13, Rob Tompkins wrote:
>
>
>> On Jun 11, 2018, at 3:55 PM, Gary Gregory wrote:
>>
>> The best IMO is “commons.packageId” for "lang3”.
>
> Sounds good….will head that direction.
I think the most important aspect is to very carefully document what
the variable is used for.
> On Jun 11, 2018, at 3:55 PM, Gary Gregory wrote:
>
> The best IMO is “commons.packageId” for "lang3”.
Sounds good….will head that direction.
>
> Gary
>
> On Mon, Jun 11, 2018 at 1:41 PM Rob Tompkins wrote:
>
>>
>>
>>> On Jun 11, 2018, at 11:58 AM, Gary Gregory
>> wrote:
>>>
>>> I t
The best IMO is “commons.packageId” for "lang3".
Gary
On Mon, Jun 11, 2018 at 1:41 PM Rob Tompkins wrote:
>
>
> > On Jun 11, 2018, at 11:58 AM, Gary Gregory
> wrote:
> >
> > I think the first statement needs to be checked and code maybe changed to
> > adjust for the fact that we have both the
> On Jun 11, 2018, at 11:58 AM, Gary Gregory wrote:
>
> I think the first statement needs to be checked and code maybe changed to
> adjust for the fact that we have both the artifact id and component id to
> play with.
The issue is that we only have two names for 3 values. Values, for lang:
I think the first statement needs to be checked and code maybe changed to
adjust for the fact that we have both the artifact id and component id to
play with.
The page generation works now BTW with the SNAPSHOT build, which I used for
Commons Text 1.4 RC1.
Gary
On Mon, Jun 11, 2018 at 9:39 AM Ro
