The cvs code is now tagged so you can always grab the source that went
into to a release using:
cvs co -r JBoss_2_2_1 jboss
>
> OK, whatever you say.
>
> Then how about to release full source bundle
> synchronously with binary distribution?
>
> like:
>
> jboss-bin-2.2.1.zip
> jboss-src-2.2.1.zip
>
> otherwise it is really a pain to synchronize binary
> and source.
>
> We are using jboss on more than 10 machines, but
> only 4 of them are for development and others for
> "preproduction".
>
> Usually we grab the sources from CVS in the same
> day as next release is available, but it doesn't
> guarantee from small divergence.
>
>
> > ----- Original Message -----
> > From: "Alexander Kogan" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, April 19, 2001 2:48 PM
> > Subject: Re: [JBoss-user] 2.2.1 release available at sourceforge
> >
> > > Hi,
> > >
> > > That is really great that *binary* release is bundled with sources now.
> > >
> > > But, maybe, build directory should be also included in this case?
> > >
> > >
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
>
> --
> __________________________________________________
> Alexander Kogan PTC www.ptc.com
> [EMAIL PROTECTED] 140 Kendrick St. Needham MA 02494
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
