You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Harrison (JIRA)" <ji...@codehaus.org> on 2009/06/29 17:15:05 UTC
[jira] Created: (MSITE-410) site:deploy fails unnecessarily in
multi user environment
site:deploy fails unnecessarily in multi user environment
---------------------------------------------------------
Key: MSITE-410
URL: http://jira.codehaus.org/browse/MSITE-410
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: Paul Harrison
with a site deploy using sshexe in a multi user envionrment the build fails at a chmod if the site has previously been deployed by another user. This is irritating because it stops other plugins attached to the site-deploy phase from executing.
A better strategy to use in site deploy is to delete the directory that is being deployed to at the start, so that there are no mixed ownership issues when the chmod is done (after the files have been unzipped, as unzipping seems to retain the owner) - the delete will only work of course if the chmod has worked from the previous
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSITE-410) site:deploy fails unnecessarily in multi
user environment
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MSITE-410.
---------------------------------
Resolution: Duplicate
> site:deploy fails unnecessarily in multi user environment
> ---------------------------------------------------------
>
> Key: MSITE-410
> URL: http://jira.codehaus.org/browse/MSITE-410
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Paul Harrison
>
> with a site deploy using sshexe in a multi user envionrment the build fails at a chmod if the site has previously been deployed by another user. This is irritating because it stops other plugins attached to the site-deploy phase from executing.
> A better strategy to use in site deploy is to delete the directory that is being deployed to at the start, so that there are no mixed ownership issues when the chmod is done (after the files have been unzipped, as unzipping seems to retain the owner) - the delete will only work of course if the chmod has worked from the previous
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira