No brew in the open source project, WAS Re: [jboss-dev] latest jboss messaging/remoting

[Adrian Brock]

I've said this before, but now I'll say it more strongly.

There should be NO BREW RELEASES in the jboss.org releases.

If the project is on jboss.org then we should use a tag
from svn.jboss.org not some cvs server somewhere on a Redhat server.

All patches must go downstream into the open source project first!
brew is as bad as snapshot.

Also all releases should come with a zip file "artificat" 
(i.e. something that gets downloaded into thirdparty) 
that is the source, not a seperate directory containing a non-portable
tar.gz file that doesn't get downloaded.

tar.gz only works properly on GNU/Linux distributions.
JBoss is cross platform.

On Fri, 2007-12-07 at 13:00 +0200, Dimitris Andreadis wrote:
> I've flipped trunk (AS5) to the latest jboss messaging/remoting combination.
> 
> Let me know if you see any problems.
> 
> Thanks
> /Dimitris
> 
> -    <componentref name="jboss/messaging" version="1.4.0.SP1-brew"/>
> +    <componentref name="jboss/messaging" version="1.4.0.SP2-brew"/>
> ...
> -    <componentref name="jboss/remoting" version="2.2.2.SP2"/>
> +    <componentref name="jboss/remoting" version="2.2.2.SP3-brew"/>
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx