[
https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789367#comment-13789367
]
Thiago H. de Paula Figueiredo commented on TAP5-64:
---------------------------------------------------
Hello, Pieter!
What do you mean by out-of-the-box portlet support? As in tapestry-core itself?
I'm sorry, that's not going to happen. Not everybody which uses Tapestry uses
portlets, so it doesn't make much sense to put support for it in core. The
Tapestry philosophy is to have the basic functionality in tapestry-core and
more specific stuff in other JARs, such as tapestry-upload and
tapestry-hibernate.
If it's about a separate JAR under the Apache Tapestry project,
tapestry5-portlet is mostly written by Tapestry committers themselves. In
addition, we avoid having too much stuff under the Tapestry project itself
because we're all volutaries and we'd need to support that code.
I agree with you that tapestry5-porlet should have its JAR in Maven Central
Repository.
Cheers!
> Support Java Portlet Specification V2 - JSR-286
> -----------------------------------------------
>
> Key: TAP5-64
> URL: https://issues.apache.org/jira/browse/TAP5-64
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Reporter: Jan Vissers
> Assignee: François Facon
> Attachments: tapestry_portlet_5.0.15.zip,
> tapestry_portlet_5.0.18.zip, tapestry_portlet_5.1.0.5.zip
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
