Community
Participate
Working Groups
Virgo 3.0 supports plans inside PAR files. See bug 335689 for details. It would be good if the tooling also supported this.
Where were you envisioning that the relevant artifact(s) would reside? Is this a separate plugin project, feature project or an artifact within a particular plugin that captures dependencies of that plugin?
(In reply to comment #1) > Where were you envisioning that the relevant artifact(s) would reside? Is this > a separate plugin project, feature project or an artifact within a particular > plugin that captures dependencies of that plugin? I have no strong feelings or preconceptions, so feel free to implement this in any reasonable way.
OK, ideas/comments from community are especially welcome on this one. This sounds quite useful but likely won't be a near-term priority unless people vote for or comment on it; it seems like one of those "better to do right than do quick" kind of things.