On Thu, 2002-04-04 at 14:51, Jon Scott Stevens wrote: > on 4/4/02 6:59 AM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I just got back online and notice that the maven bootstrap is broken. > > > > It is broken because someone updated the beanutils jar with an > > unreleased version which breaks everything because it has > > commons-logging stuff. > > > > This is a process that has to be dealt with but if you intend to update > > something please post a note first. The JARs in the repo can't be > > changed willy-nilly with the latest CVS builds or you can potentially > > break a lot of people's code. The maven bootstrap is an example of this. > > > > I will try to get a logging process going and a target in the maven > > build system so that we can track changes in the central repository. The > > beanutils that works has been put back. > > THIS IS WHY I SAID TO PUT THE FILES IN A CVS REPO!
You mean for the central repository? For some reason I always thought you meant for each individual project. If this is for the entire central repository then I'm not averse to that idea. But the repository should still be the location for released versions of tools. For logging I think this is a good idea. I still do not agree that it is a good thing to check in N developmental builds. If using CVS for the central repo is what you mean. > That way, I can reference an unreleased beanutils and you can reference > released versions. All you had to do was name it something different to identify it as different and all would have been well. > -jon > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
