Re: [wtp-pmc] Request to use Java 5 Language Features in facet plugins

[Timothy Deboer <deboer@xxxxxxxxxx>]

David,

I hate to point it out, but facets *are*
one of the more likely candidates for moving down to platform or other
environments. Konstantin has been planning and working on this for some
time, and there is already a proposed refactoring in CVS:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=159169
https://bugs.eclipse.org/bugs/show_bug.cgi?id=160245

We can discuss further on the PMC call
today.

Thanks,
Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503  (tieline 969)
deboer@xxxxxxxxxx

Date: Tue, 23 Jan 2007 01:06:17 -0500
From: David M Williams <david_williams@xxxxxxxxxx>
Subject: Re: [wtp-pmc] Request to use Java 5 Language Features in
                
facet plugins
To: "WTP PMC communications \(including coordination, announcements,
                
and Group discussions\)" <wtp-pmc@xxxxxxxxxxx>

Arthur, and others that may have forgotten ... the Eclipse Platform itself
has different requirements for each plugin, none of them 1.5. 
The reason for that is they have real requirements to run in "small
footprint" environments, hence need to really hold back any extra
dependancies. 

Eclipse as a whole, that is Europa, via the Planning and Architecture 
councils, have stated that each project is free to choose their own, but
that they should "spec" the EE in the manifest.mf. 

Long ago, we (WTP PMC) agreed our committers were free to use Java 5 
language features, "if they had a good reason" (e.g. to improve
code 
quality, but not just because they 
personally liked the new for loop syntax :) and, naturally, subject to
all 
the other constraints we place on them (no breaking API changes, and even
extra care not to break non-api if there
were known users of it). 

The one exception to our policy (due to my lobbying) was any plugin in
the 
"commons" component. There, I wanted explicit PMC review, since
in some 
cases there might be chances 
these common plugins could "move down" to a lower level component
in 
Eclipse or there might be some adopter planning to use it in a reduced
footprint environment. 
(One example of a 'move' is our attempts to move down some of our proxy
setting code). 

Hence, Konstantin's request to the PMC, hence my affirmative reply and
request for others on the PMC to approve it for these facets plugins. 

Thanks for asking. 



Arthur Ryman <ryman@xxxxxxxxxx> 
Sent by: wtp-pmc-bounces@xxxxxxxxxxx
01/22/2007 04:08 PM
Please respond to
"WTP PMC communications \(including coordination, announcements, and
Group 
discussions\)" <wtp-pmc@xxxxxxxxxxx>

Subject
Re: [wtp-pmc] Request to use Java 5 Language Features in facet plugins



Java 5 is getting fairly commonplace now so I don't see a problem in using
it to develop WTP, especially if it makes the code easier to maintain.
Of 
course, we need to be consistent with Eclipse policy. What are the Eclipse
Platform guidelines? 

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx