Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 40796 invoked from network); 20 Nov 2009 09:23:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Nov 2009 09:23:22 -0000 Received: (qmail 96488 invoked by uid 500); 20 Nov 2009 09:23:22 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 96399 invoked by uid 500); 20 Nov 2009 09:23:21 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 96391 invoked by uid 99); 20 Nov 2009 09:23:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2009 09:23:21 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates 209.85.218.222 as permitted sender) Received: from [209.85.218.222] (HELO mail-bw0-f222.google.com) (209.85.218.222) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2009 09:23:10 +0000 Received: by bwz22 with SMTP id 22so3376352bwz.25 for ; Fri, 20 Nov 2009 01:22:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:from:mime-version :content-type:subject:date:in-reply-to:to:references:message-id :x-mailer; bh=EfGe41UWMIb/66R2uGvY5JN7Ynz8Z+qYzF3TaBVhKt4=; b=JxXXs/1L7S2N32IXAJWbzRTYarB/anOb1UlRzBHxiChCHPTeiQElvTrRuGSaxluYFe oB7rOi95mqsgV1Z785ZtjqwFKca2OQ9LIkaPYyZP35UktU+jcWDYcq0BLKnd/FHwW4tQ yw6CeuIwDJM3ihc82IWDo3MCefmjDlh9qcZLE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; b=hYd7CE7972owNhQnVTOOE5xWcdPoC1qsJczYZ3dx4aTtHEoY4r16TyOadIBs3pSkh1 q8K89/6DZtlpjpjq3nLjNMme4CK385ntDFPA8LT0a1TP72Jz1Ydd+DznWqLTvPpE/6EX 5riQgC/E0cE1LNjN8931Mw8TZ7+rEsO18sY+A= Received: by 10.213.1.27 with SMTP id 27mr2558826ebd.7.1258708970334; Fri, 20 Nov 2009 01:22:50 -0800 (PST) Received: from ?192.168.0.52? (lon92-10-78-226-4-211.fbx.proxad.net [78.226.4.211]) by mx.google.com with ESMTPS id 16sm601919ewy.2.2009.11.20.01.22.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 20 Nov 2009 01:22:49 -0800 (PST) Sender: Pierre-Arnaud Marcelot From: Pierre-Arnaud Marcelot Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: multipart/alternative; boundary=Apple-Mail-1--918589607 Subject: Re: Java 6 for Studio 2.0 was: Java 6 before/after ApacheDS 2.0 Date: Fri, 20 Nov 2009 10:22:48 +0100 In-Reply-To: <19a9f6be0911200043v55796e0ag7a3431bbb7b285cb@mail.gmail.com> To: "Apache Directory Developers List" References: <4B05D2D4.7070408@apache.org> <19a9f6be0911200043v55796e0ag7a3431bbb7b285cb@mail.gmail.com> Message-Id: <7E740FA5-C315-4BE9-BA63-2545B4053B10@marcelot.net> X-Mailer: Apple Mail (2.1077) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-1--918589607 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Jeff, I share the same feeling... I'd rather stick with a 1.5 JVM as minimal requirement. Actually, the = same requirements as Eclipse, since Studio ships as an RCP app but also = as plugins embeddable in Eclipse. However, maybe it's possible to provide more features if we can detect = the JVM we're running is 1.6 (I'm not sure there's an API for that = though). In that case, we could activate several features, like a scripting = console. Regards, Pierre-Arnaud On 20 nov. 2009, at 09:43, Jeff MAURY wrote: > I don(t know if this is a requirement for Studio but switching to Java = 6 may lead to problems when using Studio into specific Eclipse = configurations (RAD, ...). which may be based on Java5. >=20 > Regards > Jeff MAURY >=20 > On Fri, Nov 20, 2009 at 1:01 AM, Ersin ER wrote: >=20 >=20 > On Fri, Nov 20, 2009 at 01:20, Stefan Seelmann = wrote: > Hi Ersin, >=20 > Ersin ER wrote: > Hi, >=20 > The question is simple: are we considering Java 6 as the minimum = required JVM version for ApacheDS 2.0? >=20 > I think the same question is valid for Studio. >=20 > especially interested in javax.scripting APIs for the SP subsystem (It = needs a serious review). Also some other related improvements have been=20= >=20 > I think about a scripting console in Studio, in order to create = scripts for mass updates as alternative to the batch operation wizard. >=20 > Slightly off-topic: I also had a DirDsl initiative (in my mind :-) ), = let's keep in touch about that. > =20 > So IMO for Studio 2.0 we should consider to switch to Java 6. >=20 > So I support it as expected. >=20 > But we need to hear any negative (or positive) experiences first. = Features are nice but without problems. > =20 > Kind Regards, > Stefan >=20 >=20 >=20 >=20 > --=20 > Ersin ER > http://www.ersiner.net >=20 >=20 >=20 > --=20 > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.lastfm.fr/listen/user/jeffmaury/personal --Apple-Mail-1--918589607 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Jeff,

I share the same = feeling...

I'd rather stick with a 1.5 JVM as = minimal requirement. Actually, the same requirements as Eclipse, since = Studio ships as an RCP app but also as plugins embeddable in = Eclipse.

However, maybe it's possible to = provide more features if we can detect the JVM we're running is 1.6 (I'm = not sure there's an API for that though).
In that case, we = could activate several features, like a scripting = console.

Regards,
Pierre-Arnaud


On 20 nov. 2009, at 09:43, Jeff MAURY = wrote:

I don(t know if this is a requirement for Studio but = switching to Java 6 may lead to problems when using Studio into specific = Eclipse configurations (RAD, ...). which may be based on = Java5.

Regards
Jeff MAURY

On Fri, Nov 20, 2009 at 1:01 AM, Ersin ER = <ersin.er@gmail.com> = wrote:


On Fri, Nov 20, = 2009 at 01:20, Stefan Seelmann <seelmann@apache.org> = wrote:
Hi Ersin,

Ersin ER wrote:
Hi,

The question is simple: are we considering Java 6 as the minimum = required JVM version for ApacheDS 2.0?

I think the same question is valid for Studio.

especially interested in javax.scripting APIs for the SP subsystem (It = needs a serious review). Also some other related improvements have been =

I think about a scripting console in Studio, in order to create scripts = for mass updates as alternative to the batch operation = wizard.

Slightly off-topic: I also had a = DirDsl initiative (in my mind :-) ), let's keep in touch about that.
 
So IMO for Studio 2.0 we should consider to switch to Java = 6.

So I support it as = expected.

But we need to hear any negative (or positive) = experiences first. Features are nice but without problems.
 
Kind Regards,
Stefan




--
Ersin = ER
http://www.ersiner.net



--
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com<= /a>
http://www.la= stfm.fr/listen/user/jeffmaury/personal

= --Apple-Mail-1--918589607--