[sakai2-tcc] Proposal: Switch to Tomcat 7 for Sakai 2.9

[Matthew Jones]

I haven't researched the meaning of the versions (5.5 verses 6 verses 7)
yet. Is this anything like other projects where one version is considered
more stable than others (at least as far as production is concerned) and
others are have more experimental features in them? Usually when something
is under active development, it's not necessarily a good thing and taking
the version (-1) that's been run for awhile might work out better or at
least be easier to justify to an operations team.

The question would this would lead to is (hypothetically) if we ended up
seeing that Tomcat 6 was a better choice for 2.9, and Tomcat 7 for 2.10,
then would this be twice the work? I know we're going to have to do some
library upgrades and significant testing either way. It's probably not worth
doubling up on the effort if a case can be made to just go straight to 7.

This is probably the question a lot of schools have with Sakai as well.
(i.e.Should I upgrade to 2.7 or just wait until 2.9?)

-Matthew

On Sun, Apr 10, 2011 at 7:31 PM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> p.s. If you want to read about the Tomcat 7 trials last week:
> https://steveswinsburg.wordpress.com/2011/04/07/sakai-runs-in-tomcat-7/
>
> I just updated it then with a comment about the tools that fail and their
> stacktraces.
>
> cheers,
> Steve
>
> On 11/04/2011, at 9:30 AM, Steve Swinsburg wrote:
>
> > Hi,
> >
> > After some successful trials last week and discussions with other active
> developers in the Sakai community, I'd like to propose that we starting
> thinking about switching to Tomcat 7 in time for Sakai 2.9.
> >
> > This effectively means we make the switch now so we can iron out any
> bugs. I have confirmed that some JSF based tools do not startup, and the
> stacktraces are rather cryptic. Someone that knows something about JSF will
> need to take a look. Samigo also fails but its stacktrace is more promising
> which hopefully means it can be resolved. This could be the first to be
> fixed so we know where the issue is with the others, perhaps.
> >
> > But with enough time these should be able to be resolved. No other
> changes should be necessary so we could back this change out at some
> predetermined date in the future if these issues cannot be resolved in time.
> >
> > What are your thoughts?
> >
> > By the way, the same configuration changes and issues are in Tomcat 6 as
> well so we might as well skip that version and focus our efforts where the
> Tomcat developers have their efforts focused as well, ie TC7.
> >
> >
> > cheers,
> > Steve
> >
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110410/dd34e5a3/attachment.html