You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Felipe Leme <ma...@felipeal.net> on 2005/06/06 03:51:25 UTC
Problem with site:deploy (was: Re: [vote] release gump, scm
plugins)
Brett,
I got the same issues when I released ear 1.7. Actually, the SCM plugin
per se seems to be fine, the problem is on the site plugin that try to
deploy the site at www.apache.org/home/brett/public_html/maven-stage-
site/, which are the values set by maven.site.stage.address and
maven.site.stage.directory on plugin-parent/project.properties. I don't
know if the problem is on the plugin's plugin.jelly or on plugin-
parent/project.properties, but I ended up uploading it manually, as even
if I changed these values it still failed, with the following messages:
[exec] rsync: chgrp "/www/maven.apache.org/reference/plugins/ear/."
failed: Operation not permitted (1)
[exec] rsync: chgrp
"/www/maven.apache.org/reference/plugins/ear/announcements" failed:
Operation not permitted (1)
[exec] rsync: chgrp
"/www/maven.apache.org/reference/plugins/ear/images" failed: Operation
not permitted (1)
[exec] rsync: chgrp
"/www/maven.apache.org/reference/plugins/ear/images/logos" failed:
Operation not permitted (1)
[exec] rsync: chgrp
"/www/maven.apache.org/reference/plugins/ear/style" failed: Operation
not permitted (1)
[exec] rsync: chgrp "/www/maven.apache.org/reference/plugins/ear/."
failed: Operation not permitted (1)
[exec] rsync: chgrp
"/www/maven.apache.org/reference/plugins/ear/announcements" failed:
Operation not permitted (1)
[exec] rsync: chgrp
"/www/maven.apache.org/reference/plugins/ear/images" failed: Operation
not permitted (1)
[exec] rsync: chgrp
"/www/maven.apache.org/reference/plugins/ear/images/logos" failed:
Operation not permitted (1)
[exec] rsync: chgrp
"/www/maven.apache.org/reference/plugins/ear/style" failed: Operation
not permitted (1)
[exec] rsync error: some files could not be transferred (code 23) at
main.c(702)
[exec] [ERROR] Result: 23
-- Felipe
On Mon, 2005-05-30 at 21:55 +1000, Brett Porter wrote:
> Felipe Leme wrote:
>
> >Hmm, when I released the EAR plugin a couple of weeks ago, I think (but
> >not sure :-( I had some issues with the code on SVN too, so I need to
> >use beta3.
> >
> >So, +1 if Brett releases 1.5 using RC1 :-)
> >
> >
> >
> I did, but I didn't have the problem before either.
>
> Can you elaborate? I'd like to confirm. (I might be able to dig it up,
> but if you have it, that'd be great).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with site:deploy
Posted by Felipe Leme <ma...@felipeal.net>.
On Mon, 2005-06-06 at 13:35 +1000, Brett Porter wrote:
> Isn't that how the instructions are?
>
> plugin:repository-deploy,site:deploy,site:publish
No, the site only says:
Produce a clean build using maven -Dmaven.repo.list=apache scm:perform-
release. When prompted for the tag, enter the one used in the previous
step. When prompted for the goal, enter plugin:repository-
deploy,site:deploy for plugins, or jar:deploy,site:deploy for an
individual JAR. To release a Maven distribution, see below.
So, that part of the instructions is missing the site:publish stage.
Also, the part that contains the properties that must be set at
$HOME/build.properties should contains the live properties as well;
right now it only says:
maven.repo.apache.username - your apache username
* maven.repo.apache.privatekey - the filename of your SSH private key
* maven.repo.apache.passphrase - the passphrase for your private key
( not your Apache password)
* maven.announcement.mail.from - Your name and email address, as
subscribed to the users and developers mailing lists, e.g. Brett
Porter <br...@apache.org>
* maven.announcement.mail.server - The SMTP server to use for sending
the announcement mail.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with site:deploy
Posted by Brett Porter <br...@apache.org>.
Isn't that how the instructions are?
plugin:repository-deploy,site:deploy,site:publish
- Brett
Felipe Leme wrote:
>On Mon, 2005-06-06 at 13:24 +1000, Brett Porter wrote:
>
>
>
>>That's not the standard way to do things... site:publish is meant to
>>push it live from staging, so that both sites are updated.
>>
>>
>
>So, how should we do the releases then? I mean the maven plugins
>project, not a generic project using maven....
>
>-- Felipe
>
>
>---------------------------------------------------------------------
>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: Problem with site:deploy
Posted by Felipe Leme <ma...@felipeal.net>.
On Mon, 2005-06-06 at 13:24 +1000, Brett Porter wrote:
> That's not the standard way to do things... site:publish is meant to
> push it live from staging, so that both sites are updated.
So, how should we do the releases then? I mean the maven plugins
project, not a generic project using maven....
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with site:deploy
Posted by Brett Porter <br...@apache.org>.
Felipe Leme wrote:
>On Mon, 2005-06-06 at 13:00 +1000, Brett Porter wrote:
>
>
>
>>>http://maven.apache.org/developers/making-releases.html
>>>
>>>Shouldn't this property/procedure be described there?
>>>
>>>
>>>
>>>
>>No, they are only a workaround because of permission issues. Like I
>>said, I think it -did- work the first time, despite the errors (which
>>are more like warnings).
>>
>>
>
>I'm sorry, I'm kind of lost here. The permission issues is related to
>the rsync/ssh method, right? What I suggested should be document is the
>use of the maven.site.deploy.live (on the making-releases page, not on
>site's properties page, which already has it documented).
>
>
That's not the standard way to do things... site:publish is meant to
push it live from staging, so that both sites are updated.
- Brett
>-- Felipe
>
>
>---------------------------------------------------------------------
>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: Problem with site:deploy
Posted by Felipe Leme <ma...@felipeal.net>.
On Mon, 2005-06-06 at 13:00 +1000, Brett Porter wrote:
> >http://maven.apache.org/developers/making-releases.html
> >
> >Shouldn't this property/procedure be described there?
> >
> >
> No, they are only a workaround because of permission issues. Like I
> said, I think it -did- work the first time, despite the errors (which
> are more like warnings).
I'm sorry, I'm kind of lost here. The permission issues is related to
the rsync/ssh method, right? What I suggested should be document is the
use of the maven.site.deploy.live (on the making-releases page, not on
site's properties page, which already has it documented).
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with site:deploy
Posted by Brett Porter <br...@apache.org>.
Felipe Leme wrote:
>On Mon, 2005-06-06 at 11:54 +1000, Brett Porter wrote:
>
>
>>As before, you can use -Dmaven.site.deploy.live=true to push directly
>>
>>
>
>Hmm, I followed these instructions:
>
>http://maven.apache.org/developers/making-releases.html
>
>Shouldn't this property/procedure be described there?
>
>
No, they are only a workaround because of permission issues. Like I
said, I think it -did- work the first time, despite the errors (which
are more like warnings).
>
>
>
>>You can probably change the rsync option so it doesn't complain, but I'm
>>pretty sure the command below actually worked.
>>
>>
>
>I agree, it should work. Anyway, I just manually sshed it this time...
>
>
>BTW, how long does it take for the content of people.apache.org/www be
>synchronized to the live sites?
>
>
every 2 hours
>-- Felipe
>
>
>---------------------------------------------------------------------
>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: Problem with site:deploy
Posted by Felipe Leme <ma...@felipeal.net>.
On Mon, 2005-06-06 at 11:54 +1000, Brett Porter wrote:
> As before, you can use -Dmaven.site.deploy.live=true to push directly
Hmm, I followed these instructions:
http://maven.apache.org/developers/making-releases.html
Shouldn't this property/procedure be described there?
> You can probably change the rsync option so it doesn't complain, but I'm
> pretty sure the command below actually worked.
I agree, it should work. Anyway, I just manually sshed it this time...
BTW, how long does it take for the content of people.apache.org/www be
synchronized to the live sites?
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with site:deploy
Posted by Brett Porter <br...@apache.org>.
As before, you can use -Dmaven.site.deploy.live=true to push directly
live, and use -Dmaven.site.deploy.method=ssh to avoid rsync.
You can probably change the rsync option so it doesn't complain, but I'm
pretty sure the command below actually worked.
- Brett
Felipe Leme wrote:
>Brett,
>
>I got the same issues when I released ear 1.7. Actually, the SCM plugin
>per se seems to be fine, the problem is on the site plugin that try to
>deploy the site at www.apache.org/home/brett/public_html/maven-stage-
>site/, which are the values set by maven.site.stage.address and
>maven.site.stage.directory on plugin-parent/project.properties. I don't
>know if the problem is on the plugin's plugin.jelly or on plugin-
>parent/project.properties, but I ended up uploading it manually, as even
>if I changed these values it still failed, with the following messages:
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org