| Summary: | change Mylyn repo locations in JEE, Javascript, Java package | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | Markus Knauer <mknauer> | ||||
| Component: | Packager | Assignee: | Markus Knauer <mknauer> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | david_williams, mknauer, steffen.pingel | ||||
| Version: | 1.3.0 | ||||||
| Target Milestone: | 1.3.0 RC4 | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Markus Knauer
Created attachment 171441 [details]
p2.inf Mylyn repo touchpoint instructions
I've applied this patch to CVS HEAD.
It changes the Mylyn p2 repositories that are activated in the JEE, Java, Javascript packages.
Note that I am not sure what happens if someone updates from RC3 to RC4. I assume that the unconfigure/configure work and that the old p2 repositories are unconfigured before the new ones are added, but I haven't tested this.
Thanks! I'll verify when the next package build is available. (In reply to comment #2) > Thanks! I'll verify when the next package build is available. There is a build running: http://build.eclipse.org/technology/epp/epp_build/36/download/20100608-1800/ I have verified that the expected update site is displayed in the latest Java package and that update site are properly migrated when updating the package from an older build. (In reply to comment #4) > I have verified that the expected update site is displayed in the latest Java > package and that update site are properly migrated when updating the package > from an older build. I've tested this myself and I was impressed that even the migration did work - okay, it was defined so from the beginning, but I've never tested it before. Closing as FIXED. |