Community
Participate
Working Groups
In the past few dev cycles, we've created our release repository early, and put our milestone builds there, similar to what the Simultaneous Release does. I think we should again, especially since the packages from EPP assumes we do. While testing the Juno M1 EPP Packages, I got a message that said "No repository found at http://download.eclipse.org/webtools/repository/juno." So, I suggest we do create one at ~/downloads/webtools/repository/juno Normally, we'd just incrementally add each webtools milestone there, unless we found a reason not to, where we might have to remove old ones (for example, if we ever remove a feature, or if a version mistakenly goes "down", then we are often stuck with removing the old ones. (Well .. unless anyone wanted to rebuild, some how). Conceptually, these repos are pretty easy to create, since it is just a few xml files that "point to" the "real" repository that is already part of our released milestone. The trick is just getting the right URls. After that, it is all indirection. No code has to be moved or re-precessed. The first time you do it, you may want to try just creating the files "manually" base of examples from last year ... in the indigo courter part, Later, or when ever, you can use some semi-automatic scripts to add repos and remove repos to these composites. A collection of miscellaneous one is in /releng.wtpbuilder/manualStepScripts/antrunner .. the files in that antnunner in cvs are not the same as ones on the files system ... I would synch them up occasionally ... but mostly just worked under the apps/antrunner directory to "create a repo" and similar. Its not all that much less work doing it with the scripts, but they do help avoid typos, and ideally someone will improve the scripts, so much more automated.
Adding Kaloyan to CC since he did the work for Libra last year. Want to take the reins, Kaloyan? Set up the initial versions? (I'm just suggesting since you have had some experience with it, so maybe you could show Carl what you know? I'd be glad to help if you have questions with no easy to find question. And, of course, you'll want to "test your work" once done to make sure it all workd, and that (basically) the same WTP content would result no matter what repo was used. (Juno or WTP).
It would be good to get this finished before Friday Morning, since that's when the packages would be delivered, and users start to see the error. (And, while "we" know there is not much strong it makes it look bad for casual users to get such confusing messages ... certainly sounds like something missing.
Yes, it something I've already partially did for Indigo. I've given it a try - I've copied the makeComposite.xml in my user folder, edited it and run it with Ant. David, could you check the result. Currently, I don't have write permission in the /shared/webtools folder. If I want to take advantage of the wisdom collected there for the long-term, it would be helpful that I am granted with such permission.
Better late than never, I just tried the Juno update site, and I can verify that I am able to get the WTP 3.4.0 M1 content installed on an Eclipse 3.8 M1 that already has all of our prereqs installed. Thanks Kaloyan for doing this. (Note: I did not try Libra.)
This was open for M1 ... and that was fixed. I assume will be for updated for M2. Thanks all.
