no objection: it's even better to do this manually, since the generated content will better match what's in the released component build
Then we should upgrade every plugin parent pom to avoid such issue for next plugins releases Regards, Hervé Le vendredi 1 mars 2013 15:11:54 Benson Margulies a écrit : > On Fri, Mar 1, 2013 at 3:08 PM, Olivier Lamy <[email protected]> wrote: > > upgrade to last maven-plugins parent 24 and that will work. > > Does anyone object if I do that manually in the checkout to publish > the site, rather than respin? > > > 2013/3/2 Benson Margulies <[email protected]>: > >> I was trying to follow our usual instructions at > >> > >> http://maven.apache.org/developers/release/maven-plugin-release.html > >> > >> and not too surprisingly, the site doc failed to push, because of > >> > >> Embedded error: Error performing commands for file transfer > >> Exit code: 1 - mkdir: /www/maven.apache.org/plugins: Permission denied > >> > >> for the changes plugin. > >> > >> Then, belatedly, it dawned on my that the CMS would seem to call for > >> the use of the new plugin. But that's not in the instructions, is it? > >> > >> Unless that's the 'other faster way'? > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > > > > -- > > Olivier Lamy > > Talend: http://coders.talend.com > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
