hg: jdk7/tl/langtools: 7043922: Regression: internal compiler error for nested anonymous inner class featuring varargs constructor

2011-05-16 Thread maurizio . cimadamore
Changeset: 5faa9eedc44e
Author:mcimadamore
Date:  2011-05-16 09:38 +0100
URL:   http://hg.openjdk.java.net/jdk7/tl/langtools/rev/5faa9eedc44e

7043922: Regression: internal compiler error for nested anonymous inner class 
featuring varargs constructor
Summary: Attributing a constructor call does not clean up the compiler's 
attribution context
Reviewed-by: jjg

! src/share/classes/com/sun/tools/javac/comp/Attr.java
+ test/tools/javac/varargs/7043922/T7043922.java



Re: Why does the new File(URI) constructor restricts the uri to hierarchical?

2011-05-16 Thread Michael McMahon

Paulo,

URI's with a scheme (such as file:) cannot be relative. That's a feature of
the specification of URIs themselves. So, this behavior is a side-effect 
of the

requirement that the URI provided to the constructor has a file: scheme.

- Michael.

On 14/05/11 18:24, Paulo Levi wrote:
I have a mapping from uri to real files, and to i was hoping to use 
that constructor to do the work, however it says it only accepts,


"absolute, hierarchical URI with a scheme equal to "file""

Now, many times on html files the uri would be the second notion of 
hierarchical from the javadoc


"A /hierarchical/ URI is either an absolute URI whose scheme-specific 
part begins with a slash character, *or a relative URI, that is, a URI 
that does not specify a scheme.*"


As in a relative file for instance. But the constructor will never 
accept this since they obviously have no schema. I was hoping to fake 
it by introducing the file schema on uris that don't have it and 
joining the current file parent directory to make a relative uri absolute.


But why doesn't the constructor allow this?





Re: Why does the new File(URI) constructor restricts the uri to hierarchical?

2011-05-16 Thread Alan Bateman

Michael McMahon wrote:

Paulo,

URI's with a scheme (such as file:) cannot be relative. That's a 
feature of
the specification of URIs themselves. So, this behavior is a 
side-effect of the

requirement that the URI provided to the constructor has a file: scheme.
Right, and I suspect the relative URIs that he has may actually be 
relative to a http URI rather than a file URI. If they are relative to a 
file URI then the question is what is the base. If the working directory 
then he can use new File("").toURI() as the base but it could be 
somewhere else.


-Alan


hg: jdk7/tl/jdk: 7042679: Phaser javadoc example does not compile

2011-05-16 Thread chris . hegarty
Changeset: cecfcb4dbcaa
Author:chegar
Date:  2011-05-16 13:10 +0100
URL:   http://hg.openjdk.java.net/jdk7/tl/jdk/rev/cecfcb4dbcaa

7042679: Phaser javadoc example does not compile
Reviewed-by: dl

! src/share/classes/java/util/concurrent/Phaser.java



hg: jdk7/tl/jdk: 7036199: Adding a notification to the implementation of GarbageCollectorMXBeans

2011-05-16 Thread frederic . parain
Changeset: e0c3fd538f1f
Author:fparain
Date:  2011-05-16 17:28 +0200
URL:   http://hg.openjdk.java.net/jdk7/tl/jdk/rev/e0c3fd538f1f

7036199: Adding a notification to the implementation of GarbageCollectorMXBeans
Summary: Add a JMX notification to GarbageCollectorMXBeans
Reviewed-by: acorn, mchung

! make/java/management/mapfile-vers
+ src/share/classes/com/sun/management/GarbageCollectionNotificationInfo.java
+ src/share/classes/sun/management/GarbageCollectionNotifInfoCompositeData.java
! src/share/classes/sun/management/GarbageCollectorImpl.java
! src/share/classes/sun/management/GcInfoCompositeData.java
! src/share/classes/sun/management/MemoryManagerImpl.java
! src/share/classes/sun/management/VMManagement.java
! src/share/classes/sun/management/VMManagementImpl.java
! src/share/javavm/export/jmm.h
! src/share/native/sun/management/GarbageCollectorImpl.c
! src/share/native/sun/management/VMManagementImpl.c
+ 
test/com/sun/management/GarbageCollectorMXBean/GarbageCollectionNotificationContentTest.java
+ 
test/com/sun/management/GarbageCollectorMXBean/GarbageCollectionNotificationTest.java



Re: Why does the new File(URI) constructor restricts the uri to hierarchical?

2011-05-16 Thread Paulo Levi
Yes, they are relative to the current directory of the file normally (the
current dir won't work since the file might not be there).

I was just surprised at the inflexibility since the file: scheme is not used
on the net. I understand that trying to convert from relative (without
scheme) to file is something that is not possible remotely, but those files
are on my filesystem.

As it is i had to do something like:

URI uri = URI.create(link);
String scheme = uri.getScheme();
if (scheme != null && scheme.startsWith("http")) {
//make a ad hoc conversion that downloads the file to the current dir and
treats it as a file that was there.
} else if (uri.getScheme() != null && uri.getScheme().equals("file")) {
//convert uri to file
} else if (uri.getScheme() == null) {
//convert relative URI to file with the current file parent dir as parent
}


On Mon, May 16, 2011 at 11:45 AM, Alan Bateman wrote:

>  Michael McMahon wrote:
>
> Paulo,
>
> URI's with a scheme (such as file:) cannot be relative. That's a feature of
> the specification of URIs themselves. So, this behavior is a side-effect of
> the
> requirement that the URI provided to the constructor has a file: scheme.
>
> Right, and I suspect the relative URIs that he has may actually be relative
> to a http URI rather than a file URI. If they are relative to a file URI
> then the question is what is the base. If the working directory then he can
> use new File("").toURI() as the base but it could be somewhere else.
>
> -Alan
>


hg: jdk7/tl/jdk: 3 new changesets

2011-05-16 Thread daniel . daugherty
Changeset: 2ecb989b6fcc
Author:dcubed
Date:  2011-05-16 12:56 -0700
URL:   http://hg.openjdk.java.net/jdk7/tl/jdk/rev/2ecb989b6fcc

6977677: 3/2 Deadlock on logging subsystem initialization
Summary: Over synchronized Logger.getLogger() deadlocks with 
LogManager.via PlatformLogger
Reviewed-by: dsamersoff, never, acorn, mchung

! src/share/classes/java/util/logging/Logger.java
+ test/java/util/logging/LoggingDeadlock4.java

Changeset: b2db38eb3b13
Author:dcubed
Date:  2011-05-16 12:57 -0700
URL:   http://hg.openjdk.java.net/jdk7/tl/jdk/rev/b2db38eb3b13

7016208: 4/3 null sometimes returned by 
java.util.logging.Logger.getLogger(String name) in -server -Xcomp
Summary: Logger can be GC'ed between LogManager.addLogger() and 
LogManager.getLogger()
Reviewed-by: dsamersoff, never, acorn, mchung

! src/share/classes/java/util/logging/LogManager.java

Changeset: 9861df231e9e
Author:dcubed
Date:  2011-05-16 12:58 -0700
URL:   http://hg.openjdk.java.net/jdk7/tl/jdk/rev/9861df231e9e

7041595: 4/4 add lost test for 6487638
Summary: Add missing LoggingDeadlock3.java and LoggingDeadlock3.props
Reviewed-by: dsamersoff, never, acorn, mchung

+ test/java/util/logging/LoggingDeadlock3.java
+ test/java/util/logging/LoggingDeadlock3.props