Hello all,
Thanks for your replies Thiago and Daniel!
Absolutely correct on Thiago's part though it isn't 5.3.x but 5.4-beta-3!
The culprit is Tynamo's tapestry-security in this case. I overlooked this
multiple times
while checking through my Maven Dependencies due to the 5.4-beta-13 and
5.4-beta
On Wed, 25 Jun 2014 09:00:23 -0300, Daniel Jue wrote:
My intuition says the same thing. Try forcing a mvn clean or the
equivalent.
My intuition says something a little different: some library has a
dependency on Tapestry 5.3.x, so it ends up in the classpath.
--
Thiago H. de Paula Figuei
My intuition says the same thing. Try forcing a mvn clean or the
equivalent.
On Jun 25, 2014 7:57 AM, "Thiago H de Paula Figueiredo"
wrote:
> On Wed, 25 Jun 2014 08:46:45 -0300, Peter Hvass wrote:
>
> Digging further I discovered RegistryBuilder and output during startup
>> looks like;
>>
>> [
On Wed, 25 Jun 2014 08:46:45 -0300, Peter Hvass wrote:
Digging further I discovered RegistryBuilder and output during startup
looks like;
[INFO] ioc.RegistryBuilder Adding module definition for class
org.apache.tapestry5.ioc.modules.TapestryIOCModule
[INFO] ioc.RegistryBuilder Adding module de
On Wed, 25 Jun 2014 08:21:15 -0300, Peter Hvass wrote:
Hi guys,
Hi!
Whenever I try to run my projects now I'm getting errors from
HibernateModule saying it can't find x or y Tapestry internal services
(i.e.: PersistentFieldManager, DashboardManager,
ClasspathAssetAliasManager, TemplateParse
Digging further I discovered RegistryBuilder and output during startup
looks like;
[INFO] ioc.RegistryBuilder Adding module definition for class
org.apache.tapestry5.ioc.modules.TapestryIOCModule
[INFO] ioc.RegistryBuilder Adding module definition for class
org.apache.tapestry5.hibernate.modules.H
