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.
Arnaud
On Wed, Oct 7, 2009 at 6:28 PM, Thomas Heute <theute(a)redhat.com
<mailto:theute@redhat.com>> wrote:
It looks like the deployment straight to the Maven repo has some
issues.
All JARs are uploaded as text files instead of binaries. You can see
this with the following commands:
$ svn propget svn:mime-type
http://anonsvn.jboss.org/repos/repository.jboss.org/maven2/org/gatein/mop...
> application/octet-stream
--> All fine, it wasn't using maven release:perform
$ svn propget svn:mime-type
http://anonsvn.jboss.org/repos/repository.jboss.org/maven2/org/gatein/mop...
> (Returns nothing which means text file)
--> It was deployed with maven release:perform
Thomas.
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org <mailto:gatein-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/gatein-dev