Hi,
Sorry for causing the confusion. I mean to include a general subject since
I think commons would benefit from the results. However, I pointed out in
the content that the work'd be done over commons-rdf. Again, sorry for
that. :D
Regards,
~Kamila.
On Thu, Mar 8, 2018 at 8:23 PM, Gilles
On Fri, 9 Mar 2018 01:47:01 +0100, Bernd Eckenfels wrote:
Hello,
any experience with compiling a JAR with old Java and only adding the
module-info.jar with a new class Version? Would that allow to avoid
the Need for Multi-Release JARs? (of Course it makes a ugly
toolchain).
IIUC, there must
> On Mar 8, 2018, at 5:47 PM, Bernd Eckenfels wrote:
>
> Hello,
>
> any experience with compiling a JAR with old Java and only adding the
> module-info.jar with a new class Version? Would that allow to avoid the Need
> for Multi-Release JARs? (of Course it makes a
Hello,
any experience with compiling a JAR with old Java and only adding the
module-info.jar with a new class Version? Would that allow to avoid the Need
for Multi-Release JARs? (of Course it makes a ugly toolchain).
Gruss
Bernd
--
http://bernd.eckenfels.net
On Thu, 8 Mar 2018 17:19:05 -0700, Ralph Goers wrote:
On Mar 8, 2018, at 5:17 PM, Ralph Goers
wrote:
On Mar 8, 2018, at 4:08 PM, Gilles
wrote:
On Thu, 8 Mar 2018 15:09:18 -0700, Ralph Goers wrote:
On Mar 8, 2018, at 11:06 AM,
That seems like a good pragmatic way about it.
Gary
On Thu, Mar 8, 2018, 16:08 Gilles wrote:
> On Thu, 8 Mar 2018 15:09:18 -0700, Ralph Goers wrote:
> >> On Mar 8, 2018, at 11:06 AM, Gilles
> >> wrote:
> >>
> >> On Thu, 8 Mar 2018
I almost pooped myself on that one Ralph :-) Good one!
Gary
On Thu, Mar 8, 2018, 17:19 Ralph Goers wrote:
>
>
> > On Mar 8, 2018, at 5:17 PM, Ralph Goers
> wrote:
> >
> >
> >
> >> On Mar 8, 2018, at 4:08 PM, Gilles
On Thu, 8 Mar 2018 17:17:40 -0700, Ralph Goers wrote:
On Mar 8, 2018, at 4:08 PM, Gilles
wrote:
On Thu, 8 Mar 2018 15:09:18 -0700, Ralph Goers wrote:
On Mar 8, 2018, at 11:06 AM, Gilles
wrote:
On Thu, 8 Mar 2018 11:01:08 -0700,
> On Mar 8, 2018, at 5:17 PM, Ralph Goers wrote:
>
>
>
>> On Mar 8, 2018, at 4:08 PM, Gilles wrote:
>>
>> On Thu, 8 Mar 2018 15:09:18 -0700, Ralph Goers wrote:
On Mar 8, 2018, at 11:06 AM, Gilles
> On Mar 8, 2018, at 4:08 PM, Gilles wrote:
>
> On Thu, 8 Mar 2018 15:09:18 -0700, Ralph Goers wrote:
>>> On Mar 8, 2018, at 11:06 AM, Gilles wrote:
>>>
>>> On Thu, 8 Mar 2018 11:01:08 -0700, Gary Gregory wrote:
On Thu, Mar 8,
On Thu, 8 Mar 2018 15:09:18 -0700, Ralph Goers wrote:
On Mar 8, 2018, at 11:06 AM, Gilles
wrote:
On Thu, 8 Mar 2018 11:01:08 -0700, Gary Gregory wrote:
On Thu, Mar 8, 2018 at 10:58 AM, Gilles
wrote:
On Thu, 8 Mar 2018 10:48:28
> On Mar 8, 2018, at 11:06 AM, Gilles wrote:
>
> On Thu, 8 Mar 2018 11:01:08 -0700, Gary Gregory wrote:
>> On Thu, Mar 8, 2018 at 10:58 AM, Gilles
>> wrote:
>>
>>> On Thu, 8 Mar 2018 10:48:28 -0700, Gary Gregory wrote:
>>>
On
On Thu, 8 Mar 2018 11:01:08 -0700, Gary Gregory wrote:
On Thu, Mar 8, 2018 at 10:58 AM, Gilles
wrote:
On Thu, 8 Mar 2018 10:48:28 -0700, Gary Gregory wrote:
On Thu, Mar 8, 2018 at 10:29 AM, Gilles
wrote:
On Thu, 8 Mar 2018
> On Mar 8, 2018, at 12:48 PM, Gary Gregory wrote:
> On Thu, Mar 8, 2018 at 10:29 AM, Gilles
> wrote:
>> Then these modules can define "module-info" files, and an actual build will
>> prove that the dependencies are as expected.
>>
> As
On Thu, Mar 8, 2018 at 10:58 AM, Gilles
wrote:
> On Thu, 8 Mar 2018 10:48:28 -0700, Gary Gregory wrote:
>
>> On Thu, Mar 8, 2018 at 10:29 AM, Gilles
>> wrote:
>>
>> On Thu, 8 Mar 2018 10:09:22 -0700, Gary Gregory wrote:
>>>
>>> On Thu,
On Thu, 8 Mar 2018 10:48:28 -0700, Gary Gregory wrote:
On Thu, Mar 8, 2018 at 10:29 AM, Gilles
wrote:
On Thu, 8 Mar 2018 10:09:22 -0700, Gary Gregory wrote:
On Thu, Mar 8, 2018 at 10:01 AM, ajs6f wrote:
> On Mar 8, 2018, at 8:33 AM, Gilles
On Thu, Mar 8, 2018 at 10:29 AM, Gilles
wrote:
> On Thu, 8 Mar 2018 10:09:22 -0700, Gary Gregory wrote:
>
>> On Thu, Mar 8, 2018 at 10:01 AM, ajs6f wrote:
>>
>> > On Mar 8, 2018, at 8:33 AM, Gilles
>>> wrote:
>>> >
On Thu, Mar 8, 2018 at 10:21 AM, ajs6f wrote:
>
> > On Mar 8, 2018, at 12:09 PM, Gary Gregory
> wrote:
> >
> > That's all quite nice but the hard reality is that the tool chains out
> > there are simply not ready for JPMS, as I've painfully learned
>
On Thu, Mar 8, 2018 at 10:01 AM, ajs6f wrote:
> > On Mar 8, 2018, at 8:33 AM, Gilles wrote:
> > Would it be useful (and interesting as part of GSoC work) to
> > establish
> > (1) which tools requires fixing,
> > (2) prepare enhancement requests
> On Mar 8, 2018, at 8:33 AM, Gilles wrote:
> Would it be useful (and interesting as part of GSoC work) to
> establish
> (1) which tools requires fixing,
> (2) prepare enhancement requests for the respective projects,
> and in the meantime, adapt the "Commons" build
20 matches
Mail list logo