Hey,
On Mon, 22 May 2000, Jim Archer wrote:
> Hi All...
> I'm wondering if anyone else is seeing this, or if it somehow my
> environment. I have had these beans running fine in the past, so I expect
> the problem is with jboss. Would it be possible for you guys with commit
> access to get the CVS tree to a point where it mostly works (at least with
> the test beans) and then tag it, so that we can check out a latest working
> jBoss? As things are now, we often do a checkout to get the latest
> features, but there is something broken.
We did tag the jBoss 1 releases and we will tag the jBoss 2 releases as
well. So far, we haven't had jBoss 2 releases though. It is *under
development*. What you get is what you get, the bleeding edge. We bleed
alot and it gets messy sometimes :)
BTW, anyone aware of a mechanism that would make tagging in CVS a little
more bearable for large projects? It seems rather a chore to be manually
picking all the files with your mouse. I know I wouldn't want to do that
on a daily basis, and I doubt Rickard will want to do that either :)
-- Juha
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
