Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Talk:Callisto Coordinated Update Sites

Talk Page started by Kim Moir (platform-releng) :-)

I've done a bit of editing to try and keep this page organized, and show what's been resolved and what still needs some active work. If anyone ever see's I've edited too much, please say so, as I'm sure it was unintentional. Eventually we may want to move "resolved and stale" issue to some separate history page and some of the "news" topics may deserve a page of their own, eventually. And ... by all means ... all committers to Callisto should feel free to contribute to these pages by organizing the content, or provide links out to other pages, etc. The end goal is to end up with a great "main" page that everyone finds accurate and a useful reference.

-- David williams 21:49, 11 February 2006 (EST)

Page talks tips

I believe the little "+" symbol next to the edit button at top should be used for these talks. --Denis Roy 16:50, 6 February 2006 (EST)

Which will add a new level 2 section at bottom of page.

Responses to page talk sections

I think it also seems to work fairly well to add a level 3 section to "respond to" a level 2 section. I do not know if there's an easy short cut for that, I've just been doing it "manually". (with 3 equal sign's (title) 3 equal signs)

-- David williams 21:49, 11 February 2006 (EST)

author date and time

And, if you don't know if yet, 4 tildes in a row automatically gets converted to your name, and the current date and time, for easy marking of who and when. I guess the bracket(initials-username)end-bracket just shows how out of date we are with this fancy new Wiki stuff :)

-- David williams 21:49, 11 February 2006 (EST)

using del to strike out old stuff

We can also use the del tag to strikeout some stuff that we want to keep, but is no longer relevant because it's been resolved

--Denis Roy 10:37, 25 February 2006 (EST)

URL's for Callisto updates

[kmoir] There is a problem with the url

Currently, the platform team stores all its updates in this directory

and subdirectories such as these

So I don't know that this is the best url for Callisto

given that

  • we already have platform content in that directory
  • we can't change the Apache alias for platform because this has been hardcoded in our feature.xmls
  • the unix permissions on the directory mean that the platform team would need to retain ownership in order to continue update the content in the existing update sites.
  • [dmw: agreed, we should have 'callisto' first in the URL, and keep it "parallel" other Eclipse projects]

    [denis: I can't host this on How about]

    [nickb] How about: (in the same folder as site.xml) ? [dmw] I think we're leaning toward, but wanted to comment on the comment ... I think we should avoid having version numbers in (any) directory ... isn't the long term goal to have a constant update site for all time, and just keep putting new plugins and features in there, as needed, so to speak? ... and, hopefully, there may start to be more and more that don't actually change, say from 3.2 to 3.3?]

    [kmoir]Until the code to resolve this bug is implemented, we can't ensure that we can just reuse the same update site from release to release.

    Resolved: URL's for Callisto updates

    These issues have been resolved as best they can, and the main page updated to reflect the update URL's for Callisto will be

    -- David williams 21:49, 11 February 2006 (EST)

    And now already changed so the "top level" one will be

    to avoid having other directories permenanently underneath the main update site directory. They should be siblings for easier management and future flexibility.

    -- David williams 00:43, 17 February 2006 (EST)

    How all-or-nothing and few-or-many-choices should Callisto be

    [kmoir] Providing Callisto as a single download comprising all 10 projects provides better exposure to the newer projects. By the same token, it also forces people to download stuff that they may not necessarily want or ever use, thus significantly increasing the strain on the distribution infrastructure. It is also rather overwhelming for a new eclipse user. My point is, perhaps there is a better way to educate users and provide choice while simultaneously exposing the full breadth of functionality available with Callisto.

    [dmw: yep, this is the question to be answered empirically and via community feedback ... but if we get one packaging working ... a few others should be easy --- though, I'd never want to get to the point of a Callisto user having more than, say, 4 or 5 choices ... those users that want more fine grained control than that will have to use project update URLs]

    [nickb] I agree that making people download EVERYTHING is both overkill and will overtax the infrastructure. However, as David points out, "enabling" projects like EMF and GEF are required for the more newb-friendly projects, so could we have a set of screenshots just showing people how to use UM and the various requirements they need to check off in order to get the projects they want? I like what WTP has done for their UM site, for example.

    Resolved: we'll start with the "completely selectable" approach

    Since its easier, and allows better incremental approach to the end goal (e.g. there could be one failing or delayed feature, without preventing other updates). As before, we'll assess as we go, and remain open to future enhancements.

    -- David williams 00:48, 17 February 2006 (EST)

    Tool to track downloads

    By the way, I've got a working tool for tracking download stats for EMF & UML2 (and other projects who want to implement it), which combines

    • a PHP script for running SQL queries at the download stats database,
    • a shell script to automatically run the PHP to convert SQL into XML, run every night/week/month, and
    • a web UI ( to display those results for trending and analysis

    For more on this, see

    --Nick Boldt 21:40, 3 March 2006 (EST)

    Responses: Tool to track downloads

    Nick, thanks. First, your tool does sound very interesting ... I personally won't have time to investigate it much for a while, but I'd think we'd want these sorts of stats for all Eclipse projects, especially those in Callisto!

    Sizes involved with Callisto

    Since several have voiced concerned over size of Callisto, I guess we should start to estimate its size.

    Here's my off hand estimates of "runtime" sizes of several components (in MegaBytes). These are mostly guesses at this point (but a few I'm "updated" recently), but if enough people provide estimate, we'll get a little better idea of what tradeoffs are.

    [Callisto meisters: feel free to update your portions of table to be accurate ... using current milestones, or previous release milestones as estimates. Any rough estimate will do.]

    [nickb] You can get numbers for your most recent builds like this:

    • ssh
    • cd /home/data/httpd/
    • find . -name "*.zip" -exec du -sh {} \;


    If we literally included each (sub) project as a choice, that would be 15 choices ... which I think is too many for what I've thought Callisto was for. Perhaps someone could propose some concrete "groupings" that would satisfy majority of users (though, I'm pessimistic if we could reach much agreement?)

    If we go that route, though, I don't think we would need to do anything, except maybe to get the platform plugin to provide all 10 "discovery sites"?

    Also, maybe our friendly webmaster could comment on if these "increases in size" are of the size to be of concern .... such as is 75 Megs, say, that much different than 150? Is 150 that much different that 300? (I know "twice as big" sounds like a lot ... but .. its not like 10 times as much). And with our improved "nearest mirror" support, maybe it wouldn't matter?).

    [denis: also consider that the bigger it is, the longer it will take to reach all our mirrors. The good news is that Mike okay'd an extra 200Mb (!!) of bandwidth for (but not limited to) Callisto, in addition to and separate of the 100Mb for, so we'll be in good shape for actual distribution.]

    Project Runtime Size SDK Size
    Business Intelligence and Reporting Tools (BIRT) 3 ?
    C/C++ IDE (CDT) 10 ?
    Data Tools Platform (DTP) 6 ?
    Eclipse Modeling Framework (EMF, SDO, XSD) EMF/SDO: 3.4, XSD: 1 EMF/SDO/XSD: 23
    Eclipse Project (Platform only) 15 ?
    Eclipse Project (PDE, JDT) 60 ?
    Graphical Editing Framework (GEF) 3 ?
    Graphical Modeling Framework (GMF) 6 ?
    Test and Performance Tools Platform (TPTP) 10 ?
    Visual Editor (VE, JEM) 5 ?
    Web Tools Platform (WTP, WST, JST) 25 45
    Totals 150 300

    Concurrent Builds & Releases

    Release Train Cascade / RSS Notification & Response

    [nickb] There's been a fair amount of discussion about getting the Callisto projects to align in terms of their releases (before the subject of UM was broached). Should this be a page by itself, rather than a footnote here, by all means please do. The link above shows what's been done so far in terms of building a build cascade automation scheme, along with some comments from the community. Please post comments about this plan into that bug so that I can integrate your requests into it, in order to make this solution more portable across all Callisto projects.

    Responses to: Concurrent Builds & Releases

    Yes, I'd agree the information in the above referenced bug report would make a good a Wiki page that spelled out the "how to" information ... step by step directions, links to example scripts, etc. I myself am not too concerned about cascaded builds, per se (we do "continuous builds", which would sort of lead to a combinatorial explosion if we and everyone followed it literally. Also, I haven't checked recently, but that discussion did not seem to address "cascading updates" ... which would be nice for developers (and by this I mean notifications of some new "weekly" update being available. That way, developers could perhaps automatically update their targets, with minimal effort.

    Just agreeing (I'm not volunteering :).

    -- David Williams 19:57, 11 February 2006 (EST)


    True, we haven't addressed cascading updates (in terms of RSS and cron scripts, anyway), but if all the projects publish builds & UM jars at the same time (like EMF, UML2 and EMFT does), then this UM cascade could happen automatically - or at least would be available for those who want to take advantage. I'm all for putting it out there, publishing where it is, making it easy to get it, and letting whoever wants it to get it, either via download page, RSS (link to download page or directly to build 's URL), or UM site.

    -- Nick Boldt 11:56, 24 February 2006 (EST)

    Cross project requirements - best practices

    [kmoir] On the same note, I couldn't find a document that gathered best practices for projects participating in Callisto

    For instance, from the platform Using qualifiers Using jarred plugins and features
    signing jars ....etc.

    Responses to: Cross project requirements - best practices

    Thanks Kim, I've adding the plugins-as-jars link to the main page's Callisto_Coordinated_Update_Sites#Related_Links_for_Further_Enjoyable_Reading_and_Reference
    Thanks for pointing it out. (In general, all Callisto Committers should free to add references or annotations to Callisto_Coordinated_Update_Sites#Related_Links_for_Further_Enjoyable_Reading_and_Reference)

    The versioning document was already linked there.

    I didn't actually see much info in the jars document about "how to" sign plugins-as-jars. Has that effort or information moved further along?

    And, by all means, I'm sure the community would use any "best practices" Wiki pages. If real general, beyond Callisto, I suggest you add pointers to them on Development_Conventions_and_Guidelines. For example, there you will find a link to a kind-of-out-of-date User_Interface_Guidelines which we in Callisto should also pay attention to.

    -- David Williams 20:13, 11 February 2006 (EST)

    [kmoir] 11:01, 24 February 2006 (EST)

    There is a process to sign jars but it is not complete yet...releng, equinox/runtime team and foundation are working on it.

    Default download should be binary not SDK

    The SDK is too big. This is bad because: a) most people don't need all of that stuff, b) it wastes bandwidth, and c) it makes us look bad compared to other products. Thus I recommend that the default set of features be the Platform runtime binary plus the JDT runtime binary. The key part here being "binary". So no source, no PDE, no doc on how to develop plug-ins, just user doc.

    Furthermore I recommend that the default for all other features like WTP also be "binary". The source / developer stuff should be in its own feature, listed on the update site, easy to download, but just not the default. We need to make Eclipse/Callisto look "lean and mean" not "huge and ungainly". --Ebb 10:13, 24 February 2006 (EST)

    Back to the top