Same issue here, i've updated the JIRA issue with some comments
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/component-report-failing-tp2436431p3331539.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
--
https://issues.apache.org/jira/browse/TAP5-1302
I marked it as both 5.1 and 5.2, although I'm not 100% sure that it actually
happens in 5.2, I don't have a running 5.2 version right now...
On Mon, Oct 11, 2010 at 10:52 AM, Inge Solvoll wrote:
> Anyone planning on fixing this? The component repo
Anyone planning on fixing this? The component reports are crucial as
developer documentation!
It fails for me in both 5.1.0.5 and 5.2
On Fri, May 7, 2010 at 1:11 PM, Ulrich Stärk wrote:
> That's so annyoing. Happens with Maven 2.0 as well as with 2.2.
>
>
> On 07.05.2010 09:04, Igor Drobiazko w
That's so annyoing. Happens with Maven 2.0 as well as with 2.2.
On 07.05.2010 09:04, Igor Drobiazko wrote:
No problems here.
On Thu, May 6, 2010 at 11:10 AM, Ulrich Stärk wrote:
Hey guys,
somehow the tapestry-component-report in 5.2-SNAPSHOT is failing for me
(see stack trace below). Has an
No problems here.
On Thu, May 6, 2010 at 11:10 AM, Ulrich Stärk wrote:
> Hey guys,
>
> somehow the tapestry-component-report in 5.2-SNAPSHOT is failing for me
> (see stack trace below). Has anyone else seen this? I believe that there's a
> problem with the dependencies but before changing them I