Eclipse Community Forums: Equinox » Eclipse 3.2 M4 or M5 + Webstart -> Impossible !

Home » Eclipse Projects » Equinox » Eclipse 3.2 M4 or M5 + Webstart -> Impossible !

Eclipse 3.2 M4 or M5 + Webstart -> Impossible ! [message #62786]

Wed, 01 March 2006 02:32

Eclipse User

Hello,

We are on the critical path of our development and JWS and Eclipse 3.2
features are the integral part of our app.

Because of this BUG (#128802) and very, very bad timing we are a bit
anxious to figure out how can this be resolved. Can anyone provide any
hints or insights how can we resolve this issue? Although I believe
that this issue might be resolved in 3.2M6 the problem is in that
our code freeze is just around that time and we can not afford to
wait that long.

We need to make decision if we should drop it altogether.

Any help would be appreciated.

Re: Eclipse 3.2 M4 or M5 + Webstart -> Impossible ! [message #62803 is a reply to message #62786]

Wed, 01 March 2006 03:16

Eclipse User

Originally posted by: alex_blewitt.yahoo.com

I believe that the problem is you're working on milestone code, which combined with a code freeze isn't a great project management decision. APIs can change under your feet during Milestone builds; having a product with a code freeze that's built on potentially shifting sands is an invitation to disaster ...

That said, given that the API freeze has begun, maybe that you'll be OK. However, you've obviously hit one of the problems that is integral to the way milestone builds work; they show off new features, but at the expense of potential unknown bugs.

I'd say that there's a reasonable chance that a fix will be forthcoming. If you keep the bug tracked (add yourself as a CC) then you'll know when the bug is fixed, and you can chose to use a nightly build that fixes that issue, or at least download the plugin(s) that do.

But the basic problem is one of poor project management, but fortunately learning from mistakes is one of the things that people tend to be good at.

Alex.

Re: Eclipse 3.2 M4 or M5 + Webstart -> Impossible ! [message #62863 is a reply to message #62786]

Wed, 01 March 2006 07:29

Eclipse User

Originally posted by: pascal.ibm.canada

Any problem like that should be reported in a bug report.
However it has already been done and a workaround is detailed in the bug
report. It consists in setting the osgi.bundles property in the jnlp file.

Ivan B wrote:
>
> Hello,
>
> We are on the critical path of our development and JWS and Eclipse 3.2
> features are the integral part of our app.
>
> Because of this BUG (#128802) and very, very bad timing we are a bit
> anxious to figure out how can this be resolved. Can anyone provide any
> hints or insights how can we resolve this issue? Although I believe
> that this issue might be resolved in 3.2M6 the problem is in that
> our code freeze is just around that time and we can not afford to
> wait that long.
>
> We need to make decision if we should drop it altogether.
>
> Any help would be appreciated.

Re: Eclipse 3.2 M4 or M5 + Webstart -> Impossible ! [message #62872 is a reply to message #62803]

Wed, 01 March 2006 16:18

Eclipse User

Originally posted by: public.bojerco.REMOVE.com

Thank you for your reply. I do agree with you that this is a risky
decision from a project management point of the view. Unfortunately such
decisions are sometime absolutely needed when you are developing on the
cutting edge. There is also another factor called "time to market." We
evaluated all there risks and decided to give it a go, especially with
Eclipse's proven record of having very stable and reliable "M" builds.

Alex Blewitt wrote:
> I believe that the problem is you're working on milestone code, which combined with a code freeze isn't a great project management decision. APIs can change under your feet during Milestone builds; having a product with a code freeze that's built on potentially shifting sands is an invitation to disaster ...
>
> That said, given that the API freeze has begun, maybe that you'll be OK. However, you've obviously hit one of the problems that is integral to the way milestone builds work; they show off new features, but at the expense of potential unknown bugs.
>
> I'd say that there's a reasonable chance that a fix will be forthcoming. If you keep the bug tracked (add yourself as a CC) then you'll know when the bug is fixed, and you can chose to use a nightly build that fixes that issue, or at least download the plugin(s) that do.
>
> But the basic problem is one of poor project management, but fortunately learning from mistakes is one of the things that people tend to be good at.
>
> Alex.

Re: Eclipse 3.2 M4 or M5 + Webstart -> Impossible ! [message #63073 is a reply to message #62863]

Wed, 01 March 2006 16:24

Eclipse User

Originally posted by: public.bojerco.REMOVE.com

Osgi.bundles is just a part of the problem and we have them set as
someone suggested in the BUG history report. The additional problem has
to do with a start sequence of the bundles. It seems that for some
reasons registry bundle starts before the preference one. This yields
Nullpointerexception in

org.eclipse.core.internal.runtime.DataArea.assertLocationIni tialized()

because CommonOSGiUtils.getDefault().getInstanceLocation() returns null
as instanceLocationTracker has not been initialized yet. What I am
failing to figure out is why this works when you invoke the same code
through Main() instead of WebstartMain.

Pascal Rapicault wrote:
> Any problem like that should be reported in a bug report.
> However it has already been done and a workaround is detailed in the bug
> report. It consists in setting the osgi.bundles property in the jnlp file.
>
>
> Ivan B wrote:
>>
>> Hello,
>>
>> We are on the critical path of our development and JWS and Eclipse 3.2
>> features are the integral part of our app.
>>
>> Because of this BUG (#128802) and very, very bad timing we are a bit
>> anxious to figure out how can this be resolved. Can anyone provide any
>> hints or insights how can we resolve this issue? Although I believe
>> that this issue might be resolved in 3.2M6 the problem is in that
>> our code freeze is just around that time and we can not afford to
>> wait that long.
>>
>> We need to make decision if we should drop it altogether.
>>
>> Any help would be appreciated.

Re: Eclipse 3.2 M4 or M5 + Webstart -> Impossible ! [message #63083 is a reply to message #63073]

Wed, 01 March 2006 18:27

Eclipse User

Originally posted by: pascal.ibm.canada

CC yourself on the bug. I will fix it for M6.

Ivan B wrote:
> Osgi.bundles is just a part of the problem and we have them set as
> someone suggested in the BUG history report. The additional problem has
> to do with a start sequence of the bundles. It seems that for some
> reasons registry bundle starts before the preference one. This yields
> Nullpointerexception in
>
> org.eclipse.core.internal.runtime.DataArea.assertLocationIni tialized()
>
> because CommonOSGiUtils.getDefault().getInstanceLocation() returns null
> as instanceLocationTracker has not been initialized yet. What I am
> failing to figure out is why this works when you invoke the same code
> through Main() instead of WebstartMain.
>
>
>
> Pascal Rapicault wrote:
>> Any problem like that should be reported in a bug report.
>> However it has already been done and a workaround is detailed in the
>> bug report. It consists in setting the osgi.bundles property in the
>> jnlp file.
>>
>>
>> Ivan B wrote:
>>>
>>> Hello,
>>>
>>> We are on the critical path of our development and JWS and Eclipse
>>> 3.2 features are the integral part of our app.
>>>
>>> Because of this BUG (#128802) and very, very bad timing we are a bit
>>> anxious to figure out how can this be resolved. Can anyone provide
>>> any hints or insights how can we resolve this issue? Although I believe
>>> that this issue might be resolved in 3.2M6 the problem is in that
>>> our code freeze is just around that time and we can not afford to
>>> wait that long.
>>>
>>> We need to make decision if we should drop it altogether.
>>>
>>> Any help would be appreciated.

Re: Eclipse 3.2 M4 or M5 + Webstart -> Impossible ! [message #63095 is a reply to message #62872]

Wed, 01 March 2006 18:36

Eclipse User

Originally posted by: alex_blewitt.yahoo.com

True, sometimes you have to take risks in order to gain a competitive advantage in the market place. And as with any risk, it's a calculated one that may lead to advantages or disadvantages.

At least you made the decision knowing it was a risky strategy :-) I hope it works out for you.

Alex.

Previous Topic:	multiple versions of one bundle
Next Topic:	Problems moving to latest serverside OSGI code

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 17 18:14:51 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter