On Oct 11, 2006, at 4:57 PM, Simon Nash wrote:
Thanks. Using the local maven repo is convenient for maven users, and adding full maven support (transitive dependency resolution and automatic downloading) to the standalone environment is a significant improvement for these users. However, I'm a bit concerned about requiring all users of the standalone environment to use maven downloading or have a local maven repo in order to get these dependencies resolved. For M2 it's probably best to do it this way for both the webapp and standalone environments and document how this works. (I will add this to the Basic Instructions document that I'm writing.) After M2 I'd like to consider what we could do for users who for whaetever reason aren't bought into maven.
The online repo is a good resource even if you are not using Maven as a build system. For example, someone using Ant can download jars or whatever by hand from one place rather than having to look at a number of different download sites. MavenProxy and other mirror systems also allow it to be replicated inside a firewall and populated with an organization's proprietary resources.
For the webapp, the download service (I believe) also looks in the war first under /WEB-INF/tuscany/repository/ so people who want everything packaged in one archive can still do so. They don't have to use the war plugin to get those resources there, any decent build tool/IDE should be able to do that. And, of course, that's just the default impl for the ArtifactRepository - a user can replace it with one of their choosing.
I would imagine the same thing would work in the standalone environment if we replaced the current simple impl with the full Maven-based one that the webapp uses. I think the impl just looks relative to the baseURL returned from the RuntimeInfo so it should work the same way. There's an option in the assembly plugin to copy artifacts and their dependencies into a repo structure in the assembly so that should be easy to set up as well. This would be worth exploring as a way of including extensions in the distro.
These are all config changes. I'm with you that anything more complex should happen after M2. We'll probably need to make a whole bunch of changes anyway when the spec starts to settle on a deployment story.
-- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
