Bugzilla – Full Text Bug Listing
| Summary: | Local update site not available for EDT | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | FVSWRK |
| Component: | EDT | Assignee: | Theresa Ramsey <tdramsey> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | hoffmanp, mheitz |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
FVSWRK
I'm creating a local update site zip for M3. I'll update this bug when it's ready, so Theresa can link to it on the web site. I don't think we should create a zip like this for every build. Doesn't seem like a good use of disk space. Theresa, the file is at http://download.eclipse.org/edt/updates/0.7.0/M3/localUpdateSite.zip Installation instructions: 1. Download the file and unzip it to a temporary directory. 2. In Eclipse, choose Install New Software... from the Help menu. 3. Click the Add... button. 4. Click the Local button and choose the temporary directory. 5. Click OK on both dialog boxes to close them. 6. Select the EDT features, click Next, and Next again. 7. Accept the license agreements and click Finish. thanks matt. can we rename the zip to something more edt related? edt07m3? Yes I can rename it, but the version and milestone are already in the path. You still want me to rename it? Correction to the URL in comment 2. People should get the file from http://eclipse.org/downloads/download.php?file=/edt/updates/0.7.0/M3/localUpdateSite.zip Why not put out the nightly build as part of the regular nightly build process? If space is the only issue, don't keep previous builds, just replace them. Paul, disk space isn't the only issue. Another is that I don't know how hard it would be to automate the process of making the local update site. I'm not going to do it by hand every time. My main objection is that I'm not sure about the utility. Nightly builds are really only meant for the developers writing EDT. They're already using the code directly from CVS. (In reply to comment #4) > Yes I can rename it, but the version and milestone are already in the path. > You still want me to rename it? (Sorry thought I had replied but something must have gone wrong) Y :-) I noticed several projects that use a more useful name over a generic one. Helpful if you Also, can you just use the archive/zip (vs having to unzip it)? You can point to an Archive in the Install New Software, Add dialog. > can we rename the zip to something more edt related? edt07m3? OK, the URL will be http://eclipse.org/downloads/download.php?file=/edt/updates/0.7.0/M3/edt07m3.zip > Also, can you just use the archive/zip (vs having to unzip it)? You can point > to an Archive in the Install New Software, Add dialog. I think that will work, but I haven't actually tried it. I wrote my instructions after reading instructions for a installing local update sites of a couple other projects, and they never mentioned the Archive option. I bet Archive is a new-ish choice and people haven't gone back to update their docs. I assume this worked since we haven't heard any complaints. Do we want a local update site for the 0.7 release? If so let's keep this open to track that work. If not then this bug should be resolved. Process releasing milestone or version builds needs to include creation of a local build as standard operating procedure. Once the process is in place the issue can be marked as resolved. Resolving this old bug. We make local update sites for all milestone and release builds. closing....local zips should be get-able from the browser pointing to update url |