|
|
| Re: Using ECF with Eclipse 3.2 codebase [message #624852 is a reply to message #624781] |
Thu, 23 April 2009 11:10   |
 Roland Tepp
Messages: 336
Registered: July 2009 |
Senior Member |
|
|
Thanks for answer.
I found already out that it is not entirely impossible to make 2.1
branch of ECF discovery to compile under 3.2.2 target platform.
However, As it involved slightly modifying source code (downgrading one
Import-Package version and adding error code bit to one Status
construction call), it made me slightly uneasy to work on a fork of the
"official" release (today, it is one or two small changes, but who knows
what follows)
Also I concluded same - that although the code compiles, it does not
necessarily mean, it will work, as there might be some subtle
assumptions about runtime environment that I could not possibly validate
without an extensive testing, for which I really do not have enough
resources.
So I chose the path of least resistence and googled for an alternative
implementation, at which point I stumbled upon the same JmDNS library
that is internally used in ECF (is it now forked somehow or do they get
developed in tandem?).
18.04.2009 3:24, Scott Lewis kirjutas:
> Hi Roland,
>
> Roland Tepp wrote:
>> Hello,
>>
>> Our company is currently developing and RCP app that is based on the
>> Eclipse 3.2.2 codebase and we want to use ECF service discovery api in
>> our application.
>>
>> However, I could not find any links to ecf builds for ECF equivalent
>> to Eclipse 3.2.2.
>>
>> So I am interested if I can use the latest ECF (non-ui) libraries in
>> the context of Eclipse 3.2.2 based RCP application?
>
> For discovery this is indeed possible...as the EE requirements for
> discovery and ECF core are minimal (CDC 1.1/Foundation 1.1). But we have
> not tested this and it's very possible that just Equinox and OSGi have
> migrated enough to make it impossible to run the core and discovery
> bundles on such an old version of the runtime.
>
> So although it's possible that things will run ok, we haven't been
> testing it, and so it may not be possible.
>
> If you do test it and find out one way or another it would be
> appreciated if you would report the results here.
>
> Thanks.
>
> Scott
|
|
|
| Re: Using ECF with Eclipse 3.2 codebase [message #624854 is a reply to message #624852] |
Thu, 23 April 2009 18:06 |
Scott Lewis
Messages: 1038
Registered: July 2009 |
Senior Member |
|
|
Hi Roland,
Roland Tepp wrote:
> Thanks for answer.
>
> I found already out that it is not entirely impossible to make 2.1
> branch of ECF discovery to compile under 3.2.2 target platform.
>
> However, As it involved slightly modifying source code (downgrading one
> Import-Package version and adding error code bit to one Status
> construction call), it made me slightly uneasy to work on a fork of the
> "official" release (today, it is one or two small changes, but who knows
> what follows)
>
> Also I concluded same - that although the code compiles, it does not
> necessarily mean, it will work, as there might be some subtle
> assumptions about runtime environment that I could not possibly validate
> without an extensive testing, for which I really do not have enough
> resources.
Yes. This is true...and the resource situation is the same for us (as
we are trying to get the final additions/changes in place for
Galileo/ECF 3.0).
>
> So I chose the path of least resistence and googled for an alternative
> implementation, at which point I stumbled upon the same JmDNS library
> that is internally used in ECF (is it now forked somehow or do they get
> developed in tandem?).
I (Scott) am a JmDNS committer...and the situation with JmDNS is this:
We (mostly Markus Kuppe...but me as well) have, through usage and
testing, found a number of problems in JmDNS over the past year and
subsequently fixed them in our local copy. Some of these fixes have
been applied to the sourceforge JmDNS, but a couple of the recent ones
(last few months) have not...only because we haven't yet done so. It's
our intention and desire to contribute back to JmDNS all
fixes/workarounds we find necessary. To the extent we can control it,
we will not fork JmDNS.
AFAIK, there is not a lot of direct work happening with JmDNS at
Sourceforge at the moment...I mean other than what we (ECF) are doing.
Rick Blair is the current JmDNS project lead committer.
Thanks,
Scott
>
>
> 18.04.2009 3:24, Scott Lewis kirjutas:
>> Hi Roland,
>>
>> Roland Tepp wrote:
>>> Hello,
>>>
>>> Our company is currently developing and RCP app that is based on the
>>> Eclipse 3.2.2 codebase and we want to use ECF service discovery api in
>>> our application.
>>>
>>> However, I could not find any links to ecf builds for ECF equivalent
>>> to Eclipse 3.2.2.
>>>
>>> So I am interested if I can use the latest ECF (non-ui) libraries in
>>> the context of Eclipse 3.2.2 based RCP application?
>>
>> For discovery this is indeed possible...as the EE requirements for
>> discovery and ECF core are minimal (CDC 1.1/Foundation 1.1). But we have
>> not tested this and it's very possible that just Equinox and OSGi have
>> migrated enough to make it impossible to run the core and discovery
>> bundles on such an old version of the runtime.
>>
>> So although it's possible that things will run ok, we haven't been
>> testing it, and so it may not be possible.
>>
>> If you do test it and find out one way or another it would be
>> appreciated if you would report the results here.
>>
>> Thanks.
>>
>> Scott
>
|
|
|
Powered by
FUDForum. Page generated in 0.03155 seconds
] 
Search
Help
Register
Login
Home
