I also wanted to mention that all of next week I'll be on vacation and while I'll be checking email, it probably won't be very regularly and I don't expect to be working on any James code.
California here I come! -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ Paul Hammant wrote: > Serge, > > OK thanks for backing down, coming clean re the need for the pub... ;-) > > Nonetheless, I'd like to offer my services to bring you completely up to > date with released Avalon comps. I'll also try to get a release of > Phoenix done (it moves a little each month) and of Cornerstone (has > hardly moved in months). I reckon it will take me a day to do. I'll > propose Saturday (if you guys can stay clear of the CVS). > I'd like to do it in this style > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/eob/eob/ where there is > greater separation between the jars that Phoenix needs and the jars that > JAMES needs. This will help a newbie see what is actually needed for > JAMES compilation. I am adept at build scripts and will leave you in a > position where all the targets (that work currently) continue to work. > What will follow, hopefully in a week or so would be the release > versions of the things that are release versions. What I have done with > EOB is take the Phoenix verison from CVS after a "build dist-lite" > build. The layout that gives is the same as that I have booked into CVS > of EOB. > > Of course, there is a lot to consider here. You have every right to > veto or decline, but the offer is tabled. > > Tonight, while you folks mull the offer, I am going to create a block > wrapper for this Tomcat wrapper :- > http://freshmeat.net/projects/mintc/?topic_id=92%2C259%2C250 > How would you feel about a web server in the same SAR file ? Another > day perhaps.... > > Regards, > > - Paul H > > >> 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. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
