Re: The rationale for runtime modularization

2015-12-04 Thread mark . reinhold
2015/12/4 6:55 -0800, rein...@zwitserloot.com: > On Fri, Dec 4, 2015 at 1:19 AM, wrote: >> Strong encapsulation at run time greatly improves both >> * security* and maintainability. (Strong encapsulation at compile time >> makes it much easier to prepare for strong encapsulation at run time.) >

Re: The rationale for runtime modularization

2015-12-04 Thread Reinier Zwitserloot
On Fri, Dec 4, 2015 at 1:19 AM, wrote: > Strong encapsulation at run time greatly improves both > * security* and maintainability. (Strong encapsulation at compile time > makes it much easier to prepare for strong encapsulation at run time.) > Is there a blogpost or documentation I can peruse t

Re: The rationale for runtime modularization

2015-12-04 Thread David M. Lloyd
On 12/03/2015 06:19 PM, mark.reinh...@oracle.com wrote: 2015/12/3 1:36 -0800, Rafael Winterhalter : I am writing this after looking into Jigsaw for about two months and after running my open-source libraries and several enterprise applications of my current employer using the EA builds. Glad t

Re: Re: The rationale for runtime modularization

2015-12-04 Thread Rafael Winterhalter
Dependency exlcusion in Maven implies that the a dependency is excluded from any created artifact, for example a war file that stores all dependencies in its lib folder. This would cause the application to malfunction at runtime because the used library internally depends on the now excluded code.

Aw: Re: The rationale for runtime modularization

2015-12-04 Thread Jochen Theodorou
> Gesendet: Freitag, 04. Dezember 2015 um 10:43 Uhr [...] > Here is however one point I disagree with: Maven does not offer > compile-time moduarization. Maven only assures that all dependencies are in > scope but it does not offer any means to cut down this dependency tree to > the set of classe

Re: The rationale for runtime modularization

2015-12-04 Thread Rafael Winterhalter
Hi Mark, thank you for your answer. I am glad to hear that the feedback is taken into serious consideration. Here is however one point I disagree with: Maven does not offer compile-time moduarization. Maven only assures that all dependencies are in scope but it does not offer any means to cut dow

RE: The rationale for runtime modularization

2015-12-04 Thread Frank Yuan
ning curve? > -Original Message- > From: jigsaw-dev [mailto:jigsaw-dev-boun...@openjdk.java.net] On Behalf Of > mark.reinh...@oracle.com > Sent: Friday, December 04, 2015 8:20 AM > To: Rafael Winterhalter > Cc: jigsaw-dev@openjdk.java.net > Subject: Re: The ratio

Re: The rationale for runtime modularization

2015-12-03 Thread mark . reinhold
2015/12/3 1:36 -0800, Rafael Winterhalter : > I am writing this after looking into Jigsaw for about two months and after > running my open-source libraries and several enterprise applications of my > current employer using the EA builds. Glad to hear it! > In the context of these experiences, I w

The rationale for runtime modularization

2015-12-03 Thread Rafael Winterhalter
Hello everybody, I am writing this after looking into Jigsaw for about two months and after running my open-source libraries and several enterprise applications of my current employer using the EA builds. In the context of these experiences, I wanted to ask for the rationale of project Jigsaw to