Bugzilla – Full Text Bug Listing
| Summary: | Tweak the name of the Riena Target Platform feature | ||
|---|---|---|---|
| Product: | [RT] Riena | Reporter: | Jeff McAffer <jeffmcaffer> |
| Component: | Releng | Assignee: | Project Inbox <riena.core-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | christian.campo |
| Version: | 2.0.0 | ||
| Target Milestone: | 2.0.0.RC2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jeff McAffer
fixed in Riena 2.0.0.RC2 which now has Riena Core Target Components and Riena Sample Target Components Would it be possible to put the samples in the Riena Target Components? Does one normally add the samples to their target or install them in the IDE? Either way it would be great for there to be one Riena entry in the category. I am not sure I understand what you want me to do. Currently we have Riena Core Target Components. That is the Riena Runtime that you use to develop your code against and that you run your applications on top of. Then there is Riena Samples Target Components. These are samples, demos, tests and stuff that runs against Riena Core Target Componets and showcases the use of Riena. That is also installed into the target platform and then its easy to import it from there into your IDE. I wouldnt want to install the Samples INTO the IDE because they are no tooling. So i believe that is the correct way if you want something to be installable in pieces into your workspace from the Helios Repo. What is the Riena Target Components then ? If you mean Riena Core Target Componets, then I think is that it is possible but not a good idea. I would like the user to be able to only install the Riena Runtime without the Samples. Doesnt Equinox or ECF or others have multiple entries in the Helios repo. Maybe you can elaborate what you want me to do. > Currently we have Riena Core Target Components. That is the Riena Runtime that > you use to develop your code against and that you run your applications on top > of. Where is the source? The suggestion was to combine the two features that are currently categorized. From the consumer point of view they want all the Riena stuff in their target (or they don't know what all they want so it amounts to the same thing). Giving them a choice at that point is not a bonus. Certainly *included in* the Riena Target Components feature there should various runtime features that are useful for folks creating products or launch configs or their own features but that is a separate problem. In short, the feature that is listed in the TP category is for adding things to target platforms and is very unlikely to ever be used directly at runtime. > Then there is Riena Samples Target Components. These are samples, demos, tests > and stuff that runs against Riena Core Target Componets and showcases the use > of Riena. Unless the samples are somehow very large or unwieldy, they can just be combined much as the source is into the Target Components feature. > I wouldnt want to install the Samples INTO the IDE because they are no tooling. > So i believe that is the correct way if you want something to be installable in > pieces into your workspace from the Helios Repo. Sure. I was just asking to make sure I understood. Makes sense. > Doesnt Equinox or ECF or others have multiple entries in the Helios repo. Maybe > you can elaborate what you want me to do. No. Check out hte RC2 Helios repo. The other projects, for the most part, have only one Target Components feature that includes all that project has to offer. Inside that feature there are (many) other features that slice and dice the world into runtime bits etc. A few projects have multiple features (e.g., EMF) where there are some conflicting configurations (eg. SWT vs RAP). The focus here is to simplify the consumer's life. If each of the 10+ projects in the target category presented 2-4 choices then the hapless consumer would be faced with dozens of similar looking things in the category. Less is more :-) I looked at what Equinox is doing and indeed, when you look at the repo in Category mode you only see Equinox Target Components (which I guess is a feature that combines the other ones). If you switch of Category Mode, then you see Equinox Target Components but only Equinox Compendium SDK, Equinox Core SDK and so on. (not sure that these are called SDK again and not Target Components, because they are in my opinion smaller pieces of target components.....) anyway.... I will try to mimic that in my build tomorrow. I think I already have the feature for the Target Components which is removed during the packing process. Only problem is that I currently havnt played with categories. I have to figure out how that is done. (In reply to comment #5) > If you switch of Category Mode, then you see Equinox Target Components but only > Equinox Compendium SDK, Equinox Core SDK and so on. (not sure that these are > called SDK again and not Target Components, because they are in my opinion > smaller pieces of target components.....) anyway.... They are still called SDK because we were trying to minimize changes this late in the game. > I will try to mimic that in my build tomorrow. I think I already have the > feature for the Target Components which is removed during the packing process. > Only problem is that I currently havnt played with categories. I have to figure > out how that is done. Great. AFAIK, the categorization is spec'd in your Helios contribution or via a bug. In the past I always end up talking to David Williams but I'm sure there is a real way to do this :-) Thanks BTW for looking at this Its done and seems to work and be right what you wanted...... There is a prelimiary Helios Repo for RC3 available here http://download.eclipse.org/releases/staging. @Jeff maybe if you have some spare cycles you can check that this is the structure you wanted. I will close this bug as resolved. |