Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ecf-dev] feature refactoring and older versions of Eclipse

Hi Folks,

Status:

With [1], the Platform has moved over to using the new ECF core+filetransfer features. Here [2] is the 4.4 platform integration build.

I realized this morning, however, that we have the following issue. Currently, we have several api features that require org.eclipse.ecf.core.feature (i.e. org.eclipse.ecf and org.eclipse.ecf.identity). Now that o.e.e.core.feature will be in Eclipse 4.4, there's no problem there.

But of course people will probably try to install ECF 3.8.0 sdk into older versions of Eclipse (e.g. 4.2, 4.3). The o.e.e.core.feature will not be present in Eclipse, and so will try to install org.eclipse.ecf.core.feature from the ECF 3.8.0 repo. I expect this will fail, however, because older versions of Eclipse specify exact versions of the ecf core plugins in the p2 feature that includes them...and so when p2 goes to install the new versions of org.eclipse.ecf and org.eclipse.ecf.identity p2 will probably complain/fail to do this (since the p2 feature specifies a specific version of these bundles).

So...any ideas in how we can most easily support ECF 3.8.0 install into 4.3.X and 4.2.X versions of Eclipse? One answer would be that we ask that people update to 4.4...but that's asking a lot...for some consumers.

Another idea is to remove all the require dependencies on org.eclipse.ecf.core.feature, and replace them with requires of org.eclipse.ecf and org.eclipse.ecf.identity plugins directly. This should work, as there haven't been any changes to org.eclipse.ecf or identity since what went out in 4.2 (I'll check this, of course). This is sort of my favored option right now.

Any other ideas/opinions?

Thanks,

Scott

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=419647#c46
[2] http://download.eclipse.org/eclipse/downloads/drops4/I20140218-0800/



Back to the top