Re: [iam-dev] Supporting previous versions of Eclipse

[Abel Muiño <amuino@xxxxxxxxx>]

I think we should be safe not bundling EMF in our features. As for adding the ganymede update site... I'm not sure. Eclipse already bundles the update site for the release, but maybe we could have a RAD Support feature that adds it.

What do you think?

On Tue, Apr 7, 2009 at 7:13 AM, Carlos Sanchez <carlos@xxxxxxxxxx> wrote:

The problem is that we include org.eclipse.emf.databinding in one of
our features, but not the transitive dependencies

We need to find out whether to include the dependencies and all the
transitive dependencies in our update site or just the ones not in
ganymede and make users add the ganymede source, maybe we can add it
when IAM is installed?


2009/3/31 Abel Muiño Vizcaino <amuino@xxxxxxxxx>:

> BTW: I have not been able to reproduce the problem to install in previous eclipse versions... see my response to a user on the newsgroup: http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.iam/msg00200.html
> Maybe the thing is to have the Ganymede update site configured so everything can be fetched from there? I have not experimented on removing all the 3rd party dependencies from our update site/features.
> El 31/03/2009, a las 15:12, Abel Muiño escribió:
>
> That change only affected the target platform, but not the required minimum versions of the bundles/features.
>
> Having a non-current target platform has some inconveniences when generating p2 metadata (in the past, users have reported not being able to install on SR2).
>
> I have read reports that removing the p2 metadata solves some of the issues with the dependencies.
>
> BTW: Doesn't RAD have the Ganymede update site installed? If it is, it should have downloaded the newer emf.ecore from there.
>
> On Tue, Mar 31, 2009 at 2:33 PM, Carlos Sanchez <carlos@xxxxxxxxxxxxxxxx> wrote:
>>
>> I see in rev 20798 that the versions in the target platform were
>> upgraded to 3.4.2 SR2
>>
>> Unfortunately that includes org.eclipse.emf.databinding
>> 1.0.0.v200902171115 also included in our update site
>> that in turn requires org.eclipse.emf.ecore/[2.4.2,3.0.0)
>>
>> unfortunately RAD based in 3.4 (and maybe other older Eclipse
>> versions) has only org.eclipse.emf.ecore_2.4.1.v200807301508 and
>> breaks the update site
>>
>> should the target platform be something more conservative instead of
>> updating to latest? or should we remove all 3rd party libs from the
>> update site?
>> _______________________________________________
>> iam-dev mailing list
>> iam-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/iam-dev
>
>
>
> --
> Abel Muiño - http://ramblingabout.wordpress.com/
>
>
> _______________________________________________
> iam-dev mailing list
> iam-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/iam-dev
>
>
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev

-- 
Abel Muiño - http://ramblingabout.wordpress.com/