Community
Participate
Working Groups
This involves a change to the plan schema and so pre-req's the move of the schema to eclipse.org.
I second the need for this enhancement. The ability to specify a URI would allow users to update artifacts of a plan at runtime, which seems like a missing feature of the plan. Additionally, to cater for this feature it might be necessary to address the following: * Ability to explicitly specify an artifact loading strategy in the plan - i.e. if a version range is provided, go for the latest\oldest version or by ID in the system (i.e. the order it was first added) * To avoid the overhead of a watch directory for runtime changes, perhaps implementing a lazy-load solution on a .plan deployment to /pickup or a way to trigger a one-time 'watch' on the local repository that allows for a new version of a bundle to be added at runtime could be introduced. Cheers, Matt
(In reply to comment #1) > I second the need for this enhancement. Thanks! [...] > * To avoid the overhead of a watch directory for runtime changes, perhaps > implementing a lazy-load solution on a .plan deployment to /pickup or a way to > trigger a one-time 'watch' on the local repository that allows for a new > version of a bundle to be added at runtime could be introduced. Compare the triggering of a 'watch' which is likely to be necessary to solve bug 337846. > > Cheers, > Matt
Documentation in commit ed5ae019c00405fc75e4da04563ff477a69a83de. This will be pushed after the implementation is pushed so as not to mislead users of milestones.
Implemented in kernel commits (tagged with this bug number) culminating in the merge 893696e6c29b3fc741315bad61793d43b8e43eca. Documentation tweaked in commit 6b8b363b6d92ac472708fb146dfd0dc86eec8e2b.
Note that the current implementation has two restrictions which are documented in the Programmer Guide. Only absolute "file:" URIs are supported. Artefacts referenced by URIs in a plan need to be available when the plan is deployed and when Virgo restarts.
