Re: [ecf-dev] Changing DocShare requirements to Java 1.5 and up - any ob

[Chris Aniszczyk <zx@xxxxxxxxxx>]

I would prefer the core code remain as low as EE as possible, this is part of the reason ECF has been successful and adopted in p2 and various other places.

Cosmetics can't be the only reason to move to an updated EE.

For UI bits and pieces, I don't mind about using J2SE-1.5 as the UI code tends to be the code reused less.

I'm excited to see what you're up to Mustafa :)

Cheers,

---
Chris Aniszczyk | IBM Lotus | Eclipse Committer | http://mea-bloga.blogspot.com | +1.860.839.2465

"Mustafa K. Isik" ---05/13/2008 03:29:35 PM---Hi fellow ECFers, As you may know, the ECF plug-ins require Java 1.4 and up as execution

From:	"Mustafa K. Isik" <codesurgeon@xxxxxxxxx>
To:	"Eclipse Communication Framework (ECF) developer mailing list." <ecf-dev@xxxxxxxxxxx>
Date:	05/13/2008 03:29 PM
Subject:	[ecf-dev] Changing DocShare requirements to Java 1.5 and up - any objections?

---

Hi fellow ECFers,

As you may know, the ECF plug-ins require Java 1.4 and up as execution
environment.

Over the last couple of weeks I have been updating Cola and
integrating it with DocShare.

Since Cola is fairly heavy on Collections (and I rely on Generics and
I don't like working with what I perceive as outdated Java language
spec), I have been using the Java 1.5 language extensions in my
development work. Committing Cola code to the ECF CVS requires me to
strip the sources of said extensions though.

Instead of having to go back and forth between Cola's surrogate mother
http://code.google.com/p/cola-rtse/ [hosting the Java 1.5 code] and
the ECF CVS, I'd like to update the DocShare requirements accordingly.

Is this OK with everyone or do you see any problems?

Thanks,

Mustafa

-- 
Mustafa K. Isik

codesurgeon@xxxxxxxxx
http://codesurgeonblog.com
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev