[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: RE: [platform-update-dev] Investigating some alternative updatemanager
|
On 15/09/06, Mark_Melvin@xxxxxxxx <Mark_Melvin@xxxxxxxx> wrote:
For another reference design, the Azureus Bittorrent client
(http://azureus.sourceforge.net/) - an RCP app - has a rather neat automatic
update design (both functionally, and UI-wise). It even deploys its updates
over Bittorrent and uses itself to download them (and subsequently share
them after they are downloaded). It is kind of neat from an "eating your
own dogfood" perspective.
Completely agree that 'eating your own' is the way to go. Making it
easier to use the update manager over e.g. nightly builds might be one
way of making that happen.
By the way, all this talk of features versus bundles -- Maven is an
excellent example of the fine-grained stuff in action. When you
download a Maven project, each component has a defined set of
dependencies which it needs, and those are downloaded on demand. It's
this kind of model that I'd like to see Eclipse being able to support
in the future, and that's only going to happen by having lots of small
dependencies. (As previously observed, those small dependencies could
be scaled up to have the big dependencies that is the feature wad.)
But you don't get a 'maven' feature; you get a specific maven plugin,
and it has dependencies that it needs to run, which it downloads in
turn on demand if they're not already in the repository.
Alex.
