|
| Re: API Changes in Buckminster [message #385768 is a reply to message #385766] |
Fri, 29 May 2009 21:18   |
|
Hi Abel,
There has been a lot of changes in Buckminster between 3.4 and 3.5. Mostly due to our efforts to integrate well with P2.
We have significant changes in everything that pertains to versions since we now are using the P2 Omni Version instead.
See: http://wiki.eclipse.org/Equinox/p2/Omni_Version
We are tightly integrated with various parts of the Eclipse platform so there is no path where you can upgrade to our
new API's while retaining 3.4 platform API's.
Regards,
Thomas Hallgren
Abel Muio Vizcaino wrote:
> Hello,
>
> I have started reviewing the compliance of Eclipse IAM with the next
> version of Buckminster and noticed two issues.
>
> With: org.eclipse.buckminster.core_1.1.340.r09948.jar, we use
> - MaterializationJob.run(MaterializationContext, boolean)
> - IVersionType.STRING
>
> With: org.eclipse.buckminster.core_1.1.350.r10327.jar these have changed
> to:
> - MaterializationJob.run(MaterializationContext) // drops boolean arg.
> - VersionType.STRING // switches from interface to class
>
> We have not following changes in Buckminster, so these might be old
> changes already.
>
> My question is: should we upgrade to new API? I guess we should, but I
> have noticed that the new versions also depend on the 3.5.x versions of
> eclipse core packages, so upgrading would mean breaking compatibility
> for our users.
>
> Thanks!
> --
> Abel Muiño
|
|
|
| Re: API Changes in Buckminster [message #385769 is a reply to message #385768] |
Fri, 29 May 2009 21:27 |
 Abel Mui
Messages: 247
Registered: July 2009 |
Senior Member |
|
|
Thanks Thomas,
Can you confirm that the changes in the first email are enough to make
our existing code work with latest version?
That is:
a) MaterializationJob.run(MaterializationContext, boolean) -> Remove
boolean argument
b) IVersionType.STRING -> Use VersionType.STRING
Thomas Hallgren wrote:
> Hi Abel,
> There has been a lot of changes in Buckminster between 3.4 and 3.5.
> Mostly due to our efforts to integrate well with P2. We have significant
> changes in everything that pertains to versions since we now are using
> the P2 Omni Version instead. See:
> http://wiki.eclipse.org/Equinox/p2/Omni_Version
>
> We are tightly integrated with various parts of the Eclipse platform so
> there is no path where you can upgrade to our new API's while retaining
> 3.4 platform API's.
>
> Regards,
> Thomas Hallgren
>
> Abel Muio Vizcaino wrote:
>> Hello,
>>
>> I have started reviewing the compliance of Eclipse IAM with the next
>> version of Buckminster and noticed two issues.
>>
>> With: org.eclipse.buckminster.core_1.1.340.r09948.jar, we use
>> - MaterializationJob.run(MaterializationContext, boolean)
>> - IVersionType.STRING
>>
>> With: org.eclipse.buckminster.core_1.1.350.r10327.jar these have
>> changed to:
>> - MaterializationJob.run(MaterializationContext) // drops boolean arg.
>> - VersionType.STRING // switches from interface to class
>>
>> We have not following changes in Buckminster, so these might be old
>> changes already.
>>
>> My question is: should we upgrade to new API? I guess we should, but I
>> have noticed that the new versions also depend on the 3.5.x versions
>> of eclipse core packages, so upgrading would mean breaking
>> compatibility for our users.
>>
>> Thanks!
>> --
>> Abel Muiño
>
|
|
|
Powered by
FUDForum. Page generated in 0.02973 seconds
] 
Search
Help
Register
Login
Home
