I'm looking for a work around since the CR opened for this bug indicates that there may be a workaround (it's priority has been marked minor).
What did the Maven community use before Maven 2.0.5 to achieve this? Did you have to build from source if you wanted a plugin at a remote site? Wendy Smoak-3 wrote: > > On Feb 5, 2008 11:54 AM, nadias <[EMAIL PROTECTED]> wrote: >> >> Actually, I would like to use deploy:deploy-file but since it doesn't >> update >> the metadata, I would like to force it to update the metadata somehow - >> similar to how deploy or deploy:deploy works. > > This is circular. It's a bug. If you could make it work, it wouldn't > be a bug. :) > > http://jira.codehaus.org/browse/MDEPLOY-52 > > Depending on how badly you want this fixed, you might take a look at > the deploy plugin source code and see what it would take to make > deploy-file do the same thing with the metadata that deploy already > does... > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Updating-Meta-Data-tp15282046s177p15301810.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
