You are right, this is by design. I prefer to have a build fail by default, even if the error is minor, because otherwise I tend to overlook things.

The problem with sourceforge is that remote users don't have the right to change the permission for the root site directory (htdocs), so the corresponding chmod command always fails.

You are also right that this needs to be documented better, I will add a BIG note in the changelog. :)

Thanks again for your testing and feedback!

-Lukas



Dennis Lundberg wrote:
It's me again...

After getting the project site built correctly, I then tried to sshdeploy it to SourceForge using the new site-plugin. It didn't go all that well. Having switched back and forth between 1.6.1 and 1.7-SNAPSHOT I have found one thing that's different in 1.7. This might be by design, looking at the resolved issues MPSITE-28 and MPSITE-34.

There are a couple of errors from [exec] using either version. It's about directories that can't be unlinked. Not sure what that means. In 1.6.1 these are ignored by the plugin and the build succeeds. In 1.7-SNAPSHOT, on the other hand, the build fails. In both cases the site is in fact deployed and working. But because the 1.7-SNAPSHOT build fails there is a file (the .tar file) left on the server that doesn't get cleaned away. This prevents prevents subsequent site deploys from succeeding. I had to log in and manually remove that file. See the logs below.

Reading Fabrizios comments on MPSITE-34 I realize that he had the exact same problem. This was supposed to have been fixed by that issue, but the default value for maven.site.failonerror=true in plugin.properties. This means that everyone with a SF project who upgrades to site-plugin-1.7 has to add this property with a value of false, to their own project.properties file.

May I suggest that we either change the default value to false, to remain backwards compatible, or add a BIG note about this somewhere.





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to