Re: [wtp-dev] Migration to Eclipse based Tabbed Properties

[David M Williams <david_williams@xxxxxxxxxx>]

To be clear ... the plan is to leave
in until M6 (to allow time for migration), but to remove after M6 ... UNLESS
an adopter asks us to leave it in. If someone needs it for some sort of
binary compatibility, I think that's fine, But ... they will have to live
with it "as is", we can't support it, nor guarantee it would
really work as expected (with the base one present also). Since this has
been announced and the plan since even before 0.7, it should not catch
anyone by surprise and I'm sure most adopters have planned for it. 

If adopters do not migrate, and want
us to leave in the old one, then their "non-API-non-platform"
debt will grow, and while not technically "our problem" ... it
is indirectly, as we need to make progress on "being a better platform"
or there will continue to be an increasing probability of problems when
users install plugins from many sources.

Craig Salter <csalter@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

02/14/2006 04:27 PM

Please respond to
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Migration to Eclipse based Tabbed Properties

I agree we should keep the old plugin there.  Keith, I assume there's
no co-existance issues between the old and new Tabbed Properties?

thanks

Craig


Craig Salter
Rational Studio XML Web Services
Internal Mail: D3/RY6/8200 /MKM 
Phone: (905) 413-3918  TL: 969-3918 FAX: (905) 413-4920
Internet: csalter@xxxxxxxxxx     Notes: Craig Salter/Toronto/IBM@IBMCA

Lawrence Mandel/Toronto/IBM@IBMCA
Sent by: wtp-dev-bounces@xxxxxxxxxxx

02/14/2006 04:07 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Migration to Eclipse based Tabbed Properties

>The plan is for clients to migrate before WTP M6.  (See https://bugs.eclipse.org/bugs/show_bug.cgi?id=125745).
  The WST plugin will be marked deprecated for >now, and will be
removed after M6. 

In our effort to not break adopters it may be better to simply deprecate
the WST plug-in but still include it in WTP 1.5. Are you sure no adopters
are using this plug-in? 

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920
lmandel@xxxxxxxxxx

Keith Chong/Toronto/IBM@IBMCA
Sent by: wtp-dev-bounces@xxxxxxxxxxx

02/14/2006 03:35 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	wtp-dev@xxxxxxxxxxx
cc
Subject	[wtp-dev] Migration to Eclipse based Tabbed Properties

The org.eclipse.wst.common.ui.properties plugin (for tabbed properties)
has been moved to the eclipse base M5. 

For those clients using this plugin, please migrate to the new plugin org.eclipse.ui.views.properties.
 The migration document, courtesy of Anthony, can be found in bug
109878. 

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

The plan is for clients to migrate before WTP M6.  (See https://bugs.eclipse.org/bugs/show_bug.cgi?id=125745).
  The WST plugin will be marked deprecated for now, and will be removed
after M6.. 

Regards,
Keith Chong
D3/QCS/8200/MKM
Phone: (905) 413-4370    T/L: 969-4370
e-mail: kchong@xxxxxxxxxx


----- Forwarded by Keith Chong/Toronto/IBM on 14/02/2006 02:56 PM -----

David M Williams <david_williams@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

13/02/2006 02:48 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	wtp-dev@xxxxxxxxxxx
cc
Subject	[wtp-dev] Moving to new pre-M5 build: Part 1

In case anyone hasn't seen posts on other dev lists, now that we are moving
up to a new pre-M5 version of our Eclipse Project pre-req, 
we are supposed to move up to a pre-M5 version of the development environment.
As far as  I know, the only consequence of not doing this 
is that getPlugionDescriptor() will show up as a compile error. (We should
still get rid of our use of that deprecated method, but, it should be 
a warning, not an error). I've been using  I20060208-0848 and its
seems basically ok. This is the same version we are using in our builds.

Don't forget the corresponding "release engineering" tool. 
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev