You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Chris Mylonas (JIRA)" <ji...@apache.org> on 2014/10/01 09:33:34 UTC
[jira] [Commented] (TAP5-2392) Commons-IO scoped for test only,
causes HTTP/500 - no stack trace
[ https://issues.apache.org/jira/browse/TAP5-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154504#comment-14154504 ]
Chris Mylonas commented on TAP5-2392:
-------------------------------------
Reference mail thread: http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Update-from-5-4-beta-6-to-beta-22-IOUtils-ClassNotFound-td5728496.html
If i was a little more proficient with mvn this would have been over earlier.
> Commons-IO scoped for test only, causes HTTP/500 - no stack trace
> -----------------------------------------------------------------
>
> Key: TAP5-2392
> URL: https://issues.apache.org/jira/browse/TAP5-2392
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Chris Mylonas
> Priority: Minor
>
> Updating from 5.3.7 -> 5.4-beta-6 not so bad. Going to 5.4-beta-22, a requirement for commons-io when an exception occurs happens and a HTTP 500 page is shown.
> No stack trace is shown on command line after adding to maven - so not sure if that is ideal too.
> Added to my pom.xml
> <dependency>
> <groupId>commons-io</groupId>
> <artifactId>commons-io</artifactId>
> <version>2.4</version>
> </dependency>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)