Re: [eclipse-dev] Rich Client Platform UI changes to be released to HEAD

[Wassim Melhem <wassimm@xxxxxxxxxx>]

An addendum to my previous note:

During the migration, when PDE adds the new plug-in dependencies to reflect
the Platform plug-in restructuring, these new dependencies are added as
'soft' dependencies, i.e. with optional="true"
This is because at that point, i.e. prior to you fixing the compilation
errors, there is no way to determine without a shadow of a doubt which
subset of these dependencies are actually needed by your plug-in.
So adding a 'soft' dependency during the migration process is the prudent
thing to do.

However, after you fix the compilation errors, go to the Dependencies tab
of the plug-in manifest editor and from the context menu and select 'Find
Unused dependencies'.
PDE will then scan your list of dependencies and flag the ones that are not
used.  You can then remove these unused dependencies, if any.  At that
point, the optional="true" can also be removed from the dependencies that
are actually being used.

Wassim.




                                                                           
             Wassim                                                        
             Melhem/Toronto/IB                                             
             M@IBMCA                                                    To 
             Sent by:                  eclipse-dev@xxxxxxxxxxx             
             eclipse-dev-admin                                          cc 
             @eclipse.org                                                  
                                                                   Subject 
                                       Re: [eclipse-dev] Rich Client       
             11/03/2003 05:49          Platform UI changes to be released  
             PM                        to HEAD after integration build     
                                                                           
                                                                           
             Please respond to                                             
                eclipse-dev                                                
                                                                           
                                                                           








In an effort to smoothen the migration process, you will find in tomorrow's
I-build a migration wizard that will convert your plugin.xml/fragment.xml
files to become 3.0-compliant.
The wizard will:
  i. add the new mandatory processing instruction for 3.0-compliant
plug-ins, as described in the porting guide.
 ii. make necessary changes, if any, to the dependencies list of your
plug-in to reflect the restructuring of the Platform UI plug-ins and Help
plug-ins.
iii. make necessary changes, if any, to any extensions you might have that
are extending extension points whose ids have changed.
iv. optionally update your classpath.

The wizard can be found in the context menu of plugin.xml/fragment.xml
files/plug-in projects under
"PDE Tools -> Migrate to 3.0"




             Nick
             Edgar/Ottawa/IBM@
             IBMCA                                                      To
             Sent by:                  eclipse-dev@xxxxxxxxxxx,
             eclipse-dev-admin         platform-ui-dev@xxxxxxxxxxx
             @eclipse.org                                               cc

                                                                   Subject
             11/03/2003 03:02          [eclipse-dev] Rich Client Platform
             PM                        UI changes to be released to HEAD
                                       after integration build

             Please respond to
                eclipse-dev







Further to the changes announced below, the Platform UI, Text, and Help
teams, as well as affected downstream teams, will be releasing changes to
HEAD after this week's integration build.
The goal is to have the Platform UI, Text and Help changes released to
HEAD by Wednesday afternoon, with downstream teams adapting to the changes
over the rest of the week.
We aim to have everything working again in the Eclipse SDK in time for
next week's integration build.

Nick


----- Forwarded by Nick Edgar/Ottawa/IBM on 11/03/2003 02:57 PM -----

Kevin Haaland/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx
10/21/2003 11:14 AM
Please respond to
eclipse-dev


To
platform-ui-dev@xxxxxxxxxxx, eclipse-dev@xxxxxxxxxxx,
platform-dev@xxxxxxxxxxx
cc

Subject
[eclipse-dev] API implications of Eclipse Rich Client Platform UI work







As outlined in the 3.0 plan,  the eclipse team firmly believes in
preserving API compatability. With this mindset the team has produced a
propsal that results in a good overall Eclipse solution while keeping most
API intact. There is a bugzilla report for this plan item and
documentation available on the UI team's home page.

The bugzilla report for this plan item is:

        http://bugs.eclipse.org/bugs/show_bug.cgi?id=36967


The summary of the proposed changes and porting guide are here:


http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ui-home/rcp-proposal/generic_workbench_summary.html




http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ui-home/rcp-proposal/generic_workbench_porting_guide.html





If you are interested in this work or are concerned about the proposed API
changes I encourage you to review the available information and send your
comments to the platform-ui-dev@xxxxxxxxxxx mailing list.



/The Eclipse Platform Team
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
http://dev.eclipse.org/mailman/listinfo/eclipse-dev


_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
http://dev.eclipse.org/mailman/listinfo/eclipse-dev