× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The platform.cfg files for workspaces that show the LPEX preferences contain
the following line of code (toward the bottom):

site.0.list.0=plugins/com.ibm.lpex_1.4.1/plugin.xml,plugins/com.ibm.lpex.doc
.isv_1.4.1/plugin.xml,plugins/com.ibm.lpex.doc.user_1.4.1/plugin.xml

The platform.cfg files for workspaces that do not show the LPEX preferences
contain this line of code instead:

site.0.list.0=plugins/com.ibm.lpex.doc.isv_1.4.2/plugin.xml,plugins/com.ibm.
lpex.doc.user_1.4.2/plugin.xml,plugins/com.ibm.lpex_1.4.2/plugin.xml

The plugins/com.ibm.lpex_1.4.1/plugin.xml file and the
plugins/com.ibm.lpex_1.4.2/plugin.xml file are causing the problem. In the
Install/Update perspective, it says I have lpex_1.4.2 installed and that I
need this version for my version of WDSCi.

In the site.0.url=file:C:/Program Files/IBM/WebSphere Studio/Site
Developer/v5.1/wstools/eclipse/ I found both the lpex_1.4.1/plugin.xml file
and the lpex_1.4.2/plugin.xml file.

I renamed the lpex_1.4.1/plugin.xml file and copied in the
lpex_1.4.2/plugin.xml file to replace it. In other words, the
plugins/com.ibm.lpex_1.4.1/ directory now contains the plugin.xml file from
the plugins/com.ibm.lpex_1.4.2/ directory. This worked.  

I'm still not exactly sure what's going on, but I suspect it has to do with
having Site Developer 5.1 installed over Site Developer 5.0.1.

Thanks,
Kelly

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.