Bugzilla – Full Text Bug Listing
| Summary: | baseline version - target version - dependances | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Xavier Méhaut <xmehaut> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Xavier Méhaut
Wow, this is a lot of stuff. >>- I would create a project which depends to other projects or even external libraries >>- I would be able to build a new target version based uton the baseline (base version), ie I want to ba able to know for a specific version of my product which versions of the dependent projects I have [DUPLICATE?] There is some discussion in the vcm mail list on config maps which might solve what you want. You should have a look there and when a bug report is opened add yourself to it (if you think this will solve it). >>- I would be able to choose at Eclipse start up whcih version I want to work on [MOVE TO CORE]Eclipse can only startup based on what plugins you have locally. You can play games where you have different plugin directories and change the startup accordingly. But in all cases the plugins need to be local. >>- I would be able to work , at least in different workbench window, on different projet branches [MOVE TO CORE] This isn't VCM. There is only one workspace in eclipse (the workspace is the environment in which all compiles occur). You would need different compilation environments to do what you want. This is a Core issue, and there may already be a bug report there for it if you want to have a look and add yourself to the CC. >>- I would like to have a life cycle attached to a product version, ie I would like to know if the current version of my product is in development, integration, validation or production state [WONTFIX] There is no support for this in CVS. Some repositories do support explicit life-cycle (for example, have a look at Merant's PVCS). I don't think you can layer this on top of an existing repository technology, unless you can guarantee that others are going to use the same client. ------------- This bug report has some interesting ideas, but your really asking Eclipse to be something fairly different than what it is. There are some places that I've indicated that we might be able to make progress. If you can distill this down to something more attainable given our current architecture, the chances of us being able to do something are better. Also, in the future its helpful if you can submit separate reports for things that are orthogonal (e.g. lifecycle). I am moving this to Core because I think this report seems to be really about three things: 1) config maps (we already have a thread on that subject so would close this report as duplicate) 2) life cycle (wontfix) 3) multiple workspaces (core) |