Perhaps I'm missing something, but I don't see anything particularly inflammatory here. Maybe the priority level could be lowered. Maybe Jan could attach a patch. But, JIRA is the appropriate channel for new feature requests. If they're not in the design goals of the framework, they could be closed with reason.
I'd just urge everyone to relax a little bit and air grievances on the list rather than in JIRA, which is the inappropriate medium. Please note that this is not an endorsement either way on the issue at hand. -- Kevin On 3/12/08 8:50 AM, "Jesse Kuhnert (JIRA)" <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/TAPESTRY-2183?page=com.atlassian.jira.pl > ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577834#action_1 > 2577834 ] > > Jesse Kuhnert commented on TAPESTRY-2183: > ----------------------------------------- > > I just don't think you understand how open source works Jan. > > If it was really that important then you should: > > a) Make a go of portlet support yourself. > b) Have your company pay Howard to do it. > > The source is right there, so anyone can in theory jump right in and do it. > That's how it works. > >> Support Java Portlet Specification V2 - JSR-286 >> ----------------------------------------------- >> >> Key: TAPESTRY-2183 >> URL: https://issues.apache.org/jira/browse/TAPESTRY-2183 >> Project: Tapestry >> Issue Type: New Feature >> Components: Portlet >> Affects Versions: 5.0 >> Reporter: Jan Vissers >> Fix For: 5.1 >> >> >> Specification will be finished early 2008. We need a framework that allows us >> to write JSR-286 portlets, would be nice if we could stick with T5 for this. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
