From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6307 invoked by alias); 8 Mar 2006 17:35:52 -0000 Received: (qmail 6297 invoked by uid 22791); 8 Mar 2006 17:35:52 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 08 Mar 2006 17:35:50 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id k28HZmUP014975 for ; Wed, 8 Mar 2006 12:35:48 -0500 Received: from opsy.redhat.com (vpn50-101.rdu.redhat.com [172.16.50.101]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k28HZl109307; Wed, 8 Mar 2006 12:35:47 -0500 Received: by opsy.redhat.com (Postfix, from userid 500) id 4622B2DC18D; Wed, 8 Mar 2006 10:30:24 -0700 (MST) To: Michael Koch Cc: classpath@gnu.org, mauve-discuss@sources.redhat.com Subject: Re: Java 5 features References: <20060307193846.GL18158@asterix.konqueror.de> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Wed, 08 Mar 2006 17:35:00 -0000 In-Reply-To: <20060307193846.GL18158@asterix.konqueror.de> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact mauve-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00055.txt.bz2 >>>>> "Michael" == Michael Koch writes: Michael> What is the state of support for the Java 5 language features Michael> in Mauve? Is it okay to use Generics and Enums and such Michael> stuff in testcases that are tagged "1.5"? I would like to Michael> commit some testcases that use Generics and Enums to test Michael> some stuff in GNU classpath generics branch. Michael> What's your opinion? The problem with doing this is that it means that parts of Mauve won't compile against classpath head. This in turn means that an eclipse checkout will always show errors. I suppose if we put these tests into a segregated part of the directory tree we could easily turn them off in the eclipse build. Perhaps we could just disable eclipse compilation of individual files, I haven't looked... Another idea would be to make a generics branch for mauve and then merge it when we do the merge for classpath. Tom