Re: [eclipse.org-architecture-council] On subject of JSR's - JigSaw

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

The JDT Compiler team also has concerns
regarding incomplete specifications. A good entry point is http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-May/012464.html.

Note that they wanted to reply here
earlier but ran into https://bugs.eclipse.org/315210.

Dani



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

---

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.