> so I am frustrated, and should probably cool down, take a deep breath > and wait until americal guys wake up. But I just have to say this.
I am awake now. Please do take some deep breaths... > I do not work with the JBoss project every day, not even every week. But > once in a while I contribute something, be it documentation, bugfixes or > new features. And I have to say this: since buidldmagic entered JBoss > this has been a verry frustration bussines. I can hardly remember any > time I have not ended up in having a cvs working copy that is out of > sync with the cvs repository and which is not fixable by an ordinary > update. I keep explaning this over and over and over. This is a CVS issue, in that cvs update does not consult CVSROOT/modules for changes. Buildmagic has little to do with it. I setup the jboss-all project to use CVSROOT/modules because the poor layout of the existing modules did not allow for a single module name to be specified to get the required sources. I hope to fix this eventually, but it is complicated by the fact that CVS is on SF and there are (almost) 2 releases which need to be maintain off of the old and current style. If you like, you can revert to the old style of checking out modules one by one. > Currently I am making testing and making changes to JBossMQ, and it's > not more than I week that I had to get a fresh copy from CVS. But > already it is non-functional. Even if I follow the instructions in the > new fix-workspace, the compilation is totally screwed (seems to have > something with all utils classes disapearing). What broke? I tested this very carefully, but it is possible that I missed something. > Why can't we have a module for 3.0 that is easy to live with? Change can sometimes be difficult for some, yet evolution is a nessesity for a growing project to survive and thrive. --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
