Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Callisto staging Update Site ready for testing ... sort of

Oh, O.K. I was just looking for a way to reduce my workload. Since the CDT never ends up being forwards compatible with new Eclipse platform releases, I need to make a new update site for each one anyway. I was just going to use the Callisto site for that.

 

One thing I’ve learned through this exercise is that this stuff technically isn’t rocket science at all, especially if you copy the jar files into the plugin/features directories with the site.xml, i.e. no need to list your archives. I don’t see any reason why we couldn’t keep this going to include updates/fixes, etc. We’d just have to make sure we don’t klobber eachother updating the site.xml, maybe keep it in CVS somewhere. Of course, I’m often guilty of over simplifying things and ignoring things like scalability J

 

Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead, http://cdtdoug.blogspot.com

 


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Tuesday, March 07, 2006 11:20 AM
To: Cross project issues
Subject: RE: [cross-project-issues-dev] Callisto staging Update Site ready for testing ... sort of

 


Thanks Doug.

But, please do not plan on using Callisto as your only update site,

I'd like to emphasize that projects are (still) responsible for having their own
update sites -- and Callisto should be viewed as a common Discovery Site.  
Each project  should still "implant" your own projects update URL in your features.xml ... as your CDT one currently does.

   <url>
      <update label="%updateSiteName" url="">
   </url>

This is, mostly, to have a place to put your updates (fixes) ... there is no commitment to use Callisto in the future for fix updates.
But, also, many projects may have "extra" stuff at their own update sites (sdks, examples, unit tests, etc) that may never be on Callisto.
Also, sometimes, a projects own update/discovery site might have a different organization or set of categories than Callisto.
(for an example, see http://download.eclipse.org/webtools/milestones/   from update manager)

I realize CDT might not currently ... but ... still, I do not think Callisto was intended to replace the project sites.
(I know it seems redundant, but that's actually only temporary, and due to update and mirror limitations ... long term, there will only be
project physical sites .. with a common "pointer" site).

Lastly, as a tip to all ... don't forget to include "sister projects" in your own features.xml discovery sites.
For example, in one of our webtools features, we include BIRT and TPTP, since they are our buddies :)
(and, really, there are some use cases were they all work better together!)

   <url>
      <update label="Web Tools Platform (WTP) Updates" url="">
      <discovery label="Web Tools Platform (WTP) Updates" url="">
      <discovery label="Business Intelligence and Reporting Tools (BIRT) Updates" url="">
      <discovery label="Test and Performance Tools Platform (TPTP) Updates" url="">
   </url>

This way, if someone installs "only" webtools they will be more likely to discover new and wonderful things if the go to the update manager dialog again.






Doug Schaefer <DSchaefer@xxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/07/2006 09:09 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [cross-project-issues-dev] Callisto staging Update Site ready        for testing ... sort of

 

 

 




Oops, sorry David, I missed that line in your e-mail. Trying things out, I do have write access to the staging area. I didn’t change anything though J.
 
For the CDT, I will likely use the Callisto site as my only update site, thus my need for write access. I don’t see the point in having the CDT bits in two locations (and makes it harder to collect download stats). I may have my own site.xml file just to make it easier to find the CDT features.
 
Great work David, thanks for this!
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
 

 



From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent:
Tuesday, March 07, 2006 12:31 AM
To:
Cross project issues
Subject:
RE: [cross-project-issues-dev] Callisto staging Update Site ready for testing ... sort of

 

Wouldn't hurt my feelings! As I said in the note that started all this ...


I have (tried) go give all committers write access to that staging directory ... so, if any of you can fix any of the above problems,
(e.g. if I just missed a copy of some jar) ... then feel free ... but, please, keep us all informed by a post here.


But, I'll admit, I'm not much of a "sys admin" .. so, if some one is being held up due to permissions, let me know and I'll try again (or, ask someone who knows :)



But, the hold up for EMFT I do not think is purely technical ... call me a stick in the mud if you want ... but ... EMFT is not mentioned in
http://www.eclipse.org/projects/callisto.php

So, I would expect the Planning Counsel to say yeh or nay ... or .... at least the owner of that document ... Bjorn ... to comment

"yes, that was the intent, document will be updated".
(Am I reading too much in to that document?  ... I was not privy to the actual council meetings where this list was determined).


But I do think it is instructive, somehow, that it not being on Callisto is holding you up from trying it out. It and its pre-reqs are, presumably

available from some project update sites .... just need the book marks .... maybe the Technology PMC needs its own "whole of Technology Update Site" to make
trying things out easier? There's a ton of stuff in there to try out!




Doug Schaefer <DSchaefer@xxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/06/2006 04:42 PM

 

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

 

To

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [cross-project-issues-dev] Callisto staging Update Site ready        fortesting ... sort of


 

 

 

 





Is there an ETA on this? I think it is the last piece preventing me from trying to download all of Callisto. And I want to try out GMF
J.
 
I’m wondering if it would be an idea that doesn’t hurt anyone’s feelings to give more people write access to the Callisto directories on dev.eclipse.org. I’m sure if someone was free they could have copied these over in a matter of minutes…

 
Thanks,

Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead,
http://cdtdoug.blogspot.com
 


 




From:
cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Richard Gronback
Sent:
Monday, March 06, 2006 6:04 AM
To:
Cross project issues
Subject:
RE: [cross-project-issues-dev] Callisto staging Update Site ready fortesting ... sort of

 
Hi,

 
GMF depends on EMFT OCL, Query, Validation, and Transaction components (M5a of each), which can be gotten from here:
http://download.eclipse.org/technology/emft/updates/site-interim.xml
 
The EMFT team should have representation on this list and be on board with Callisto (officially).  I thought they were, anyway.

 
Best,

Rich

 


 




From:
cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent:
Monday, March 06, 2006 1:55 AM
To:
Cross project issues
Subject:
[cross-project-issues-dev] Callisto staging Update Site ready fortesting ... sort of

 

The good news: there is an update site to point to


http://download.eclipse.org/callisto/staging/


I personally install (test) starting with only a minimum "Platform Runtime Binary" (30 meg zip).
Then you have to "manuall" define the remote update site using the URL of
http://download.eclipse.org/callisto/staging/



But, bad news is, either I've gotten mixed up on some EMF M5 versions, or ... that was so long ago for them :)  they've deleted some of the jars already!?
(If the latter, perhaps we haven't been clear, or perhaps we all have all not agreed, that the project supplied update sites need to "stick around" .... just like their zipped milestone downloads would).

So, for that, I've create bug
130505  M5 Update pre-reqs seem gone?

https://bugs.eclipse.org/bugs/show_bug.cgi?id=130505


But, if you just install EMF from somewhere else, you can make more progress and run into more interesing problems.

the most interesting is

130497 Callisto update site says "can't find jdt.apt" while installing CDT

https://bugs.eclipse.org/bugs/show_bug.cgi?id=130497

(A packaging issue? Or a new JRE version issue?)


Next most interesting


130502  no capabiliites if just "runtimes" installed

https://bugs.eclipse.org/bugs/show_bug.cgi?id=130502



And, least interesting ...

130506 gmf update needs org.eclipse.emf.ocl_1.0.0.jar

https://bugs.eclipse.org/bugs/show_bug.cgi?id=130506


Well, this latter may indicate a planning hole in the Technolodgy Project Chain of Callisto ... which, I guess
some would find the MOST interesting!



I'm sure there's many many more waiting for you to find.

I have (tried) go give all committers write access to that staging directory ... so, if any of you can fix any of the above problems,
(e.g. if I just missed a copy of some jar) ... then feel free ... but, please, keep us all informed by a post here.

We'll improve write/update process as we go.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top