I cannot put a comment on the issue but the patch doesn't work. I didn't study why.But I found a solution.
:-)
We have a solution using the wagon-scm and the scm-svn frrm Maven's team.
It's a little bit slow if find but it works and it is automated.
The only limitation is that it uses the svn executable you have on your desktop and not a java implementation.
Is it a problem ?
Everybody has svn executable on its computer ?
I suppose because it is also required for the release plugin.
If we need I can work in my free time to have a wagon-svn compatible with the javasvn implementation of scm. It will remove the need to have svn binaries to do a release and to publish artifacts.
I will release a new beta of jboss-parent and gatein-parent and update our components to use it.
Arnaud
On Fri, Oct 9, 2009 at 1:33 PM, Arnaud HERITIER
<aheritier@gmail.com> wrote:
The issue is here and a patch is provided.
I'll try to apply it and test to see if it solves our issue
If yes, we'll have to find someone in the team to apply it and do a release.
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
#
http://www.exoplatform.com#
http://blog.aheritier.net
Those librairies are using svnkit and not our local svn binairies to deploy.This is certainly why we have the difference.
On Thu, Oct 8, 2009 at 5:27 PM, Thomas Heute
<theute@redhat.com> wrote:
This is puzzling me :(
I really wonder why it works when we do it 'manually'...
SVN has a mechanism to automatically set some properties based on the
extension for example, but I see that in my case it is set as 'off' by
default, still it does some kind of magic as if I upload a text file or
binary it acts differently.
On 10/08/2009 05:20 PM, Arnaud HERITIER wrote:
Same issue with wagon-svn :
Perhaps we can propose a patch to kohsuke
Arnaud
On Thu, Oct 8, 2009 at 4:17 PM, Thomas Heute
<theute@redhat.com> wrote:
On 10/08/2009 04:06 PM, Arnaud HERITIER wrote:
Is it a problem ?
Yes encoding might screw up the binaries. In other terms, it isn't safe.
I always released MOP with the release
plugin :-)
But a thing changed betwenn Beta07 and Beta08. I'm using
though
the gatein-parent the last jboss-parent and we do not more deploy our
releases on a local svn checkout that we commit. We directly use the
webdav connector.
Yes that's the difference and I think that's what is broken. I've been
advised to release locally and push for this reason.
I have to do some tests on jboss parent to see if we can fix
it.
With Paul we know that their is another connector for SVN. Perhaps it
can help.
ok
The problem is to test it. There's only the releases repo of
jboss which is using SVN.
I'll do some tests on a sandbox svn @ exo.
Let me know if I can help.