New nightly? Customizer is failing. [message #92786] |
Thu, 02 June 2005 02:19  |
Eclipse User |
|
|
|
Originally posted by: no.ddress.here
Building VE from HEAD as of 6/1/2005.
Trying to verify the correct operation of the EXPLICIT_PROPERTY_CHANGE
attribute. Unfortunately, seems that setting EXPLICIT_PROPERTY_CHANGE
to TRUE results in a complete failure of VE to add the customizer JPanel
to the JFrame. The customizer JFrame is effectively size 0 with no
error messages being logged anywhere.
VE is also appears to now be failing to recognize another beaninfo that
worked previously. So, I cannot be sure that the problem is not with my
build.
Any chance at getting another nightly soon?
Thanks,
Gerald
|
|
|
|
|
Re: New nightly? Customizer is failing. [message #92886 is a reply to message #92871] |
Sat, 04 June 2005 03:32   |
Eclipse User |
|
|
|
Originally posted by: no.ddress.here
In article <d7o1so$163$1@news.eclipse.org>, winchest@uk.ibm.com says...
> Sorry my last fix failed. To correct it (again) was a tiny fix but I
> have just spent a fair while testing it with quite a few test cases and
> it looks OK now. Just released into HEAD.
>
> Best regards and apologies,
>
> Joe Winchester
>
Thanks.
Ok, now trying to test from head again: VE is evidently not recognizing
any of my customizers. Based on the absence of any logging messages
from my beaninfos, VE is simply not trying to read them; at least, there
are no messages of VE trying and failing for any reason.
These are the same beans/beaninfos that work just fine with the May 23
VE nightly.
Are you testing with the test case I sent in (JTestPanel2)? The
customizer in that test case was working with the prior head version.
Finally, to test VE, I have been launching the workbench as an Eclipse
Application, which seems to work. If, however, I try to export a
Deployable Plug-In, I just get a zipped log of errors (below). Can you
recommend a "best approach" for me to use in testing VE?
----------
1. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.ve.jfc
\vm_jfcbeaninfo\org\eclipse\ve\internal\jfc\beaninfo
\AbstractButtonBeanInfo.java
(at line 19)
public class AbstractButtonBeanInfo extends IvjBeanInfo {
^^^^^^^^^^^^^^^^^^^^^^
The hierarchy of the type AbstractButtonBeanInfo is inconsistent
----------
2. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.ve.jfc
\vm_jfcbeaninfo\org\eclipse\ve\internal\jfc\beaninfo
\AbstractButtonBeanInfo.java
(at line 32)
super.createMethodDescriptor(java.awt.event.ActionListener.c lass,
^^^^^^^^^^^^^^^^^^^^^^
The method createMethodDescriptor(Class, String, Object[],
ParameterDescriptor[], Class[]) is undefined for the type IvjBeanInfo
----------
3. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.ve.jfc
\vm_jfcbeaninfo\org\eclipse\ve\internal\jfc\beaninfo
\AbstractButtonBeanInfo.java
(at line 35)
DISPLAYNAME, resAbstractButton.getString
("MthdDesc.ActionPerformed.Name"), //$NON-NLS-1$
^^^^^^^^^^^
DISPLAYNAME cannot be resolved
----------
4. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.ve.jfc
\vm_jfcbeaninfo\org\eclipse\ve\internal\jfc\beaninfo
\AbstractButtonBeanInfo.java
(at line 40)
createParameterDescriptor("actionEvent", new Object[] { //$NON-
NLS-1$
^^^^^^^^^^^^^^^^^^^^^^^^^
The method createParameterDescriptor(String, Object[]) is undefined for
the type AbstractButtonBeanInfo
|
|
|
|
|
|
|
Re: New nightly? Customizer is failing. [message #92970 is a reply to message #92956] |
Sun, 05 June 2005 14:20  |
Eclipse User |
|
|
|
Originally posted by: no.ddress.here
In article <d7v8gb$8ek$1@news.eclipse.org>, no@ddress.here says...
> In article <d7si3q$rg4$1@news.eclipse.org>, richkulp@us.NO_SPAM.ibm.com
> says...
> > Catch up to HEAD again. I just released a change to the build.properties
> > which should allow you to do an export now.
>
> All but one appear to export fine. Cannot export org.eclipse.jem.util
> due to an unresolved dependency:
The perfmsr.jar is part of the project and the standard project build
does complete without errors -- meaning the stub jar is being found.
It is only the compile under Export that fails. Looking at the
plugin.xml, the Dependencies list shows the Required Plug-ins
"org.eclipse.perfmsr.core" with a red X.
Adding the perfmsr.jar to the plugin.xml -> Runtime Libraries list seems
to allow the export to complete -- and VE seems to run correctly. For
what little it may matter, still have that red X though.
HTHs and thanks,
Gerald
|
|
|
Re: New nightly? Customizer is failing. [message #607877 is a reply to message #92786] |
Thu, 02 June 2005 17:00  |
Eclipse User |
|
|
|
Hi Gerald,
> Trying to verify the correct operation of the EXPLICIT_PROPERTY_CHANGE
> attribute. Unfortunately, seems that setting EXPLICIT_PROPERTY_CHANGE
> to TRUE results in a complete failure of VE to add the customizer JPanel
> to the JFrame. The customizer JFrame is effectively size 0 with no
> error messages being logged anywhere.
>
> VE is also appears to now be failing to recognize another beaninfo that
> worked previously. So, I cannot be sure that the problem is not with my
> build.
I'll take a look. If possible you could e-mail me a test case so I can
hopefully stop you having to be the guinea pig ?
Best regards,
Joe
|
|
|
Re: New nightly? Customizer is failing. [message #607879 is a reply to message #92786] |
Thu, 02 June 2005 18:40  |
Eclipse User |
|
|
|
Hi Gerald,
> Trying to verify the correct operation of the EXPLICIT_PROPERTY_CHANGE
> attribute. Unfortunately, seems that setting EXPLICIT_PROPERTY_CHANGE
> to TRUE results in a complete failure of VE to add the customizer JPanel
> to the JFrame. The customizer JFrame is effectively size 0 with no
> error messages being logged anywhere.
>
> VE is also appears to now be failing to recognize another beaninfo that
> worked previously. So, I cannot be sure that the problem is not with my
> build.
Sorry my last fix failed. To correct it (again) was a tiny fix but I
have just spent a fair while testing it with quite a few test cases and
it looks OK now. Just released into HEAD.
Best regards and apologies,
Joe Winchester
|
|
|
Re: New nightly? Customizer is failing. [message #607880 is a reply to message #92871] |
Sat, 04 June 2005 03:32  |
Eclipse User |
|
|
|
In article <d7o1so$163$1@news.eclipse.org>, winchest@uk.ibm.com says...
> Sorry my last fix failed. To correct it (again) was a tiny fix but I
> have just spent a fair while testing it with quite a few test cases and
> it looks OK now. Just released into HEAD.
>
> Best regards and apologies,
>
> Joe Winchester
>
Thanks.
Ok, now trying to test from head again: VE is evidently not recognizing
any of my customizers. Based on the absence of any logging messages
from my beaninfos, VE is simply not trying to read them; at least, there
are no messages of VE trying and failing for any reason.
These are the same beans/beaninfos that work just fine with the May 23
VE nightly.
Are you testing with the test case I sent in (JTestPanel2)? The
customizer in that test case was working with the prior head version.
Finally, to test VE, I have been launching the workbench as an Eclipse
Application, which seems to work. If, however, I try to export a
Deployable Plug-In, I just get a zipped log of errors (below). Can you
recommend a "best approach" for me to use in testing VE?
----------
1. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.ve.jfc
\vm_jfcbeaninfo\org\eclipse\ve\internal\jfc\beaninfo
\AbstractButtonBeanInfo.java
(at line 19)
public class AbstractButtonBeanInfo extends IvjBeanInfo {
^^^^^^^^^^^^^^^^^^^^^^
The hierarchy of the type AbstractButtonBeanInfo is inconsistent
----------
2. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.ve.jfc
\vm_jfcbeaninfo\org\eclipse\ve\internal\jfc\beaninfo
\AbstractButtonBeanInfo.java
(at line 32)
super.createMethodDescriptor(java.awt.event.ActionListener.c lass,
^^^^^^^^^^^^^^^^^^^^^^
The method createMethodDescriptor(Class, String, Object[],
ParameterDescriptor[], Class[]) is undefined for the type IvjBeanInfo
----------
3. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.ve.jfc
\vm_jfcbeaninfo\org\eclipse\ve\internal\jfc\beaninfo
\AbstractButtonBeanInfo.java
(at line 35)
DISPLAYNAME, resAbstractButton.getString
("MthdDesc.ActionPerformed.Name"), //$NON-NLS-1$
^^^^^^^^^^^
DISPLAYNAME cannot be resolved
----------
4. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.ve.jfc
\vm_jfcbeaninfo\org\eclipse\ve\internal\jfc\beaninfo
\AbstractButtonBeanInfo.java
(at line 40)
createParameterDescriptor("actionEvent", new Object[] { //$NON-
NLS-1$
^^^^^^^^^^^^^^^^^^^^^^^^^
The method createParameterDescriptor(String, Object[]) is undefined for
the type AbstractButtonBeanInfo
|
|
|
|
Re: New nightly? Customizer is failing. [message #607882 is a reply to message #92886] |
Sat, 04 June 2005 20:24  |
Eclipse User |
|
|
|
Hi Gerald,
> Are you testing with the test case I sent in (JTestPanel2)? The
> customizer in that test case was working with the prior head version.
Where can I get the jar(s) to satisfy the import:
import org.apache.log4j.Logger;
Best regards,
Joe Winchester
|
|
|
|
Re: New nightly? Customizer is failing. [message #607885 is a reply to message #92900] |
Sun, 05 June 2005 12:20  |
Eclipse User |
|
|
|
In article <d7si3q$rg4$1@news.eclipse.org>, richkulp@us.NO_SPAM.ibm.com
says...
> Catch up to HEAD again. I just released a change to the build.properties
> which should allow you to do an export now.
All but one appear to export fine. Cannot export org.eclipse.jem.util
due to an unresolved dependency:
----------
1. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.jem.util
\jemutil\org\eclipse\jem\util\PerformanceMonitorUtil.java
(at line 18)
import org.eclipse.perfmsr.core.IPerformanceMonitor;
^^^^^^^^^^^^^^^^^^^
The import org.eclipse.perfmsr cannot be resolved
----------
2. WARNING in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.jem.util
\jemutil\org\eclipse\jem\util\PerformanceMonitorUtil.java
(at line 35)
public static class PerformanceEvent extends EventObject {
^^^^^^^^^^^^^^^^
The serializable class PerformanceEvent does not declare a static final
serialVersionUID field of type long
----------
3. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.jem.util
\jemutil\org\eclipse\jem\util\PerformanceMonitorUtil.java
(at line 94)
int OperatingSystemCounters =
IPerformanceMonitor.Types.OperatingSystemCounters;
^^^^^^^^^^^^^^^^^^^
IPerformanceMonitor cannot be resolved
----------
4. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.jem.util
\jemutil\org\eclipse\jem\util\PerformanceMonitorUtil.java
(at line 102)
int GlobalSystemCounters =
IPerformanceMonitor.Types.GlobalSystemCounters;
^^^^^^^^^^^^^^^^^^^
IPerformanceMonitor cannot be resolved
----------
5. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.jem.util
\jemutil\org\eclipse\jem\util\PerformanceMonitorUtil.java
(at line 107)
int JavaHeapSize = IPerformanceMonitor.Types.JavaHeapSize;
^^^^^^^^^^^^^^^^^^^
IPerformanceMonitor cannot be resolved
----------
6. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.jem.util
\jemutil\org\eclipse\jem\util\PerformanceMonitorUtil.java
(at line 112)
int JavaHeapUsed = IPerformanceMonitor.Types.JavaHeapUsed;
^^^^^^^^^^^^^^^^^^^
IPerformanceMonitor cannot be resolved
----------
7. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.jem.util
\jemutil\org\eclipse\jem\util\PerformanceMonitorUtil.java
(at line 117)
int PluginInfo = IPerformanceMonitor.Types.PluginInfo;
^^^^^^^^^^^^^^^^^^^
IPerformanceMonitor cannot be resolved
----------
8. ERROR in D:\DevFiles\EclipseWorkSpace31M7\org.eclipse.jem.util
\jemutil\org\eclipse\jem\util\PerformanceMonitorUtil.java
(at line 120)
int All = IPerformanceMonitor.Types.All;
^^^^^^^^^^^^^^^^^^^
IPerformanceMonitor cannot be resolved
----------
|
|
|
Re: New nightly? Customizer is failing. [message #607886 is a reply to message #92956] |
Sun, 05 June 2005 14:20  |
Eclipse User |
|
|
|
In article <d7v8gb$8ek$1@news.eclipse.org>, no@ddress.here says...
> In article <d7si3q$rg4$1@news.eclipse.org>, richkulp@us.NO_SPAM.ibm.com
> says...
> > Catch up to HEAD again. I just released a change to the build.properties
> > which should allow you to do an export now.
>
> All but one appear to export fine. Cannot export org.eclipse.jem.util
> due to an unresolved dependency:
The perfmsr.jar is part of the project and the standard project build
does complete without errors -- meaning the stub jar is being found.
It is only the compile under Export that fails. Looking at the
plugin.xml, the Dependencies list shows the Required Plug-ins
"org.eclipse.perfmsr.core" with a red X.
Adding the perfmsr.jar to the plugin.xml -> Runtime Libraries list seems
to allow the export to complete -- and VE seems to run correctly. For
what little it may matter, still have that red X though.
HTHs and thanks,
Gerald
|
|
|
Powered by
FUDForum. Page generated in 0.28248 seconds