Peter and Paul, Thank you for responding so calmly. Regardless of my points, I should have just walked to the nearby bar before writing that kind of a message, and I appreciate your positive responses.
I'm glad to see Avalon is making some releases. I see the latest in code James CVS reporting "Phoenix 4.0a4" and a bunch of timestamped avalon jars. I don't see where Avalon-Phoenix is "currently shipping a beta"... both freshmeat and jakarta show 4.0a1-a3 and latest. If there is a release, that's great and we should probably upgrade. On that note, what would really help me from Avalon would be concrete/complete releases. What I would like in a release would be a main jar, dependent jars, source code, javadocs, and ideally a branch in CVS. I'm used to drilling from James' code to Avalon-Phoenix to Avalon-Cornerstone, etc..., that's fine and expected... I like to do that and that's a big reason why I use open source. The problem is without clear releases, I have to setup timestamped checkouts of code from CVS, maybe generate my own javadocs, and otherwise always be uncertain if I'm checking the source and docs of what I'm actually running. Also, as it seems every other line of code in Avalon is dependent on another Avalon subproject, in these releases I would very much like to understand how these builds are made and with what dependencies. Are these being built with the latest of CVS in the other subprojects, or a particular release? It always worries me when I see how 2/3rds of the subprojects have made releases since there is so much interdependency. It seems at some point there could be a combined "Avalon" release for projects like James where we're using more than one or two modules. -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ Paul Hammant wrote: > Serge, > > As an Avalon advocate, who has none of the problems you mention before, > I think I should offer my help. Your cry for help is heard. > > At the risk of contradicting you, Avalon comps have been released : - > http://freshmeat.net/projects/avalon/?topic_id=810 > Avalon-Cornerstone has not. Avalon-Phoenix is currently shipping a beta. > > Regards, > > - Paul H > >> I don't know if I can take much more of Avalon. I've lost so much >> interest in working on James because of the problems that arise from >> using Avalon, and am nearing my last straw this afternoon. >> >> The latest problem with our use of Avalon is that if you have any open >> connections when you try to stop the JVM, it hangs and has to be >> forcibly stopped. I thought the whole reason behind migrating to >> Avalon was so that we didn't have to deal with underlying threading, >> configuration, object pooling, database sources, connection handling, >> logging, and other server related issues. Unfortunately, none of the >> features are implemented that wonderfully, the platform continually >> moves from one pre-alpha release to another, there are regular huge >> arguments on the dev mailing list about what latest pre-pre-alpha >> component should be added next to the already uncertain platform, and >> meanwhile the James project is stuck working again and again on stuff >> that was already working before we ported to Avalon years ago. >> >> Sorry, I'm just really really tired of this stuff. Since there aren't >> any real official releases of Avalon, should we just do another >> snapshot? Or maybe just branch the code, import it into James so we >> can gain control over our project again? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
