[
https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789426#comment-13789426
]
Pieter Schoenmakers commented on TAP5-64:
-----------------------------------------
Separate jar is what I'd expect; you don't want to force portlet.jar upon
everybody.
Out of the box, as in documented and provided on tapestry.apache.org just like
all tap5 jars.
(I'm still maintaining a tap4-based portlet app and I would love to migrate to
tap5.)
> 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)
