Eclipse Community Forums: TMF (Xtext) » issue with start levels in launch config?

Help

Home

Home » Modeling » TMF (Xtext) » issue with start levels in launch config?

Show: Today's Messages :: Show Polls :: Message Navigator

issue with start levels in launch config? [message #902986]

Tue, 21 August 2012 14:22

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

Hi,
I have a problem, and I think it has to do with start levels in the
launch configuration I am using when developing.

If I have a dirty editor and exit, I get a question if I want to save.
If I answer ok, the builder kicks in, and then it runs into problems
because some bundle(s) have been deactivated.

How can I figure out which bundles need "auto-start" or some start level
set?

e.g. the stacktrace I am looking at right now was caused by
org.eclipse.xtext.builder.internal.Activator.getDefault() returning null.

Hints how to fix this? It is very annoying when developing.
It seems to be ok in the built product, so I am not in panic :)

Regards
- henrik

Report message to a moderator

Re: issue with start levels in launch config? [message #903058 is a reply to message #902986]

Tue, 21 August 2012 18:39

Sebastian Zarnekow

Messages: 3118
Registered: July 2009

Senior Member

Hi Henrik,

I assume that the issue is caused by the builder where some resource
service providers shall be instantiated?
I think we need to listen to changes in the registered bundles in order
to deregister pending extension. That would probably do the trick.

Regards,
Sebastian
--
Looking for professional support for Xtext, Xtend or Eclipse Modeling?
Go visit: http://xtext.itemis.com

Am 21.08.12 16:22, schrieb Henrik Lindberg:
> Hi,
> I have a problem, and I think it has to do with start levels in the
> launch configuration I am using when developing.
>
> If I have a dirty editor and exit, I get a question if I want to save.
> If I answer ok, the builder kicks in, and then it runs into problems
> because some bundle(s) have been deactivated.
>
> How can I figure out which bundles need "auto-start" or some start level
> set?
>
> e.g. the stacktrace I am looking at right now was caused by
> org.eclipse.xtext.builder.internal.Activator.getDefault() returning null.
>
> Hints how to fix this? It is very annoying when developing.
> It seems to be ok in the built product, so I am not in panic :)
>
> Regards
> - henrik

Report message to a moderator

Re: issue with start levels in launch config? [message #903094 is a reply to message #903058]

Tue, 21 August 2012 21:20

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

On 2012-21-08 20:39, Sebastian Zarnekow wrote:
> Hi Henrik,
>
> I assume that the issue is caused by the builder where some resource
> service providers shall be instantiated?
> I think we need to listen to changes in the registered bundles in order
> to deregister pending extension. That would probably do the trick.
>
> Regards,
> Sebastian
Not sure, problem is really odd, and I have not seen it earlier. It may
have something to do with some screwed up launch config (me or
eclipse... don't know). I got the problem from lots of different places
- and IMO, those bundles should really be around, or a build would
simply not be possible (not a correct one in any case).

I am just switching over to Juno, and have not yet seen the problem
there - maybe it is just something odd with old workspace...

Will post again if the problem comes back on Juno; I have a suspeicion
that it could be because of build taking some time...

Regards
- henrik

Report message to a moderator

Previous Topic:	Use Xtend instead of Java in more places in the generated DSL implementation
Next Topic:	Type inference across inferred jvm elements

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 23:28:27 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter