Description Oliver Soehnges 2005-06-22 11:50:31 EDT

Until Eclipse 3.0 we used the constant 
ID "org.eclipse.ui.propertypages.info.file" for creating an "Info" property 
page as first and topmost entry of all property pages of an entity. We saw and 
still see no other possibility to ignore the alphabetic sort order of the 
entries. Additionaly we define an filter for each property page in the 
following way:

         <filter
               name="remoteclass"
               value="com.fujitsu.enabler.scm.EScmProject">
         </filter>

This worked well until Eclipse 3.0. But with the latest version of Eclipse 3.1 
(downloaded today) the filter check doesn't work any more, because Eclipse 3.1 
seems to have problems with the multiple used ids for the same object class.

Here a short sample for the problem:

     <page
            objectClass="com.fujitsu.enabler.eclipse.scm.Class1"
            adaptable="false"
            name="Info"
            class="com.fujitsu.enabler.eclipse.scm.ui.PropPageClass1"
            id="org.eclipse.ui.propertypages.info.file">
            <filter
               name="filter1"
               value="value1">
            </filter>
     </page>
     <page
            objectClass="com.fujitsu.enabler.eclipse.scm.Class1"
            adaptable="false"
            name="Info"              
            class="com.fujitsu.enabler.eclipse.scm.ui.PropPageClass2"
            id="org.eclipse.ui.propertypages.info.file">
            <filter
               name="filter2"
               value="value2">
            </filter>
     </page>

If the property pages for "com.fujitsu.enabler.eclipse.scm.Class1" are called, 
only the filter "filter2" will be checked. "filter1" check is not invoked (but 
was invoked with Eclipse 3.0).

I agree that it maybe it's not valid to define the same id twice, but if not, 
we would at least need some possiblity to set a define page (like "Info") as 
first entry of the list...

Thanks for any comments about this....