Werner Guttmann wrote: > > Thanks, Bruce. It does, at least for now. You might have seen the "Plea for info ..." > thread on castor-dev, where me and two colleagues of mine are trying to establish >whether > major bugs (or "change requests", as Thomas calls them) will get resolved in the near > future (based on messages found in the archives about 8 months ago).
What I can tell you is that Thomas used to be employed by Intalio to work on Castor full-time. Unfortunately, his situation has changed so that his duties at Intalio require his full-time attention rather than Castor. Currently, Thomas can only work on Castor part-time (and mostly in his own spare time at that) and that has affected many other things to do with the project. > I guess we are just afraid that we will have to abandon Castor as one of our tools >to use > as our expectations towards bug resolution(s) have not been met. Now I know that >Castor > is open-source, but Thomas has made it very clear that he doesn't appreciate more > developers due to ongoing refactoring. I think that Thomas, and everyone else involved, truly appreciates others wanting to help out in any way they can. However, please understand that Thomas doesn't necessarily make these decisions on his own. All I'm saying is, please don't kill the messenger, if you know what I mean. > It's just a bit of a dilemma we are facing here, and we are trying to find a way to > > a) help you fixing this one particular problem. > b) help you identifying the problem (but it seems like Thomas exactly knows what the > problem is anyway) > c) get an idea what the problem really is (whether it's just a problem with the OQL >Query > builder) > d) etc. Thomas did state that if someone submits a patch for this issue, he would take the time to review it. You also state above that you're more than willing to help resolve the issue. That being the case, I would encourage you to get involved. Dig right into the source and start to debug the problem (I like to use BugSeeker (http://www.karmira.com/) for faster debugging than System.out.println). Start to create a fix and submit it to the list so that it can be properly reviewed. A good example of this is in the following thread: http://castor.exolab.org/list-archive/msg13211.html Alan wanted Castor to accept and use object instances from an external pool, which Castor did not support. So he asked how he might go about submitting his own changes to make Castor support this functionality. As it currently stands, his patches have been reviewed by Thomas and they are tweaking a few final things before being committed to CVS. BTW, this all really took place this past weekend - rather quick action. Please submit any questions you might have to the list and we'll help out as best we can. I hope this helps you understand the situation a little more. Bruce ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
