I see,
but what is the strategy if there is a feature request for tapestry
which is covered by a third party module already? Could it still be that
it will be reimplemented to tapestry-core or will the feature-request
most of the time be referred to the third party module?
From framework usa
That's part of the reason why we're setting up Tapestry360
(http://tapestry.formos.com), as a secondary space for Tapestry
projects that can't be part of the project distribution itself, while
providing a more consistent set of resources (Bamboo CI, JIRA,
Confluence Wiki).
On Mon, Feb 2, 2009 at 2
Hi,
what is the general strategy for tapestry when it comes to using own
modules vs. adding "similar-behaving" third party ones?
take the sample, where I need a asset-type which is based on URL
(currently tapestry supports only context and relative path). As
mentioned in https://issues.apach
