<snip/> > Does it not make sense to have a single maven style repository? This > could provide access to versioned resources and keep them all in one > place. Separate user repositories for each application seems like it > might encourage or require duplication of common resources. > > Are there any implications for a security model?. [Karasulu, Alex]
Your right the whole purpose for a repository is for keeping things in one place. However keep in mind that this so called application repository is really a artifact cache for the application and not a REPOSITORY REPOSITORY like ibiblio etc where you snarf down dependencies. The application repository is the local disk cache of all the dependencies pulled down from the remote repo. But your question still holds does it make sense to "allow" multiple artifact cache' one per application. I don't really know the answer to this right now because I have not encountered the use cases. The safest approach I think is to allow for it and leave it up to the user to decide and configure. What do you think? Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
