[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Pre-populating p2 with multiple update sites (was Re: [eclipse.org-planning-council] RE: [cross-project-issues-dev] Heresy mark II (summaries and replies))
|
Bjorn, testing Ganymede assumptions using Europa is like turning on the
radio to watch TV. :P
However, your assumption is partly correct for Eclipse 3.4 w/ p2 as well.
1. Install Eclipse I20080429-0100
2. Unpack EMF 2.4 into dropins/
3. Start Eclipse
4. Help > Software Updates... > Available Software > EMF update site is
already listed. (It's not *NAMED* like it used to be in Eclipse 3.3, but
/modeling/emf/updates/ should be pretty obvious even to the noobiest of
users.)
But will p2 resolve cross-site dependencies like Europa did? Not exactly.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=229679
Nick
Bjorn Freeman-Benson wrote:
I was under the impression that we already did pre-populate with more
than one site. To test my theory, I downloaded the Europa package
"Eclipse IDE for Java Developers" and opened Help > Software Updates >
Find and Install... > Search for new features and, voila!, there are
nine update sites pre-populated.
We could very easily pre-populate with all the project's update sites,
n'est pas? And that would provide a natural additional level of
classification of the features...
I'm sure we could prepopulate more then one site.
--
[end of message]
------------------------------------------------------------------------
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
