Bugzilla – Full Text Bug Listing
| Summary: | RELENG: Please add deeplinking to build | ||
|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Dave Orme <djo> |
| Component: | UI | Assignee: | Paul Webster <pwebster> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | gordon.mcmahon, pwebster |
| Version: | 0.9 | ||
| Target Milestone: | 4.1 M2 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Dave Orme
I've created the releng location in e4/releng/org.eclipse.e4.deeplink.releng and added a maps file with features and plugins. I've added a master feature, and (in theory) the ability to generate the source plugins. I'll be able to run a test build first think tomorrow morning. PW Thanks Paul. I'll try to be on IRC tomorrow AM CDT in case we need to chat to work things out. I noticed that one of the plugins depends on org.apache.commons.lang ... we need a CQ to be able to consume that in e4. PW (In reply to comment #3) > I noticed that one of the plugins depends on org.apache.commons.lang ... we > need a CQ to be able to consume that in e4. Okay; even though that's in Orbit? mmm; okay. Just go to the CQ bugzilla instance and open a new ticket? Thanks Paul. (In reply to comment #4) > Okay; even though that's in Orbit? mmm; okay. Yes, each project needs to open a CQ to reuse them ... but it's "subject to parallel IP process" so it's more about the PMC approving it for re-use in our project. > Just go to the CQ bugzilla instance and open a new ticket? Yes, please. For use in the eclipse.e4 project. PW OK; done. https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4373 On vacation now. :) (In reply to comment #6) > OK; done. Thanx. > > On vacation now. :) :-) I've got a test build created with the deeplink stuff. http://build.eclipse.org/eclipse/e4/build/e4/downloads/drops/4.0.0/I20100725-2015/I20100725-2015/repository There should be a deeplink category + a number of installable features. Everywhere you see 2 features they should be 1) the feature and 2) the matching source feature. You'll probably need to update your sourceFeature/sourcePlugin directories that I've added to your feature. First things first. Can you install your core functionality? With or without the matching source. Then we need to clean up the features as they appear in the category. Should the dependency features be there? Or is it enough that they're in the repo? This will be in tomorrows e4 build, but with only 1 or 2 builds left, we probably will break it out into its own repo and build it after e4/4.0 ships. PW (In reply to comment #8) > This will be in tomorrows e4 build, but with only 1 or 2 builds left, we > probably will break it out into its own repo and build it after e4/4.0 ships. Yes, at this point I think we should just leave it out until after the release wraps up. The deeplinking features should be available at http://download.eclipse.org/e4/updates/0.11-I-builds PW Thanks Paul. Tested/works against 3.6. Haven't integration tested anything yet, from the build, but it's good to be there. In I20100914-1023 PW |