[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] On subject of JSR's - JigSaw

thanks Dani - cc'ed Scott and Jason for info.
/max

> I know Jason was really interested to hear if anyone looked into the impact how use of jigsaw
> modules from within a osgi bundle will work/behave as that would become a future issue/concern.

This might be of interest if not already seen: https://www.eclipseconverge.org/na2017/session/osgi-java-modules-jpms-all-way-down

Dani



From:        "Max Rydahl Andersen" <manderse@xxxxxxxxxx>
To:        "eclipse.org-architecture-council" <eclipse.org-architecture-council@xxxxxxxxxxx>
Cc:        Scott Stark <sstark@xxxxxxxxxx>, Jason Greene <jgreene@xxxxxxxxxx>
Date:        15.04.2017 23:28
Subject:        Re: [eclipse.org-architecture-council] On subject of JSR's - JigSaw
Sent by:        eclipse.org-architecture-council-bounces@xxxxxxxxxxx




On 15 Apr 2017, at 14:23, MikaÃl Barbero wrote:

> Hi Max,
>
> Thanks for the link. Very well written. It depicts very well how
> concerning is the jsr-376. One question: what can we do today about
> this final draft?

If you have additional real life examples where jigsaw makes life harder
than it should be those would be welcome. i.e. I know Jason was really
interested to hear if anyone looked into the impact how use of jigsaw
modules from within a osgi bundle will work/behave as that would become
a future issue/concern.

Also, Eclipse as a JCP member could also take a stance on the JSR wether
to vote yay, nay or abstain.

/max

> Cheers,
> Mikael
>
>> Le 15 avr. 2017 Ã 12:07, Max Rydahl Andersen <manderse@xxxxxxxxxx> a
>> Ãcrit :
>>
>> Hi,
>>
>> The Java and JavaEE team at Red Hat are looking for comments/feedback
>> on jigsaw.
>>
>> We are especially interested in hearing about how jigsaw is going to
>> effect osgi runtimes
>> and the tooling platform.
>>
>> The team wrote up their concerns for jigsaw JSR at
>>
https://developer.jboss.org/blogs/scott.stark/2017/04/14/critical-deficiencies-in-jigsawjsr-376-java-platform-module-system-ec-member-concerns
>>
>> Comments/input welcome - i've cc'ed Jason and Scott from Red Hat that
>> worked on this.
>>
>> /max
>>
http://about.me/maxandersen
>> _______________________________________________
>> eclipse.org-architecture-council mailing list
>> eclipse.org-architecture-council@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
>>
>> IMPORTANT: Membership in this list is generated by processes internal
>> to the Eclipse Foundation.  To be permanently removed from this list,
>> you must contact emo@xxxxxxxxxxx to request removal.
>
> _______________________________________________
> eclipse.org-architecture-council mailing list
> eclipse.org-architecture-council@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
>
> IMPORTANT: Membership in this list is generated by processes internal
> to the Eclipse Foundation.  To be permanently removed from this list,
> you must contact emo@xxxxxxxxxxx to request removal.


/max
http://about.me/maxandersen
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.



_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.


/max
http://about.me/maxandersen