[vwnc] Federated Store
Locked
 
|
Hello List,
I would need a word of wisdom on a topic that I would like to propose as a class project. Background. I am lecturing a project oriented OOP class. Most of our project start up by taking bundles from public Store repositories (Cincom, DMP). Sometimes the students just use the bundles but sometimes they add new functionality. For different reasons, the students end up uploading on the local Store the packages that were downloaded from somewhere else (Cincom, DMP). This is a good practice because we keep the public repositories clean ;-). But I see a couple problems with this practice: +Duplication, +Possible inconsitencies: sometimes bandles have a complex chain of dependencies that are not well uploaded to my local store (for example soul or Opentalk). As a result, building a project in a fresh image requires (re)accessing other Stores and load the required bundles by hand. Question. What do you guys think of allowing Store to have dependecies to remote bandles so when I load a local bundle it goes and fetch its prerequisites from remote Stores? For example, last year a project built an extension to HotDraw that allows peer-to-peer editors. In my local Store now I have both, HotDraw and the extension (P2PHotDraw). Similarly a project allowed GLORP to handel Hibernate mapping definitions, the local Store now has both GLORP and XMLGLORP. I think it would be cool to have P2PHotDraw on m local repo which in turn fetch the required stuff from the remote repository. There is a lot more to say about this but this email is long enough. Thanks!, Federico _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
Federico Balaguer wrote:
> > Question. > What do you guys think of allowing Store to have dependecies to remote > bandles so when I load a local bundle it goes and fetch its > prerequisites from remote Stores? I dislike the idea of putting this functionality in the store 'load' code (because remote alterations will affect my build results), however I would like access to tools that allow me to resolve these 'remote' dependencies. Usually I only want to build from a known repository (mine) with known package versions in it. So I think that importing packages from remote Store repositories should not be done by loading them in an image and then publishing them in the local repository, instead replicating packages should be done by using the replicator tool. The replicator tool then seems like a much better place to implement the functionality you suggest: some UI/tool that alerts me when the prerequisites of some package I'm replicating are not present. As a variation I would like a tool that searches for newer package versions in the remote repository (i.e. it alerts me when I do have the prerequisite locally but it may have received some bug fixes remotely). Similarly I would like a tool that alerts me when I fixed a public package locally but failed to replicate the new version out to the public repository. Cheers! Reinout ------- _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
I'm less averse to having the store load code handle this as I am to making sure I have control of which repositories it will access, and in which order the accesses are made. Of course, this presupposes that we have multiple Store connections (or the ability to transparently switch among them), that we track the source repository and version when we publish to a different repository, that we understand the distinction between the replication of a package and a [new] publication of that package [elsewhere], and so on. The mechanics will need to handle credentials, etc.
Tools are great for tracking things down. Pprompts defeat the purpose of trying to do an automated build. Perhaps this is a case for an extended policy on how to handle load exceptions? Cheers! Tom Hawker -------------------------- Senior Framework Developer -------------------------- Home +1 (408) 274-4128 Office +1 (408) 576-6591 Mobile +1 (408) 835-3643 -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Reinout Heeck Sent: Wednesday, September 02, 2009 8:23 AM To: [hidden email] Subject: Re: [vwnc] Federated Store Federico Balaguer wrote: > > Question. > What do you guys think of allowing Store to have dependecies to remote > bandles so when I load a local bundle it goes and fetch its > prerequisites from remote Stores? I dislike the idea of putting this functionality in the store 'load' code (because remote alterations will affect my build results), however I would like access to tools that allow me to resolve these 'remote' dependencies. [snipped] Cheers! Reinout ------- _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc IMPORTANT NOTICE Email from OOCL is confidential and may be legally privileged. If it is not intended for you, please delete it immediately unread. The internet cannot guarantee that this communication is free of viruses, interception or interference and anyone who communicates with us by email is taken to accept the risks in doing so. Without limitation, OOCL and its affiliates accept no liability whatsoever and howsoever arising in connection with the use of this email. Under no circumstances shall this email constitute a binding agreement to carry or for provision of carriage services by OOCL, which is subject to the availability of carrier's equipment and vessels and the terms and conditions of OOCL's standard bill of lading which is also available at http://www.oocl.com. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
«
Return to VisualWorks
|
1 view|%1 views
| Free forum by Nabble | Edit this page |