if CVS is keeping up to date, then that's news to me. AFAIK, the CVS repo is read-only now, and at the least, i've only been checking in changes to the SVN repo.
what issues were happening with SVN for you? just for the record, i think while we're all getting used to using subversion, it fine to ask questions on working with it here on the dev list. obviously, we want to help people to help us out with the development of velocity/tools, and such questions would fall under that. at least i know i'm still asking some questions on SVN here. :) On Fri, 18 Feb 2005 08:09:04 +0200, Florin Vancea <[EMAIL PROTECTED]> wrote: > This makes me reopen my old question: Is the CVS version up-to-date? > I tried to switch to SVN but it's my first attempt and I got some weird > behavior that I cannot afford to dig into now. > However, the CVS _seems_ to be still updated somehow. > > If CVS is still active, I'll try to keep the pace using that. If not, I'm > afraid I'll have to postpone until I have the time to play with SVN. > > ----- Original Message ----- > From: "Nathan Bubna" <[EMAIL PROTECTED]> > To: "Velocity Developers List" <[email protected]> > Sent: Thursday, February 17, 2005 10:00 PM > Subject: Re: More on compat with 1.2.4 > > > hmm. let me know if you figure it out. and since i have been making > > some updates since we switched to SVN, the sooner we can get early > > adopters switched over and using the latest code, the better it'll be > > for all of us. :) > > > > On Thu, 17 Feb 2005 18:19:53 +0200, Florin Vancea <[EMAIL PROTECTED]> > wrote: > > > Since you asked, Nathan: > > > > > > I stumbled on a glitch where $text was able to render correctly a key > but > > > $errors was not. However, I am using a custom MessageResources plugin > and I > > > cannot be really sure where is the problem. > > > For now it's not a major issue for me, but as soon as I clean out the > bigger > > > ones (not Velocity related :) ) I will check and report if it has > something > > > to do with the tools. > > > > > > Florin > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
