You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "fabrizio giustina (JIRA)" <ji...@codehaus.org> on 2005/08/01 21:59:57 UTC
[jira] Created: (MPSITE-34) site:sshdeploy now always fails for any remote error
site:sshdeploy now always fails for any remote error
----------------------------------------------------
Key: MPSITE-34
URL: http://jira.codehaus.org/browse/MPSITE-34
Project: maven-site-plugin
Type: Bug
Components: plugin
Versions: 1.6.1
Reporter: fabrizio giustina
after the patch for MPSITE-28 (Maven site 1.6.1 plugin always results in 'Build Successful') now sshdeploy fails for any "minor" error: for example if tar can't overwrite a file or if the remote user doesn't have the needed rights to change the permission for the root site directory (which is pretty common, like for the htdocs dir on sourceforge).
This is also more annoying considering that an incomplete deploy can leave a remote *.tar file, which by default is not overwritten and that will make any further build fail till manually removed.
for refence, this is the patch previously applied by Arnaud:
http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/site/plugin.jelly?rev=202438&r1=189828&r2=202438&diff_format=h
what about leaving the "failonerror" parameter in last snippet to "false" or at least making it configurable?
<exec dir="." executable="${maven.ssh.executable}" failonerror="true"> <------ will make the build fail if any of the commands will report an "innocent" error
<arg line="${maven.ssh.args} -l ${siteUsername} ${siteAddress} 'cd ${maven.homepage} &&
${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz && ${maven.site.tar.executable}
${maven.site.tar.options} ${maven.final.name}-site.tar && chmod -Rf g+u * . && rm
${maven.final.name}-site.tar'"/>
</exec>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPSITE-34) site:sshdeploy now always fails for any remote error
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPSITE-34?page=comments#action_43763 ]
fabrizio giustina commented on MPSITE-34:
-----------------------------------------
You are right, I am using 1.6.2 snapshot compiled from svn, not 1.6.1
> site:sshdeploy now always fails for any remote error
> ----------------------------------------------------
>
> Key: MPSITE-34
> URL: http://jira.codehaus.org/browse/MPSITE-34
> Project: maven-site-plugin
> Type: Bug
> Components: plugin
> Versions: 1.6.1
> Reporter: fabrizio giustina
> Assignee: Arnaud Heritier
>
>
> after the patch for MPSITE-28 (Maven site 1.6.1 plugin always results in 'Build Successful') now sshdeploy fails for any "minor" error: for example if tar can't overwrite a file or if the remote user doesn't have the needed rights to change the permission for the root site directory (which is pretty common, like for the htdocs dir on sourceforge).
> This is also more annoying considering that an incomplete deploy can leave a remote *.tar file, which by default is not overwritten and that will make any further build fail till manually removed.
> for refence, this is the patch previously applied by Arnaud:
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/site/plugin.jelly?rev=202438&r1=189828&r2=202438&diff_format=h
> what about leaving the "failonerror" parameter in last snippet to "false" or at least making it configurable?
> <exec dir="." executable="${maven.ssh.executable}" failonerror="true"> <------ will make the build fail if any of the commands will report an "innocent" error
> <arg line="${maven.ssh.args} -l ${siteUsername} ${siteAddress} 'cd ${maven.homepage} &&
> ${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz && ${maven.site.tar.executable}
> ${maven.site.tar.options} ${maven.final.name}-site.tar && chmod -Rf g+u * . && rm
> ${maven.final.name}-site.tar'"/>
> </exec>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPSITE-34) site:sshdeploy now always fails for any remote error
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPSITE-34?page=all ]
Arnaud Heritier updated MPSITE-34:
----------------------------------
Assign To: (was: Arnaud Heritier)
> site:sshdeploy now always fails for any remote error
> ----------------------------------------------------
>
> Key: MPSITE-34
> URL: http://jira.codehaus.org/browse/MPSITE-34
> Project: maven-site-plugin
> Type: Bug
> Components: plugin
> Versions: 1.6.2
> Reporter: fabrizio giustina
>
>
> after the patch for MPSITE-28 (Maven site 1.6.1 plugin always results in 'Build Successful') now sshdeploy fails for any "minor" error: for example if tar can't overwrite a file or if the remote user doesn't have the needed rights to change the permission for the root site directory (which is pretty common, like for the htdocs dir on sourceforge).
> This is also more annoying considering that an incomplete deploy can leave a remote *.tar file, which by default is not overwritten and that will make any further build fail till manually removed.
> for refence, this is the patch previously applied by Arnaud:
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/site/plugin.jelly?rev=202438&r1=189828&r2=202438&diff_format=h
> what about leaving the "failonerror" parameter in last snippet to "false" or at least making it configurable?
> <exec dir="." executable="${maven.ssh.executable}" failonerror="true"> <------ will make the build fail if any of the commands will report an "innocent" error
> <arg line="${maven.ssh.args} -l ${siteUsername} ${siteAddress} 'cd ${maven.homepage} &&
> ${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz && ${maven.site.tar.executable}
> ${maven.site.tar.options} ${maven.final.name}-site.tar && chmod -Rf g+u * . && rm
> ${maven.final.name}-site.tar'"/>
> </exec>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPSITE-34) site:sshdeploy now always fails for any remote error
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPSITE-34?page=all ]
Arnaud Heritier updated MPSITE-34:
----------------------------------
Version: (was: 1.6.1)
1.6.2
More logical. It's a problem in 1.6.2 due to MPSITE-28
> site:sshdeploy now always fails for any remote error
> ----------------------------------------------------
>
> Key: MPSITE-34
> URL: http://jira.codehaus.org/browse/MPSITE-34
> Project: maven-site-plugin
> Type: Bug
> Components: plugin
> Versions: 1.6.2
> Reporter: fabrizio giustina
> Assignee: Arnaud Heritier
>
>
> after the patch for MPSITE-28 (Maven site 1.6.1 plugin always results in 'Build Successful') now sshdeploy fails for any "minor" error: for example if tar can't overwrite a file or if the remote user doesn't have the needed rights to change the permission for the root site directory (which is pretty common, like for the htdocs dir on sourceforge).
> This is also more annoying considering that an incomplete deploy can leave a remote *.tar file, which by default is not overwritten and that will make any further build fail till manually removed.
> for refence, this is the patch previously applied by Arnaud:
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/site/plugin.jelly?rev=202438&r1=189828&r2=202438&diff_format=h
> what about leaving the "failonerror" parameter in last snippet to "false" or at least making it configurable?
> <exec dir="." executable="${maven.ssh.executable}" failonerror="true"> <------ will make the build fail if any of the commands will report an "innocent" error
> <arg line="${maven.ssh.args} -l ${siteUsername} ${siteAddress} 'cd ${maven.homepage} &&
> ${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz && ${maven.site.tar.executable}
> ${maven.site.tar.options} ${maven.final.name}-site.tar && chmod -Rf g+u * . && rm
> ${maven.final.name}-site.tar'"/>
> </exec>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MPSITE-34) site:sshdeploy now always fails for any remote error
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPSITE-34?page=all ]
Arnaud Heritier closed MPSITE-34:
---------------------------------
Resolution: Fixed
New property maven.site.failonerror can be used bypass remote errors.
> site:sshdeploy now always fails for any remote error
> ----------------------------------------------------
>
> Key: MPSITE-34
> URL: http://jira.codehaus.org/browse/MPSITE-34
> Project: maven-site-plugin
> Type: Bug
> Components: plugin
> Versions: 1.7
> Reporter: fabrizio giustina
> Fix For: 1.7
>
>
> after the patch for MPSITE-28 (Maven site 1.6.1 plugin always results in 'Build Successful') now sshdeploy fails for any "minor" error: for example if tar can't overwrite a file or if the remote user doesn't have the needed rights to change the permission for the root site directory (which is pretty common, like for the htdocs dir on sourceforge).
> This is also more annoying considering that an incomplete deploy can leave a remote *.tar file, which by default is not overwritten and that will make any further build fail till manually removed.
> for refence, this is the patch previously applied by Arnaud:
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/site/plugin.jelly?rev=202438&r1=189828&r2=202438&diff_format=h
> what about leaving the "failonerror" parameter in last snippet to "false" or at least making it configurable?
> <exec dir="." executable="${maven.ssh.executable}" failonerror="true"> <------ will make the build fail if any of the commands will report an "innocent" error
> <arg line="${maven.ssh.args} -l ${siteUsername} ${siteAddress} 'cd ${maven.homepage} &&
> ${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz && ${maven.site.tar.executable}
> ${maven.site.tar.options} ${maven.final.name}-site.tar && chmod -Rf g+u * . && rm
> ${maven.final.name}-site.tar'"/>
> </exec>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPSITE-34) site:sshdeploy now always fails for any remote error
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPSITE-34?page=comments#action_43738 ]
Arnaud Heritier commented on MPSITE-34:
---------------------------------------
MPSITE-28 can't be the root cause of this problem if you are using the release 1.6.1. This patch was applied on the 1.6.2 which is not yet released.
> site:sshdeploy now always fails for any remote error
> ----------------------------------------------------
>
> Key: MPSITE-34
> URL: http://jira.codehaus.org/browse/MPSITE-34
> Project: maven-site-plugin
> Type: Bug
> Components: plugin
> Versions: 1.6.1
> Reporter: fabrizio giustina
> Assignee: Arnaud Heritier
>
>
> after the patch for MPSITE-28 (Maven site 1.6.1 plugin always results in 'Build Successful') now sshdeploy fails for any "minor" error: for example if tar can't overwrite a file or if the remote user doesn't have the needed rights to change the permission for the root site directory (which is pretty common, like for the htdocs dir on sourceforge).
> This is also more annoying considering that an incomplete deploy can leave a remote *.tar file, which by default is not overwritten and that will make any further build fail till manually removed.
> for refence, this is the patch previously applied by Arnaud:
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/site/plugin.jelly?rev=202438&r1=189828&r2=202438&diff_format=h
> what about leaving the "failonerror" parameter in last snippet to "false" or at least making it configurable?
> <exec dir="." executable="${maven.ssh.executable}" failonerror="true"> <------ will make the build fail if any of the commands will report an "innocent" error
> <arg line="${maven.ssh.args} -l ${siteUsername} ${siteAddress} 'cd ${maven.homepage} &&
> ${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz && ${maven.site.tar.executable}
> ${maven.site.tar.options} ${maven.final.name}-site.tar && chmod -Rf g+u * . && rm
> ${maven.final.name}-site.tar'"/>
> </exec>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPSITE-34) site:sshdeploy now always fails for any remote error
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPSITE-34?page=all ]
Lukas Theussl updated MPSITE-34:
--------------------------------
Fix Version: 1.6.2
> site:sshdeploy now always fails for any remote error
> ----------------------------------------------------
>
> Key: MPSITE-34
> URL: http://jira.codehaus.org/browse/MPSITE-34
> Project: maven-site-plugin
> Type: Bug
> Components: plugin
> Versions: 1.6.2
> Reporter: fabrizio giustina
> Fix For: 1.6.2
>
>
> after the patch for MPSITE-28 (Maven site 1.6.1 plugin always results in 'Build Successful') now sshdeploy fails for any "minor" error: for example if tar can't overwrite a file or if the remote user doesn't have the needed rights to change the permission for the root site directory (which is pretty common, like for the htdocs dir on sourceforge).
> This is also more annoying considering that an incomplete deploy can leave a remote *.tar file, which by default is not overwritten and that will make any further build fail till manually removed.
> for refence, this is the patch previously applied by Arnaud:
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/site/plugin.jelly?rev=202438&r1=189828&r2=202438&diff_format=h
> what about leaving the "failonerror" parameter in last snippet to "false" or at least making it configurable?
> <exec dir="." executable="${maven.ssh.executable}" failonerror="true"> <------ will make the build fail if any of the commands will report an "innocent" error
> <arg line="${maven.ssh.args} -l ${siteUsername} ${siteAddress} 'cd ${maven.homepage} &&
> ${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz && ${maven.site.tar.executable}
> ${maven.site.tar.options} ${maven.final.name}-site.tar && chmod -Rf g+u * . && rm
> ${maven.final.name}-site.tar'"/>
> </exec>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MPSITE-34) site:sshdeploy now always fails for any remote error
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPSITE-34?page=all ]
Arnaud Heritier updated MPSITE-34:
----------------------------------
Comment: was deleted
> site:sshdeploy now always fails for any remote error
> ----------------------------------------------------
>
> Key: MPSITE-34
> URL: http://jira.codehaus.org/browse/MPSITE-34
> Project: maven-site-plugin
> Type: Bug
> Components: plugin
> Versions: 1.6.1
> Reporter: fabrizio giustina
> Assignee: Arnaud Heritier
>
>
> after the patch for MPSITE-28 (Maven site 1.6.1 plugin always results in 'Build Successful') now sshdeploy fails for any "minor" error: for example if tar can't overwrite a file or if the remote user doesn't have the needed rights to change the permission for the root site directory (which is pretty common, like for the htdocs dir on sourceforge).
> This is also more annoying considering that an incomplete deploy can leave a remote *.tar file, which by default is not overwritten and that will make any further build fail till manually removed.
> for refence, this is the patch previously applied by Arnaud:
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/site/plugin.jelly?rev=202438&r1=189828&r2=202438&diff_format=h
> what about leaving the "failonerror" parameter in last snippet to "false" or at least making it configurable?
> <exec dir="." executable="${maven.ssh.executable}" failonerror="true"> <------ will make the build fail if any of the commands will report an "innocent" error
> <arg line="${maven.ssh.args} -l ${siteUsername} ${siteAddress} 'cd ${maven.homepage} &&
> ${maven.site.gunzip.executable} ${maven.final.name}-site.tar.gz && ${maven.site.tar.executable}
> ${maven.site.tar.options} ${maven.final.name}-site.tar && chmod -Rf g+u * . && rm
> ${maven.final.name}-site.tar'"/>
> </exec>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org