Bugzilla – Full Text Bug Listing
| Summary: | [RAP] Can't define target platform in Indigo | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Miles Parker <milesparker> |
| Component: | Releng | Assignee: | Michal Ruzicka <michal.ruza> |
| Status: | RESOLVED WONTFIX | QA Contact: | Kenn Hussey <Kenn.Hussey> |
| Severity: | normal | ||
| Priority: | P3 | CC: | Ed.Merks, michal.ruza |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
| Bug Depends on: | 333588 | ||
| Bug Blocks: | |||
|
Description
Miles Parker
OK, I git upon the magic combination of features. It seems to be: EMF Base Framework EMF Core Framework EMF Common EMF RAP Runtime EMF RAP Target Components RAP Target Components I'm guessing that some subset of these is actually needed. So there is a work around but the basic packaging/doc issue remains. Kenn, I was pretty sure we're building the EMF RAP feature, including its SDK, and that it's all available in our usual update site as well as Indigo. If not, that needs some attention. (In reply to comment #2) > Kenn, > > I was pretty sure we're building the EMF RAP feature, including its SDK, and > that it's all available in our usual update site as well as Indigo. If not, > that needs some attention. Yes, the RAP features are there. The only difference is now the base Ecore (and common) features are part of the "base" build and located in a different (sub)repository. However, selecting "EMF RAP Target Components" and letting it pick up the required dependencies should work... (In reply to comment #3) > The only difference is now the base Ecore (and > common) features are part of the "base" build and located in a different > (sub)repository. However, selecting "EMF RAP Target Components" and letting it > pick up the required dependencies should work... I'm afraid this is caused by the new build structure in that the dependencies on the artifacts produced by the base build don't don't specify strict version ranges any more. (They used to be _included_ in the respective features, but now they are only _required_, that is why the change in the depnedency version ranges.) The consequence is that these artifacts are not picked up by the target platform provisioning algorithm any longer. Adding the: EMF Base Framework feature to the target platform explicitly should resolve the issue. (In reply to comment #4) > I'm afraid this is caused by the new build structure in that the dependencies > on the artifacts produced by the base build don't don't specify strict version > ranges any more. (They used to be _included_ in the respective features, but > now they are only _required_, that is why the change in the depnedency version > ranges.) > The consequence is that these artifacts are not picked up by the target > platform provisioning algorithm any longer. > > Adding the: > EMF Base Framework > feature to the target platform explicitly should resolve the issue. Yeah, exactly. I know it won't build with the two Runtime features. So the current workaround then is to add: RAP Target Components EMF RAP Target Components EMF Base Framework (In reply to comment #5) > Yeah, exactly. I know it won't build with the two Runtime features. So the > current workaround then is to add: > > RAP Target Components > EMF RAP Target Components > EMF Base Framework I've updated the wiki page to note that, as of the Indigo release, the base feature must also be installed. I tried with the three above and it actually looks like you need more than that..otherwise I got a bunch of errors at Runtime and the app didn't work. This is what I was able to get work.. EMF Base Runtime EMF RAP Common UI EMF RAP Edit UI EMF RAP Runtime EMF RAP Target Components Again, probably all not necessary but it does look as though there is an issue with the provisioning/build of features. Note that I have "Include Required Software" unchecked. (In reply to comment #7) > I tried with the three above and it actually looks like you need more than > that..otherwise I got a bunch of errors at Runtime and the app didn't work. > This is what I was able to get work.. > > EMF Base Runtime > EMF RAP Common UI > EMF RAP Edit UI > EMF RAP Runtime > EMF RAP Target Components Hmm, that doesn't seem quite right. The EMF RAP Target Components feature is supposed to include the other EMF RAP features... Michal, can you look into that? > > Again, probably all not necessary but it does look as though there is an issue > with the provisioning/build of features. Note that I have "Include Required > Software" unchecked. We'll take a look... This is really a releng issue, so I'll reassign it to that. In order to set things up the way they were in Helios (given the new base/core split), a bug in Buckminster needs to be fixed (see bug 333588). I'm resolving all old releng bugs because the build has been replaced with a Tycho build: https://bugs.eclipse.org/bugs/show_bug.cgi?id=529487 And the update site has been superseded by: http://download.eclipse.org/modeling/emf/emf/builds/ If there are outstanding issues, please report a new bug based on the new build infrastructure and the new update site. |