Hi David, I completely agree with Hema and Jeff. I for one really need this combination going since this is going to be production software...otherwise I'm hosed. My vote also would be to not deprecate Fusion.
I'm all for trying anything to get Jetspeed 1 with Fusion going. The news you gave us was very disappointing and unfortunate. I have been watching the mailing list for long (since that was the lifeline for me when I was working with 1.5 and now with Fusion) and I have seen how your contribution has been and I know it was valuable to me. Based on what you said I think at least get Jetspeed 1.6 out (since that is quiet stable and we do not have to worry about building it) and then next try to get the developers to test fusion. If that is not possible then release the binaries for fusion that are in M1 which work with Jetspeed 1.6....so at least we are not lost. Also list out the known issues with Fusion so that we can get them addressed...somehow. There are a lot of people who are using 1.5 /1.6 and still need support. We and those people cannot be left in a lurch. I personally would at least try appealing to the developers to test Fusion and see if they can get that going. Thanks David for your replies. At least we know where we stand. And If you want we can all vote you in to show how valuable your contribution is...;-) Regards, Archana -----Original Message----- From: Hema Menon [mailto:[EMAIL PROTECTED] Sent: Thursday, March 10, 2005 1:52 PM To: Jetspeed Users List; [EMAIL PROTECTED] Subject: Re: Jetspeed 1.6-Fusion HELP!!!! David, I too would like to echo what Jeff is talking about. For us too, Fusion was a must to get our struts portlet running, otherwise we were very much happy with what Jetspeed 1.5 offered. We are not yet ready to move to JS2, due to the changes from JS1.5. So Fusion is doing for us what JS2 has in the offing. My vote would be to not deprecate Fusion. P.S - Sorry to hear about your disappointment. We, the users of Jetspeed value your and the contributions of the developers here at Jetspeed, very much. Thanks. Thanks, Hema On Thu, 10 Mar 2005 13:43:04 -0600, Jeff Sheets <[EMAIL PROTECTED]> wrote: > David, > > I definitely vote to support Fusion. My reasoning is that Jetspeed 1 > is much more stable and complete than Jetspeed 2, even if the > architecture is lacking. With Jetspeed 1 and the JSR 168 capabilities > of 1.6 Fusion, we would have everything we need until 2 if finally > finished. > > And I see I was not correct about the build being ok. After checking > out the use-fusion.xml file, I see that Jetspeed 1 builds with the > Jetspeed 2 M1 files that were still cached in Maven. Switching this > to M2-dev does break the build. > > I, for one, highly value your work on Fusion. Without Fusion, we > would have found another portal to work with, because JSR-168 is a > high priority item for our portlets. > > Thank you, > -- Jeff > > On Thu, 10 Mar 2005 10:52:54 -0800, David Sean Taylor > <[EMAIL PROTECTED]> wrote: > > Archana Turaga wrote: > > > Thanks for the reply Jeff. But I know in the past they have said that > > > when Jetspeed 1.6 is released you do not need to build Jetspeed 2.0. > > > Won't that be really convenient...if it works that way? > > > > The 1.6 release will only require jars from Jetspeed 2.0 > > If that is M1 or M2 is yet to be determined... > > > > -- > > David Sean Taylor > > Bluesunrise Software > > [EMAIL PROTECTED] > > [office] +01 707 773-4646 > > [mobile] +01 707 529 9194 > > > > --------------------------------------------------------------------- > > 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] > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hema Menon --------------------------------------------------------------------- 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]
