| Summary: | Problems consuming ECF | ||
|---|---|---|---|
| Product: | [RT] ECF | Reporter: | Wim Jongman <wim.jongman> |
| Component: | ecf.releng | Assignee: | ecf.core-inbox <ecf.core-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | slewis |
| Version: | 3.4.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=302243 | ||
| Whiteboard: | |||
|
Description
Wim Jongman
Who does the Target Definition editor >> PDE can we create a repo without the pack.gz files?about [14:36:04] Wim Jongman: It is about our 3.4 repositories but I already filed a bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=331536 [14:39:48] Wim Jongman: can we create a repo without pack.gz plugins? [14:40:38] lemmster: We used to create a repo that contained both packed and unpacked jars. But consumers complained about it. [14:41:00] lemmster: IIRC there exists a bug about it [14:41:48] Wim Jongman: Why did we choose to remove unpack and keep pack and not the other way around? [14:41:59] Wim Jongman: Or better [14:42:31] Wim Jongman: is it possible to create a second repo with unpacked plugins? [14:42:45] Wim Jongman: is it a bucky target or does it involve the build.properties [14:43:19] lemmster: Sure it's possible but it would require running buckminsters site.p2 target twice with different properties switched on. [14:43:57] lemmster: And I don't think this workaround solves the real problem anyway. It just makes it more confusing to consumers which repo to select. [14:43:57] Wim Jongman: the trouble is, our repo cannot be consumed in the target editor [14:44:39] Wim Jongman: Then i would opt for unpacked plugins [14:45:12] lemmster: You sure, http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/commit/?id=c6f06182b8387590c5d74e1437e27229cca4435a is the .target that is dynamically created during build and it uses the packged.gzs [14:46:57] Wim Jongman: i'm not sure what you mean by this link [14:48:45] Wim Jongman: I am now using the ECF 3.3 repo from helios which works [14:50:28] lemmster: So you're saying 3.4 does not work while 3.3 works? [14:50:46] Wim Jongman: yes [14:51:09] Wim Jongman: 3.3 from helios does work. 3.4 from our repo does not work [14:51:32] Wim Jongman: http://download.eclipse.org/rt/ecf/3.4/site.p2 is our eclipse repo [14:51:34] lemmster: by our repo you mean OSU? [14:51:40] Wim Jongman: no the link above [14:52:03] lemmster: The I guess the repo metadata is somehow broken. [14:52:19] lemmster: Unless 3.3 is .jar instead of jar.packed.gz [14:52:48] Wim Jongman: i guess the last because installing it with p2 works just fine [14:53:03] Wim Jongman: only the target def editor has problems [14:53:16] Wim Jongman: could be that bucky can resolve it fine too [14:53:24] lemmster: Well, then it's a target def editor bug. ;) [14:53:48] Wim Jongman: I think so. But getting a fix for that can take ages [14:54:16] Wim Jongman: generating an unpacked repo can be fixed in minutes [14:54:59] lemmster: With all the side effects it has [14:58:53] lemmster: My gut feeling is that creating a second repo is going to cause a lot more work that you expect. [14:59:52] Wim Jongman: if we were not optimistic we would not start anything ;) [15:00:19] Wim Jongman: Maybe i can just repack the zip manually? [15:01:03] lemmster: You will have to tweak the metadata (artifacts/content) too. [15:01:57] Wim Jongman: yes, that sucks. Did we already create an integration build on the new hardware. I cannot find a workspace for the sdk.feature job [15:02:18] lemmster: http://download.ecf-project.org/repo/C-HEAD-sdk.feature/lastSuccessful/archive/site.p2/ [15:03:03] lemmster: https://bugs.eclipse.org/bugs/show_bug.cgi?id=302243 [15:03:52] lemmster: If it helpes we can revert #302243 for the moment. [15:04:23] Wim Jongman: ah, i see. Just make one quick build you mean and then restore it back. [15:04:23] Wim Jongman: ah, i see. Just make one quick build you mean and then restore it back. [15:09:56] lemmster: https://bugs.eclipse.org/bugs/show_bug.cgi?id=304958 I have set site.retain.unpacked=true for the next SDK build. [15:12:14] Wim Jongman: Thanks, I will file a bug against PDE and see what they say. [15:12:29] lemmster: ok |