Is it a problem ?

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.
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.
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.

Arnaud





On Wed, Oct 7, 2009 at 6:28 PM, Thomas Heute <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/mop-api/1.0.0-Beta03/mop-api-1.0.0-Beta03.jar
 > 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/mop-api/1.0.0-Beta08/mop-api-1.0.0-Beta08.jar
 > (Returns nothing which means text file)

--> It was deployed with maven release:perform

Thomas.
_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev