| VE N20050516 problems with M7 [message #91411] |
Tue, 17 May 2005 12:55  |
Eclipse User |
|
|
|
Hello,
I'm unable to open a visual class with the new N20050516 for M7.
When I try to open the class, a message box appears with the following
message:
"Error trying to set new file into editor.
Reason: org.eclipse.ve.internal.java.core.BeanProxyAdapter".
I'm working over a clean Eclipse 3.1 M7 installation and a M6 workspace
(W2K).
Thanks in advance for your help,
Francesc Rosés
|
|
|
|
|
|
|
|
|
|
|
| Re: VE N20050516 problems with M7 [message #91673 is a reply to message #91659] |
Wed, 18 May 2005 14:03  |
| Eclipse User |
|
|
|
I checkout ve manual with (linux)
cvs co ve-all
I import existing projects (all plugins) in eclipse.
I try first export existing feature and it doesn't work
I make simple feature project and add all ve-plugins
export this feature and get logs.zip with error in 3 plugins
I the export this 3 plugins separately (one by one) and it compile fine
(mystery)
all is fine in runtime workbench (always), but I have error when deploy
plugins (sometimes) because exits error in build.properties
Thanks
Rich Kulp wrote:
> How are you building? It works fine if you check out through Eclipse and
> let the standard incremental editor compile them.
>
> If you are trying to build this outside of Eclipse:
>
> For jem.util: Create a dummy plugin called org.eclipse.perfmsr.core and
> put the perfmsr.jar found in the org.eclipse.jem.util checked CVS files.
> This is a stripped down only for compile against version of the jar. It
> will not run and it should not be in the runtime. It should only be in
> the build path.
>
> I don't understand the other other problems. You weren't specific.
>
|
|
|
| Re: VE N20050516 problems with M7 [message #607789 is a reply to message #91411] |
Tue, 17 May 2005 17:17 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
There are problems with the Nightly build. It was a first pass and
mostly Swing/AWT works but SWT has problems.
Did you run eclipse.exe -clean first after you unzipped the driver? You
need to do that to pick up the new code.
Francesc Rosés wrote:
> Hello,
> I'm unable to open a visual class with the new N20050516 for M7.
> When I try to open the class, a message box appears with the following
> message:
> "Error trying to set new file into editor.
> Reason: org.eclipse.ve.internal.java.core.BeanProxyAdapter".
>
> I'm working over a clean Eclipse 3.1 M7 installation and a M6 workspace
> (W2K).
> Thanks in advance for your help,
> Francesc Rosés
>
--
Thanks,
Rich Kulp
|
|
|
| Re: VE N20050516 problems with M7 [message #607791 is a reply to message #91476] |
Tue, 17 May 2005 20:08 |
| Eclipse User |
|
|
|
Rich,
I find similar problem when build from cvs
it work in runtime workbench, but 'create visual class' (swing application,
frame etc) doesn't work whe I build vep
reason : plugin org.eclipse.ve.jfc = build properties doesn't include
directory templates and i get 'null pointer error'
There are another files/directories non included in another plugins
regards
Haris Peco
Rich Kulp wrote:
> There are problems with the Nightly build. It was a first pass and
> mostly Swing/AWT works but SWT has problems.
>
> Did you run eclipse.exe -clean first after you unzipped the driver? You
> need to do that to pick up the new code.
>
> Francesc Rosés wrote:
>> Hello,
>> I'm unable to open a visual class with the new N20050516 for M7.
>> When I try to open the class, a message box appears with the following
>> message:
>> "Error trying to set new file into editor.
>> Reason: org.eclipse.ve.internal.java.core.BeanProxyAdapter".
>>
>> I'm working over a clean Eclipse 3.1 M7 installation and a M6 workspace
>> (W2K).
>> Thanks in advance for your help,
>> Francesc Rosés
>>
>
|
|
|
|
| Re: VE N20050516 problems with M7 [message #607794 is a reply to message #91533] |
Tue, 17 May 2005 18:42 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Oh, you said you were using an M6 workspace. You will also need to run
Project->Clean->Clean All Projects. There are some cached files laying
around from M6 that have changed and need to be recreated. See if that
helps.
Francesc Rosés wrote:
> Hello Rich,
> Yes I run Eclipse.exe with -clean.
>
> Thanks,
> Francesc
>
--
Thanks,
Rich Kulp
|
|
|
| Re: VE N20050516 problems with M7 [message #607795 is a reply to message #91505] |
Tue, 17 May 2005 19:00 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Yeah we just found the templates problem this afternoon. We just created
a new nightly build that fixes that problem, N20050517.
snpe wrote:
> Rich,
> I find similar problem when build from cvs
> it work in runtime workbench, but 'create visual class' (swing application,
> frame etc) doesn't work whe I build vep
> reason : plugin org.eclipse.ve.jfc = build properties doesn't include
> directory templates and i get 'null pointer error'
--
Thanks,
Rich Kulp
|
|
|
| Re: VE N20050516 problems with M7 [message #607796 is a reply to message #91561] |
Tue, 17 May 2005 21:37 |
| Eclipse User |
|
|
|
I see.Sorry.
I build from cvs and it work fine, but I have to build plugins
org.eclipse.jem.util - have problem with perfmsr.jar
org.eclipse.ve.jfc - return error when build with any another plugin
org.eclipse.ve.swt - like jfc
out of another plugin - I can set features and include all plugins
regards
Rich Kulp wrote:
> Yeah we just found the templates problem this afternoon. We just created
> a new nightly build that fixes that problem, N20050517.
>
> snpe wrote:
>> Rich,
>> I find similar problem when build from cvs
>> it work in runtime workbench, but 'create visual class' (swing
>> application, frame etc) doesn't work whe I build vep
>> reason : plugin org.eclipse.ve.jfc = build properties doesn't include
>> directory templates and i get 'null pointer error'
>
>
|
|
|
|
| Re: VE N20050516 problems with M7 [message #607802 is a reply to message #91575] |
Wed, 18 May 2005 11:42 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
How are you building? It works fine if you check out through Eclipse and
let the standard incremental editor compile them.
If you are trying to build this outside of Eclipse:
For jem.util: Create a dummy plugin called org.eclipse.perfmsr.core and
put the perfmsr.jar found in the org.eclipse.jem.util checked CVS files.
This is a stripped down only for compile against version of the jar. It
will not run and it should not be in the runtime. It should only be in
the build path.
I don't understand the other other problems. You weren't specific.
--
Thanks,
Rich Kulp
|
|
|
| Re: VE N20050516 problems with M7 [message #607803 is a reply to message #91659] |
Wed, 18 May 2005 14:03 |
| Eclipse User |
|
|
|
I checkout ve manual with (linux)
cvs co ve-all
I import existing projects (all plugins) in eclipse.
I try first export existing feature and it doesn't work
I make simple feature project and add all ve-plugins
export this feature and get logs.zip with error in 3 plugins
I the export this 3 plugins separately (one by one) and it compile fine
(mystery)
all is fine in runtime workbench (always), but I have error when deploy
plugins (sometimes) because exits error in build.properties
Thanks
Rich Kulp wrote:
> How are you building? It works fine if you check out through Eclipse and
> let the standard incremental editor compile them.
>
> If you are trying to build this outside of Eclipse:
>
> For jem.util: Create a dummy plugin called org.eclipse.perfmsr.core and
> put the perfmsr.jar found in the org.eclipse.jem.util checked CVS files.
> This is a stripped down only for compile against version of the jar. It
> will not run and it should not be in the runtime. It should only be in
> the build path.
>
> I don't understand the other other problems. You weren't specific.
>
|
|
|
Powered by
FUDForum. Page generated in 0.11414 seconds
Home