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]
