I actually believe the ibiblio m1 repo is a "virtual" repo created through Apache rewrite, redirect, filters, etc. I don't have details and I'm not a strong enough Apache admin to make it up on the fly here, but I am pretty certain I read this somewhere in an email on user/dev or on the Maven site somewhere.
So if you want to spend some time configuring things, you could probably eliminate your m1 repo entirely. Not saying this is trivial, but when you think about the differences between the repo formats, you can see how this could certainly be done. Wayne On 5/11/06, Siegmann Daniel, NY <[EMAIL PROTECTED]> wrote:
> Personally I find the M2 repo format a lot more scalable and > approachable. If you're only going to have a few projects > with a handful of releases each, then there's not necessarily > a strong reason to prefer M2 over M1, esp since M2 can read > from M1 repos. > > Wayne OK, thanks. I'll definitely be using an M2 repository. I also set up Maven-Proxy, which works nicely. It's really not a big deal for me to copy over the one artifact manually. I used to deploy manually anyway, before I set up an FTP server on that machine (FileZilla just made it so easy). The problem is remembering to do so - always a challenge for me. ;) Thanks, ~Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
