On Wed, Apr 11, 2007 at 09:45:17PM +0200, Heinrich Nirschl spake thus: *snip* > On 4/11/07, Alan D. Salewski <[EMAIL PROTECTED]> wrote: > >Maybe we need an attribute for 'finalName' that indicates "yes I know > >this name will not be accessible by maven once installed or deployed"; > >when set maven would deploy the file as named. > > Why insist to put something into a *maven* repository if there is no > intention to access it by maven? Wouldn't it be more useful to be able > to publish to a different place? I don't know, if there already is a > plugin achieving that, but it would not be too hard to build. > > Henry
I'm not insisting on it; in fact, I like your idea much better ;-) Our current practice of deploying all of our artifacts to our internal maven repository came about because the infrastructure was already in place and accessible by everyone who needed access to the artifacts. Now that you mention it, though, it would make sense to have an arbitrary deployment plugin. There is precedence for this with other specialized deployment plugins (cargo, tomcat, probably others). -Al -- :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: Alan D. Salewski Software Developer Health Market Science, Inc. :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
