Thanks for the exemplary investigative approach, simple or otherwise :)
On Wed, 01 Oct 2014 21:48:00 +1000, Lance Java
wrote:
I looked on maven central for the release dates
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.tapestry%22%20AND%20a%3A%22tapestry-core%22
Then I fol
I looked on maven central for the release dates
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.tapestry%22%20AND%20a%3A%22tapestry-core%22
Then I followed your exception stack trace to ExceptionReporterImpl and
looked up the history on github
https://github.com/apache/tapestry-5/com
where/how'd you find this out btw?
sounds like a good way to move with the times.
On Wed, 01 Oct 2014 18:21:27 +1000, Lance Java
wrote:
Ah, found it. Beta6 was added to maven central on 15 may.
ExceptionReporterImpl was created 30th may.
On 1 Oct 2014 09:11, "Lance Java" wrote:
I still
Ah, found it. Beta6 was added to maven central on 15 may.
ExceptionReporterImpl was created 30th may.
On 1 Oct 2014 09:11, "Lance Java" wrote:
> I still can't see how this was working on beta-6 since commons-io has the
> same "test" scope.
>
I still can't see how this was working on beta-6 since commons-io has the
same "test" scope.
Umm
On Wed, 01 Oct 2014 17:00:00 +1000, Kalle Korhonen
wrote:
I'm totally confused about this thread. Why don't you just add commons-io
as a dependency of your project
OK done - fixes my HTTP/500 message and I get the nice exception page.
No stack trace on command line still thoug
I'm totally confused about this thread. Why don't you just add commons-io
as a dependency of your project and file an issue that commons-io is
incorrectly declared as test scoped dependency to T5?
Kalle
On Tue, Sep 30, 2014 at 11:17 PM, Chris Mylonas wrote:
> (gosh i'm a liar, i found time to t
(gosh i'm a liar, i found time to try it out some more)
AND I GOT IT!
tapestry-hibernate project, pretty plain, one entity, one service
interface one implementation binder.bind() used.
Page class does NOT have @CommitAfter on the onSuccess() method.
Instead I have it on the serviceImpl for cr
Can you include the commons-io snippets from both versions (including
parent hierarchy).
I never use commons-io directly (even unknowningly), it's just plain old
tapestry. This is the part that spins me out.
-
To unsubs
Hi All,
I had it happen in a fresh tapestry-hibernate project for demo, cut it
down to one entity and CRUD page classes, can't get it to happen again.
I had my hibernate sesion in the tapestry service, it was complaining
about nested transactions in this instance, but kicked itself with IOU
I'm working on a fresh share-able example following my previous workflow -
if it breaks, we can fix it. If it doesn't there's something wrong with
my other project.
Will be a few hours, I'm learning nodejs stuff at the same time.
On Tue, 30 Sep 2014 17:42:17 +1000, Lance Java
wrote:
So, have you solved this yet?
If it breaks by switching from beta6 to beta22 can you run "mvn
dependency:tree" in both cases?
Can you include the commons-io snippets from both versions (including
parent hierarchy).
Am 28.09.14 um 03:54 schrieb Chris Mylonas:
Are you using persitence?
Yes in EJB, eclipse link.
I spent some hours porting a bash scripts code generator to nodejs
yesterday and nearly finished but won't get to it again for today.
I'll be able to do more accurate troubleshooting on this issue
>
> Are you using persitence?
Yes in EJB, eclipse link.
I spent some hours porting a bash scripts code generator to nodejs
yesterday and nearly finished but won't get to it again for today.
I'll be able to do more accurate troubleshooting on this issue then, using
standalone tapestry-hibernate a
Am 25.09.14 um 04:54 schrieb Chris Mylonas:
Hi T54Beta People,
As subject says, updated my pom got an error on deployment.
Changing back to beta-6, error goes away.
Google and some 54 release notes don't mention IOUtils or commons that
I've found.
mvn clean install
Deploy to glassfish 3.1.2.2
Yeah OK that's a good point. So is it a tapestry maven error or a chris
maven error, because I've only updated from beta-6 to beta-22and
maaaybe at the same time contributeExceptionReporterStuffInAppModule
Chris (phone)
On 26/09/2014 7:40 am, "Thiago H de Paula Figueiredo"
wrote:
> The err
The error message is pretty clear about ExceptionReporterImpl from Tapesry
using IOUtils from Commons-IO, but IOUtils not being in the classpath.
This means Commons-IO isn't in the classpath for some reason. This is a
Maven configuration error, not a Tapestry one.
On Thu, 25 Sep 2014 01:52:
And in case you really wanted the dependency:tree from the root of the
project, for completeness, here it is: no commons-io anywhere.
Mylos-MacBook-Air:MetwideWebsite mylo$ mvn dependency:tree
[INFO] Scanning for projects...
[INFO]
--
Yeah it's a multi-module project, and doing mvn dependency:tree from the
web module (tapestry-beta-22)
One can see commons-io in with selenium stuff for testing.
[INFO] org.opencsta:website.metwide:war:1.0-SNAPSHOT
[INFO] +- org.opencsta:WebsiteMetwide-ejb:jar:1.0-SNAPSHOT:provided
[INFO] +- jav
Try
mvn dependency:tree
from the command line.
Perhaps your provided dependency is preventing commons-io from being added
to the classpath.
If 2 poms declare the same dependency, the "nearest definition wins".
On 25 Sep 2014 03:54, "Chris Mylonas" wrote:
> Hi T54Beta People,
>
> As subject say
I'm not sure but it looks like an internal Class for Tapestry's use. You
shouldn't use Tapestry's "internal" classes. However you can use Apache's
commons IO utils instead. Hopefully you'll get the same functionality you
were using.
commons-io
commons-io
2.4
*-*
*Muhammad G
21 matches
Mail list logo
