[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[wtp-pmc] Agenda for WTP PMC telecon for Tuesday, August 1, 2006
|
Call info:
- Tollfree in the US:
866-214-3176
- Alternate: 404-827-9098
- Access code: 8870689#
Call Time: 7am PDT / 10am PDT
Robert and Arthur sent regrets for this morning’s
meeting. I have a hard stop at 7:55 due to an analyst call.
Agenda:
- Community [Lawrence]
- Process issues [Tim]
- Update on Dali and JSF release
review paperwork discussion
- “Full” 1.5 release
review deck (attached)
- Robert Goodman committership
vote
- Orbit support (see Arthur’s
comments, attached)
- Konstantin’s request for
permission to employ Java 5 in wst.common.facet.* to enable API
declaration using the established design
- Update on UI testing
- Requirements and 2.0 Planning
(Jochen)
- 1.5.1 and 2.0 Status (David)
- JSF [Raghu]
- Dali/JPA [Neil]
|
Attachment:
wtp15-full-release-review.ppt
Description: wtp15-full-release-review.ppt
From: wtp-pmc-bounces@xxxxxxxxxxx on behalf of Arthur Ryman
[ryman@xxxxxxxxxx]
Sent: Tuesday, July 11, 2006 8:19 PM
To:
wtp-pmc@xxxxxxxxxxx
Subject: [wtp-pmc] Fw: [eclipse.org-committers]
Eclipse Project Declarationfor Orbit
Attachments:
ATT2989253.txt
I think we should support
Orbit and use it for WTP 2.0 if possible. Let's get rid of all our third party
content and pull it in from Orbit.
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 ----- Forwarded by Arthur Ryman/Toronto/IBM
on 07/11/2006 10:43 PM -----
Anne Jacko
<emo@xxxxxxxxxxx>
Sent
by: eclipse.org-committers-bounces@xxxxxxxxxxx
07/10/2006 05:52 PM
|
|
To
| eclipse.org-membership-at-large@xxxxxxxxxxx,
eclipse.org-committers@xxxxxxxxxxx
|
|
cc
|
|
|
Subject
| [eclipse.org-committers] Eclipse
Project Declaration for Orbit |
|
Project Declaration for Eclipse Orbit The Eclipse Orbit Project is a proposed open source project under the
Eclipse Tools Project (http://www.eclipse.org/proposals/orbit/). This project will provide a repository of
bundled versions of third party libraries that are approved for use in one or
more Eclipse projects. The repository will maintain old versions of such
libraries to facilitate rebuilding historical output. It will also clearly
indicate the status of the library (i.e., the approved scope of use). The
repository will be structured such that the contained bundles are easily
obtained and added to a developer's workspace or target platform.
You are invited to comment on and/or join the project.
Please send all feedback to news://news.eclipse.org/eclipse.tools.orbit. Anne Jacko Development Process Operations Support emo@xxxxxxxxxxx _______________________________________________
eclipse.org-committers
mailing
list
eclipse.org-committers@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-committers
From: wtp-dev-bounces@xxxxxxxxxxx
on behalf of Konstantin Komissarchik
Sent: Friday, July 28, 2006 10:37
AM
To: General discussion of project-wide or architectural
issues.
Cc: Cross project issues
Subject: RE: [wtp-dev]
Using Java 5 language features in WTP 2.0
Attachments:
ATT8046604.txt
Ok, so Id like to
request PMC approval to use Java 5 features in wst.common.facet.core and
facet.ui plugins. The reason is that the API of both of these plugins has been
designed from the start to utilize parameterized collections (generics) and
enumerations. The API in these plugins has been shipped in a provisional state
for the 1.0 and 1.5 releases. The current plan is to move this API into the
declared status for the 2.0 release. However, that cannot happen until
collections in the API are properly parameterized and the fake enum classes are
replaced with real enums. Note that this is not the only issue currently
blocking the API declaration, but the plan is to resolve the other issues in the
2.0 release.
-
Konstantin
From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Tim
Wagner
Sent:
Thursday, July 27, 2006 8:45 PM
To: General
discussion of project-wide or architectural issues.
Cc: Cross project issues
Subject: [wtp-dev] Using Java 5 language
features in WTP 2.0
On the status call today we agreed
to the following policy:
- Implementations in
the common component will be restricted to 1.4.x VM levels, which implies
Java 1.4 language features (no Java 5 features, such as generics). However,
developers can request permission of the PMC to use Java 5 language features
on a plugin-by-plugin basis.
- All other components
in WTP are free to use Java 5 language features, and WTP as a project will
require a Java 5-level VM in the 2.0 (Europa) release and will need to be
compiled with a Java 5-level compiler.
Maintenance releases on the 1.x
lines (1.5.1, 1.5.2, etc.) are unchanged they are still restricted to Java 1.4
language features and must compile and run on a Java 1.4
JDK/VM.
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
|
