| Summary: | consolidate feature definitions | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Martin Lippert <mlippert> |
| Component: | tooling | Assignee: | Project Inbox <virgo-inbox> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse, leo.dos.santos, mlippert, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 368890 | ||
|
Description
Martin Lippert
Yep, makes sense. See also bug 368580. I believe we also want a separate feature for Zest, but we can make that included in either the SDK or IDE as appropriate. Steffen, could use your help on this one as well. I'm not familiar enough with Maven builds to know how to put together an automated source code feature build. (I know this is possible in buckminster, and I'm hoping there is some equally straight-forward way of doing this. I know what to do in terms of the feature templates and what not if that's all the same, I just don't know how to setup the build artifacts themselves.
We really only need two features:
1. The Virgo Tools, including all docs. (we already have this)
Leo and I talked about the possibility of having a separate feature for documentation, but both of us felt it was over-kill. (The docs are about 6 MB as they include runtime.)
2. Virgo SDK / Source for Virgo. Could include above plus the source code.
I haven't done this with Tycho myself but I believe support for source features was added recently: bug 345234. This will not happen any time soon. :) |