You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benson Margulies <bi...@gmail.com> on 2013/03/02 00:04:03 UTC
CMS versus plugin docs and releases
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: CMS versus plugin docs and releases
Posted by Hervé BOUTEMY <he...@free.fr>.
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 <ol...@apache.org> 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 <bi...@gmail.com>:
> >> 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: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: CMS versus plugin docs and releases
Posted by Benson Margulies <bi...@gmail.com>.
On Fri, Mar 1, 2013 at 3:08 PM, Olivier Lamy <ol...@apache.org> 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 <bi...@gmail.com>:
>> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: CMS versus plugin docs and releases
Posted by Olivier Lamy <ol...@apache.org>.
upgrade to last maven-plugins parent 24 and that will work.
2013/3/2 Benson Margulies <bi...@gmail.com>:
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org