aspectj-devhttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/maillist.html
aspectj-deven-usFri, 09 Dec 2016 10:30:15 GMTFri, 09 Dec 2016 10:30:15 GMThttp://blogs.law.harvard.edu/tech/rssMHonArc RSS 2.0 RCFilewebmaster@eclipse.org (Webmaster)webmaster@eclipse.org (Webmaster)aspectj-devhttp://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpghttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/maillist.html
[aspectj-dev] JDK 9 b148 including a refresh of the module system is available on java.nethttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03213.html
Hi Andy, JDK 9 build b148 includes an important Refresh of the module system [1] , summary of&#xC2; changes are listed here . This refresh includes a disruptive change that is important to understand. For those that have been trying out modules with regular JD...

Hi Andy,

JDK 9 build b148
includes an important Refresh of the module system [1] , summary ofÂ
changes are listed here
.

This refresh includes a disruptive change that is important to
understand.

For those that have been trying out modules with regular JDK 9
builds then be aware that `requires public` changes to `requires
transitive`. In addition, the binary representation of the module
declaration (module-info.class) has changed so that you need to
recompile any modules that were compiled with previous JDK 9 builds.

As things stand today in JDK 9 then you use setAccessible to break
into non-public elements of any type in exported packages. However,
it cannot be used to break into any type in non-exported package.
The current specified behavior was a compromise for the initial
integration of the module system. It is of course not very
satisfactory, hence the #AwkwardStrongEncapsulation issue [2] on the
JSR 376 issues list. With the updated proposal in the JSR, this
refresh changes setAccessible further so that it cannot be used to
break into non-public types, or non-public elements of public types,
in exported packages. Code that uses setAccessible to hack into the
private constructor of java.lang.invoke.MethodHandles.Lookup will be
disappointed for example.

This change will expose hacks in many existing libraries and tools.
As a workaround then a new command line option `--add-opens` can be
used to open specific packages for "deep reflection". For example, a
really popular build tool fails with this refresh because it uses
setAccessible + core reflection to hack into a private field of an
unmodifiable collection so that it can mutate it, facepalm! This
code will continue to work as before when run with `--add-opens
java.base/java.util=ALL-UNNAMED` to open the package java.util in
module java.base to "all unnamed modules" (think class path).

Any help reporting issues to popular tools and libraries would be
appreciated.

A debugging aid that is useful to identify issues is to run with
-Dsun.reflect.debugModuleAccessChecks=true to get a stack trace when
setAccessible fails, this is particularly useful when code swallows
exceptions without any logging.

What version of Java9 are you using? It may be possible they have tweaked the module format yet again and the 1.9 betas no longer work against it, in which case I have more to do. Once I finish 1.8.10 I think AspectJ 1.9 will be the focus going forward as Java 1.9 finally gets finished off.

tells me you are on JDK9.Â
AspectJ 1.8 does not support Java9 - it does not understand
the packaging system Java 9 uses for system classes and will
not locate java.lang.Object/etc. You either need to run on
Java8 or use a beta of AspectJ 1.9.

]]>Mon, 14 Nov 2016 20:19:52 GMThttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03212.htmlandrew.clement@xxxxxxx (Andy Clement)[aspectj-dev] JDK 9 & JDK 9 with Project Jigsaw b144 are available on java.nethttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03211.html
Hi Andy, Early Access b144 (#5709) for JDK 9 with Project Jigsaw is available on java.net, summary of changes are listed here. Early Access b144 for JDK 9 is available on java.net, summary of&#xC2; changes are listed here . There have been a number of fixes to...

Hi Andy,

Early Access b144(#5709) for JDK 9 with Project Jigsaw is
available on java.net, summary of changes are listed here.

Early Access b144 for
JDK 9 is available on java.net, summary ofÂ changes are listed here
.

There have been a number of fixes to bugs reported by Open Source
projects since the last availability emailÂ :

tells me you are on JDK9.
AspectJ 1.8 does not support Java9 - it does not understand
the packaging system Java 9 uses for system classes and will
not locate java.lang.Object/etc. You either need to run on
Java8 or use a beta of AspectJ 1.9.

tells me you are on JDK9.Â AspectJ 1.8 does not support Java9 - it does not understand the packaging system Java 9 uses for system classes and will not locate java.lang.Object/etc. You either need to run on Java8 or use a beta of AspectJ 1.9.

]]>Wed, 02 Nov 2016 16:44:23 GMThttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03209.htmlandrew.clement@xxxxxxx (Andy Clement)[aspectj-dev] java.lang.Runnable cannot be resolved when building with aspectj librarieshttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03208.html
Hi Guys, I am struggling against an error looks connect to aspectj. The stack trace is below, Does anyone encounter the similar issue in working experience and I would be appreciated if any info can be available. thanks so much. We use aspectj libraries f...

Hi Guys,

I am struggling against an error looks connect to aspectj. The
stack trace is below,

Does anyone encounter the similar issue in working experience and
I would be appreciated if any info can be available.

]]>Wed, 02 Nov 2016 13:28:14 GMThttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03208.htmlfeng.l.liu@xxxxxxx (feng l.liu)[aspectj-dev] Early Access builds for JDK 8u122 b02 , JDK 9 & JDK 9 with Project Jigsaw b140 are available on java.nethttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03207.html
Hi Andy, Thanks again for your recent email, I have passed it on. Will let you know if there are any other issues. Early Access b02 for JDK 8u122 is available , summary of changes are listed here. Early Access b140 (#5625) for JDK 9 with Project Jigsaw is...

Hi Andy,

Thanks again for your recent email, I have passed it on. Will let
you know if there are any other issues.

Early Access b02
for JDK 8u122 is available , summary of changes are listed here.

Early Access b140(#5625) for JDK 9 with Project Jigsaw is
available on java.net, summary of changes are listed here.

Early Access b140
for JDK 9 is available on java.net, summary ofÂ changes are listed
here
.

A couple of items to point out with regard to b140:

A fix for Cyclic interface initialization causes JVM crash is
included in b140

We are requesting feedback on a change that went intoÂ JDK 9
b140

The java.io.FilePermission class was changed to remove
pathname canonicalization from its creation,
alongÂ with a system property to revert the behavior back to way
it worked in the previous JDK release.
We do this mainly for performance enhancement so that there is no
need to consult the file system every
time a FilePermisson is created. If you use a security manager and
file permissions then you should read
the details as described on the jdk9 mailing list [1]

One proposal to call out is #AwkwardStrongEncapsulation as
this proposes to change setAccessible(true) so that it can't be
used to break into non-public types/members in exported
packages. This is a non-issue when using setAccessible to get
access to non-public types/members of classes on the class path
but will be an issue for code that uses this method to break
into JDK-internals. We would appreciate as much help as possible
testing these builds. If InaccessibleObjectException is thrown
then examine the stack trace (run with
-Dsun.reflect.debugModuleAccessChecks=true to uncover failed
access attempts in code that shallows exceptions). If it looks
like a library is attempting to access a non-public method or
field of a platform class and make sure to submit a bug in
the issue tracker for the library.

Â- Proposal to Reorganize source classes in src.zip by modules [2]

This proposal might have a compatibility impact on IDEs or
other tools that look in src.zip

]]>Fri, 07 Oct 2016 10:36:09 GMThttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03206.htmlrory.odonnell@xxxxxxx (Rory O'Donnell)[aspectj-dev] Early Access build 136 for JDK 9 & JDK 9 with Project Jigsaw are available on java.nethttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03205.html
Hi Andy, Early Access b136 for JDK 9 is available on java.net, summary of&#xC2; changes are listed here . Early Access b136 (# 5506) for JDK 9 with Project Jigsaw&#xC2;is available on java.net, summary of&#xC2; changes are listed here . There have been a number of fixes...

Hi Andy,

Early Access b136 for
JDK 9 is available on java.net, summary ofÂ changes are listed here
.
Early Access b136(#5506) for JDK 9 with Project
JigsawÂis available on java.net, summary ofÂ changes are listed here
.

There have been a number of fixes to bugs reported by Open Source
projects since the last availability emailÂ :

8165116 - b136 - xml redirect function is not allowed even
with enableExtensionFunctions

NOTE:-Â Build 135 included a fix forÂ JDK-8161016 which has
introduced a behavioral change to HttpURLConnection, more info:

The behavior of HttpURLConnection when using a ProxySelector has
been modified with this JDK release. Currently,
HttpURLConnection.connect() call would fallback to a DIRECT
connection attempt if the configured proxy/proxies failed to make a
connection. This release introduces a change whereby no DIRECT
connection will be attempted in such a scenario. Instead, the
HttpURLConnection.connect() method will fail and throw an
IOException which occurred from the last proxy tested. This behavior
now matches with the HTTP connections made by popular web browsers.
But this change will bring compatibility issues for the applications
expecting a DIRECT connection when a proxy server is down or when
wrong proxies are provided.

JDK 9 Outreach Survey

In order to encourage and receive additional feedback from
developers testing their applications with JDK 9,
the OpenJDK Quality Outreach effort has put together a very brief
survey about your experiences with JDK 9 so far.

]]>Tue, 20 Sep 2016 10:21:12 GMThttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03205.htmlrory.odonnell@xxxxxxx (Rory O'Donnell)[aspectj-dev] Early Access builds of JDK 9 b134 are available on java.nethttp://dev.eclipse.org/mhonarc/lists/aspectj-dev/msg03204.html
Hi Andy, Early Access b134 for JDK 9 is available on java.net, summary of&#xC2; changes are listed here . &#xC2;There have been a number of fixes , since the last availability email , to bugs reported by Open Source projects : 8156841&#xC2;&#xC2;&#xC2; sun.security.pkcs11.SunPKCS...

Hi Andy,

Early Access b134 for
JDK 9 is available on java.net, summary ofÂ changes are listed here
.

ÂThere have been a number of fixes , since the last availability
email , to bugs reported by Open Source projects :