Re: [epf-dev] Tooling: What's the plan for the move to 3.2?

[Charles Yan <cyan@xxxxxxxxxx>]

Brian,

EPF 1.0 will support 3.2. But, for milestone
2, we will stay on 3.1.1 in order to get a quality M2 build.
We will target 3.2 support in M3.

Charlie Yan
IBM Method and IC Engineering
18880 Homestead Rd., Cupertino, CA
Office: 408-342-4681 Mobile: 408-690-4999

Brian Schlosser/Austin/IBM@IBMUS
Sent by: epf-dev-bounces@xxxxxxxxxxx

03/27/2006 12:47 PM

Please respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>

To	"Eclipse Process Framework Project Developers List" <epf-dev@xxxxxxxxxxx>
cc
Subject	[epf-dev] Tooling: What's the plan for the move to 3.2?

What's the plan for supporting the tooling on 3.1.x and 3.2? I was playing
around a bit with 3.2 and there are a couple of changes needed. Some in
the authoring.ui plugin and one in library.persistance. I've got a patch
for the authoring.ui, but I'm not sure what should be done in library.persistance

Also I was wondering what the plan was for dealing with the "Discouraged
access" warnings that we get with 3.2 from using internal, non API
methods? 

Brian Schlosser - bschloss@xxxxxxxxxx - 512-838-0521_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev