Can anyone speculate as to when the initial build will be available? I thought I saw a post to the effect that there was a delay b/c of a licensing problem with an IBM jar - giving me the impression that it was otherwise all ready to go.
Days? Weeks? Months? Sometime after Doom 3? Hate to be cranky, but we're about to start to start a big new project, and would really rather be building against the new spec. > > I have seen the votes for creating a subproject for > Jetspeed 2. Could > > someone summarize how this will work? > > > > 1. Is the Jetspeed 2 code releasable to everyone now? > > AFAIK, the portlet API is in public draft, which means the license is > temporary (to be substituted by the "final" one). It can change after > the public draft phase. So, I would say that the status > (without going > into heavy legalese) should be considered as highly experimental > > > 2. If it is releasable, what steps need to be taken to make it > > available > > to everyone? > > checkout, build, test, patch iteratively until it works. ;-) > > > 3. Is there any information available describing the status of > > Jetspeed > > you mean Jetspeed-2? I don't think so, but we should document as soon > the code lands in CVS. > > > 2 (Since we can't see it yet)? > > a. How much of it is working? > > b. What parts are complete, what parts are not? > > > > think proof of concept (I hope David, Paul, Mark, Scott can be more > specific as it lands in CVS). > > > Sorry to pester the list with questions. I guess I'm just anxious to > > see > > it and at some point give it a try. > > > > Regards, > > > > James > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
