Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » CVS plugins and compilation errors
CVS plugins and compilation errors [message #128301] Thu, 16 April 2009 18:01 Go to next message
Eclipse UserFriend
Originally posted by: benjamin.wolff.web.de

Hi,


i'm using the latest CVS HEAD of the RAP plugins.
the plugins org.eclipse.rap.jface and org.eclipse.rap.ui.workbench are having compile errors
saying that some private constructors are never used locally. these errors are causing the following
exception when starting the application:

java.lang.RuntimeException: Could not create the session singleton instance of 'org.eclipse.ui.internal.WorkbenchPlugin$ThemeRegistryStore' because an Exception was thrown by the constructor:
Unresolved compilation problems:
The constructor WorkbenchPlugin.ThemeRegistryStore() is never used locally
The constructor WorkbenchPlugin.WorkingSetRegistryStore() is never used locally
..
at org.eclipse.rwt.SessionSingletonBase.getInstanceInternal(Ses sionSingletonBase.java:189)
.....


the project-specific compile options cause unused private members to be handled as an error.
i can overwrite these project-specific options, the exception is not thrown then, but are these
strong compile options actually intended?


greetings,
ben
Re: CVS plugins and compilation errors [message #128314 is a reply to message #128301] Thu, 16 April 2009 19:16 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
Ben,

the workbench plug-in is adopted from RCP, so are the compiler
settings. The intention was to leave things unchanged as much as
possible.
However, I am also working against CVS HEAD and do not have any errors.
Are you sure that you checked out from the /cvsroot/rt repository?

HTH
Rüdiger

Ben W. wrote:
> Hi,
>
>
> i'm using the latest CVS HEAD of the RAP plugins.
> the plugins org.eclipse.rap.jface and org.eclipse.rap.ui.workbench are
> having compile errors
> saying that some private constructors are never used locally. these
> errors are causing the following
> exception when starting the application:
>
> java.lang.RuntimeException: Could not create the session singleton
> instance of 'org.eclipse.ui.internal.WorkbenchPlugin$ThemeRegistryStore'
> because an Exception was thrown by the constructor:
> Unresolved compilation problems: The constructor
> WorkbenchPlugin.ThemeRegistryStore() is never used locally
> The constructor WorkbenchPlugin.WorkingSetRegistryStore() is never
> used locally
> ..
> at
> org.eclipse.rwt.SessionSingletonBase.getInstanceInternal(Ses sionSingletonBase.java:189)
>
> .....
>
>
> the project-specific compile options cause unused private members to be
> handled as an error.
> i can overwrite these project-specific options, the exception is not
> thrown then, but are these
> strong compile options actually intended?
>
>
> greetings,
> ben
Re: CVS plugins and compilation errors [message #128328 is a reply to message #128314] Thu, 16 April 2009 19:38 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: benjamin.wolff.web.de

hmmm, that's odd.

yes, i'm using the /cvsroot/rt plugins. could you check the plugin properties ->
java compiler -> errors/warnings -> unnecessary code.. there are some options set to
'error' in your workspace?!

however the errors have gone after i reverted the plugin to base and then updated from
cvs again. but i didn't change anything in the plugin before, there also wasn't a '>'
before the plugin name...

nevertheless it's gone for now, i was just curious if someone else is experiencing
a similiar problem. thanks!

greetings,
ben




Rüdiger Herrmann schrieb:
> Ben,
>
> the workbench plug-in is adopted from RCP, so are the compiler settings.
> The intention was to leave things unchanged as much as possible.
> However, I am also working against CVS HEAD and do not have any errors.
> Are you sure that you checked out from the /cvsroot/rt repository?
>
> HTH
> Rüdiger
>
> Ben W. wrote:
>> Hi,
>>
>>
>> i'm using the latest CVS HEAD of the RAP plugins.
>> the plugins org.eclipse.rap.jface and org.eclipse.rap.ui.workbench are
>> having compile errors
>> saying that some private constructors are never used locally. these
>> errors are causing the following
>> exception when starting the application:
>>
>> java.lang.RuntimeException: Could not create the session singleton
>> instance of
>> 'org.eclipse.ui.internal.WorkbenchPlugin$ThemeRegistryStore' because
>> an Exception was thrown by the constructor:
>> Unresolved compilation problems: The constructor
>> WorkbenchPlugin.ThemeRegistryStore() is never used locally
>> The constructor WorkbenchPlugin.WorkingSetRegistryStore() is never
>> used locally
>> ..
>> at
>> org.eclipse.rwt.SessionSingletonBase.getInstanceInternal(Ses sionSingletonBase.java:189)
>>
>> .....
>>
>>
>> the project-specific compile options cause unused private members to
>> be handled as an error.
>> i can overwrite these project-specific options, the exception is not
>> thrown then, but are these
>> strong compile options actually intended?
>>
>>
>> greetings,
>> ben
Re: CVS plugins and compilation errors [message #128340 is a reply to message #128328] Thu, 16 April 2009 20:05 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
Ben W. wrote:
> hmmm, that's odd.
>
> yes, i'm using the /cvsroot/rt plugins. could you check the plugin
> properties ->
> java compiler -> errors/warnings -> unnecessary code.. there are some
> options set to
> 'error' in your workspace?!
yes, they are set to 'error'

>
> however the errors have gone after i reverted the plugin to base and
> then updated from
> cvs again. but i didn't change anything in the plugin before, there also
> wasn't a '>'
> before the plugin name...
strange, indeed.

>
> nevertheless it's gone for now, i was just curious if someone else is
> experiencing
> a similiar problem. thanks!
Sorry, I can't help here. For me, it works out of the box.

>
> greetings,
> ben
>
>
>
>
> Rüdiger Herrmann schrieb:
>> Ben,
>>
>> the workbench plug-in is adopted from RCP, so are the compiler
>> settings. The intention was to leave things unchanged as much as
>> possible.
>> However, I am also working against CVS HEAD and do not have any errors.
>> Are you sure that you checked out from the /cvsroot/rt repository?
>>
>> HTH
>> Rüdiger
>>
>> Ben W. wrote:
>>> Hi,
>>>
>>>
>>> i'm using the latest CVS HEAD of the RAP plugins.
>>> the plugins org.eclipse.rap.jface and org.eclipse.rap.ui.workbench
>>> are having compile errors
>>> saying that some private constructors are never used locally. these
>>> errors are causing the following
>>> exception when starting the application:
>>>
>>> java.lang.RuntimeException: Could not create the session singleton
>>> instance of
>>> 'org.eclipse.ui.internal.WorkbenchPlugin$ThemeRegistryStore' because
>>> an Exception was thrown by the constructor:
>>> Unresolved compilation problems: The constructor
>>> WorkbenchPlugin.ThemeRegistryStore() is never used locally
>>> The constructor WorkbenchPlugin.WorkingSetRegistryStore() is
>>> never used locally
>>> ..
>>> at
>>> org.eclipse.rwt.SessionSingletonBase.getInstanceInternal(Ses sionSingletonBase.java:189)
>>>
>>> .....
>>>
>>>
>>> the project-specific compile options cause unused private members to
>>> be handled as an error.
>>> i can overwrite these project-specific options, the exception is not
>>> thrown then, but are these
>>> strong compile options actually intended?
>>>
>>>
>>> greetings,
>>> ben
Re: CVS plugins and compilation errors [message #128379 is a reply to message #128328] Thu, 16 April 2009 20:34 Go to previous messageGo to next message
Ralf Sternberg is currently offline Ralf SternbergFriend
Messages: 1313
Registered: July 2009
Senior Member

Hi,

> yes, i'm using the /cvsroot/rt plugins. could you check the plugin
> properties ->
> java compiler -> errors/warnings -> unnecessary code.. there are some
> options set to
> 'error' in your workspace?!

Obviously, some new compiler preferences have been introduced with
Eclipse 3.5 M6. These are still missing in our plugin preferences and
the aggressive defaults seem to cause these errors. I guess we'll need
to update our preferences files.

Still strange that we only see those errors for these two plug-ins.

> however the errors have gone after i reverted the plugin to base and
> then updated from
> cvs again. but i didn't change anything in the plugin before, there also
> wasn't a '>'
> before the plugin name...

Strange. Still with M6 and didn't change your workspace settings?

Cheers,
Ralf


> Rüdiger Herrmann schrieb:
>> Ben,
>>
>> the workbench plug-in is adopted from RCP, so are the compiler
>> settings. The intention was to leave things unchanged as much as
>> possible.
>> However, I am also working against CVS HEAD and do not have any errors.
>> Are you sure that you checked out from the /cvsroot/rt repository?
>>
>> HTH
>> Rüdiger
>>
>> Ben W. wrote:
>>> Hi,
>>>
>>>
>>> i'm using the latest CVS HEAD of the RAP plugins.
>>> the plugins org.eclipse.rap.jface and org.eclipse.rap.ui.workbench
>>> are having compile errors
>>> saying that some private constructors are never used locally. these
>>> errors are causing the following
>>> exception when starting the application:
>>>
>>> java.lang.RuntimeException: Could not create the session singleton
>>> instance of
>>> 'org.eclipse.ui.internal.WorkbenchPlugin$ThemeRegistryStore' because
>>> an Exception was thrown by the constructor:
>>> Unresolved compilation problems: The constructor
>>> WorkbenchPlugin.ThemeRegistryStore() is never used locally
>>> The constructor WorkbenchPlugin.WorkingSetRegistryStore() is
>>> never used locally
>>> ..
>>> at
>>> org.eclipse.rwt.SessionSingletonBase.getInstanceInternal(Ses sionSingletonBase.java:189)
>>>
>>> .....
>>>
>>>
>>> the project-specific compile options cause unused private members to
>>> be handled as an error.
>>> i can overwrite these project-specific options, the exception is not
>>> thrown then, but are these
>>> strong compile options actually intended?
>>>
>>>
>>> greetings,
>>> ben
Re: CVS plugins and compilation errors [message #128392 is a reply to message #128340] Thu, 16 April 2009 20:41 Go to previous messageGo to next message
Benjamin Muskalla is currently offline Benjamin MuskallaFriend
Messages: 338
Registered: July 2009
Senior Member
One thing which came to my mind when I read the questions:

The JDT/Core compiler had a bug which manifested itself as a too strict
"dead code" detection.

As far as I remember this is gone in 3.5M6. Do you use the Eclipse
milestone builds?

Rüdiger Herrmann wrote:
> Ben W. wrote:
>> hmmm, that's odd.
>>
>> yes, i'm using the /cvsroot/rt plugins. could you check the plugin
>> properties ->
>> java compiler -> errors/warnings -> unnecessary code.. there are some
>> options set to
>> 'error' in your workspace?!
> yes, they are set to 'error'
>
>>
>> however the errors have gone after i reverted the plugin to base and
>> then updated from
>> cvs again. but i didn't change anything in the plugin before, there
>> also wasn't a '>'
>> before the plugin name...
> strange, indeed.
>
>>
>> nevertheless it's gone for now, i was just curious if someone else is
>> experiencing
>> a similiar problem. thanks!
> Sorry, I can't help here. For me, it works out of the box.
>
>>
>> greetings,
>> ben
>>
>>
>>
>>
>> Rüdiger Herrmann schrieb:
>>> Ben,
>>>
>>> the workbench plug-in is adopted from RCP, so are the compiler
>>> settings. The intention was to leave things unchanged as much as
>>> possible.
>>> However, I am also working against CVS HEAD and do not have any errors.
>>> Are you sure that you checked out from the /cvsroot/rt repository?
>>>
>>> HTH
>>> Rüdiger
>>>
>>> Ben W. wrote:
>>>> Hi,
>>>>
>>>>
>>>> i'm using the latest CVS HEAD of the RAP plugins.
>>>> the plugins org.eclipse.rap.jface and org.eclipse.rap.ui.workbench
>>>> are having compile errors
>>>> saying that some private constructors are never used locally. these
>>>> errors are causing the following
>>>> exception when starting the application:
>>>>
>>>> java.lang.RuntimeException: Could not create the session singleton
>>>> instance of
>>>> 'org.eclipse.ui.internal.WorkbenchPlugin$ThemeRegistryStore' because
>>>> an Exception was thrown by the constructor:
>>>> Unresolved compilation problems: The constructor
>>>> WorkbenchPlugin.ThemeRegistryStore() is never used locally
>>>> The constructor WorkbenchPlugin.WorkingSetRegistryStore() is
>>>> never used locally
>>>> ..
>>>> at
>>>> org.eclipse.rwt.SessionSingletonBase.getInstanceInternal(Ses sionSingletonBase.java:189)
>>>>
>>>> .....
>>>>
>>>>
>>>> the project-specific compile options cause unused private members to
>>>> be handled as an error.
>>>> i can overwrite these project-specific options, the exception is not
>>>> thrown then, but are these
>>>> strong compile options actually intended?
>>>>
>>>>
>>>> greetings,
>>>> ben


--
Benjamin Muskalla | EclipseSource Karlsruhe
http://www.eclipsesource.com | http://twitter.com/eclipsesource
Re: CVS plugins and compilation errors [message #128405 is a reply to message #128379] Thu, 16 April 2009 21:11 Go to previous message
Eclipse UserFriend
Originally posted by: benjamin.wolff.web.de

hi,

yes ralf, i'm using the latest eclipse milestone (build-id: I20090313-0100).

it's getting more strange, looking at the class org.eclipse.jface.util.Assert
the public constructor AssertionFailedException() is marked as never used locally with
an error. the project, however, only reports warning and compiles well. sometime these
'used locally' warnings are threated as fata compile errors and sometimes they aren't.
didn't change any of my workspace options...

this might even originate from an eclipse jdt bug, but since this issue, if it occurs,
can be easily solved by overriding the project specific compile warnings/erros it shouldn't
break any applications working against cvs head.

thx for your hints!

greetings,
ben



Ralf Sternberg schrieb:
> Hi,
>
>> yes, i'm using the /cvsroot/rt plugins. could you check the plugin
>> properties ->
>> java compiler -> errors/warnings -> unnecessary code.. there are some
>> options set to
>> 'error' in your workspace?!
>
> Obviously, some new compiler preferences have been introduced with
> Eclipse 3.5 M6. These are still missing in our plugin preferences and
> the aggressive defaults seem to cause these errors. I guess we'll need
> to update our preferences files.
>
> Still strange that we only see those errors for these two plug-ins.
>
>> however the errors have gone after i reverted the plugin to base and
>> then updated from
>> cvs again. but i didn't change anything in the plugin before, there also
>> wasn't a '>'
>> before the plugin name...
>
> Strange. Still with M6 and didn't change your workspace settings?
>
> Cheers,
> Ralf
>
>
>> Rüdiger Herrmann schrieb:
>>> Ben,
>>>
>>> the workbench plug-in is adopted from RCP, so are the compiler
>>> settings. The intention was to leave things unchanged as much as
>>> possible.
>>> However, I am also working against CVS HEAD and do not have any errors.
>>> Are you sure that you checked out from the /cvsroot/rt repository?
>>>
>>> HTH
>>> Rüdiger
>>>
>>> Ben W. wrote:
>>>> Hi,
>>>>
>>>>
>>>> i'm using the latest CVS HEAD of the RAP plugins.
>>>> the plugins org.eclipse.rap.jface and org.eclipse.rap.ui.workbench
>>>> are having compile errors
>>>> saying that some private constructors are never used locally. these
>>>> errors are causing the following
>>>> exception when starting the application:
>>>>
>>>> java.lang.RuntimeException: Could not create the session singleton
>>>> instance of
>>>> 'org.eclipse.ui.internal.WorkbenchPlugin$ThemeRegistryStore' because
>>>> an Exception was thrown by the constructor:
>>>> Unresolved compilation problems: The constructor
>>>> WorkbenchPlugin.ThemeRegistryStore() is never used locally
>>>> The constructor WorkbenchPlugin.WorkingSetRegistryStore() is
>>>> never used locally
>>>> ..
>>>> at
>>>> org.eclipse.rwt.SessionSingletonBase.getInstanceInternal(Ses sionSingletonBase.java:189)
>>>>
>>>> .....
>>>>
>>>>
>>>> the project-specific compile options cause unused private members to
>>>> be handled as an error.
>>>> i can overwrite these project-specific options, the exception is not
>>>> thrown then, but are these
>>>> strong compile options actually intended?
>>>>
>>>>
>>>> greetings,
>>>> ben
Previous Topic:org.eclipse.ui.forms with RWT
Next Topic:Context Disposed Problem
Goto Forum:
  


Current Time: Wed Dec 01 22:37:51 GMT 2021

Powered by FUDForum. Page generated in 0.01765 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top