Thanks Uli - I was just about to email that I got to the bottom of it.  The
problem was that I had some pom entries that were pulling in
persistence-api-1.0.jar, which was clashing with the hibernate upgrade in
tapestry-hibernate, in particular:

[INFO] +- com.trg:trg-dao-hibernate:jar:0.5.1:compile
[INFO] |  +- com.trg:trg-dao:jar:0.5.1:compile
[INFO] |  |  \- com.trg:trg-search:jar:0.5.1:compile
[INFO] |  |     \- javax.persistence:persistence-api:jar:1.0:compile

I just added an exclusion:

                    <exclusions>
                        <exclusion>
        
<groupId>javax.persistence</groupId>
        
<artifactId>persistence-api</artifactId>
                        </exclusion>
                    </exclusions>

... to the trg-dao-hibernate dependency.

Not sure why they weren't pulled in when I ran build from the command line -
think the magical (scope not updated to compile) message may have something
to do with it (some optimisation / checking that wasn't occurring with the
eclipse / maven / jetty plugin.

When maven bombs it really bombs - I've been looking at this for hours ...!
Thanks.

Regards,
Jim.

-----Original Message-----
From: Ulrich Stärk [mailto:u...@spielviel.de] 
Sent: 03 June 2010 11:14
To: Tapestry users
Subject: Re: java.lang.NoSuchMethodError:
javax.persistence.UniqueConstraint.name()Ljava/lang/String

I remember having to completely clean my project (under project -> clean)
from time to time because 
of similar errors.

HTH,

Uli

On 03.06.2010 11:45, Jim O'Callaghan wrote:
> I'm getting the error above on startup since pulling the latest and
greatest
> T5.2.0 snapshot - quite a long stack trace but I see this has been on the
> list before at:
>
>
>
>
http://tapestry.markmail.org/message/3c7uyc67oirmernp?q=UniqueConstraint+NoS
> uchMethodError
>
>
>
> The solution isn't listed though - can anyone elaborate on it?  Currently
I
> have maven building fine from the command line but the NoSuchMethodError
is
> pops up when using the mavan plugin with Eclipse, though both appear to be
> using the same pom and local repo.   I'm sure there is some difference but
I
> haven't found it yet - if anyone could recall the clash that caused a
> similar problem it would really save me some time - thanks.
>
>
>
> That's what I get for not using maven in offline mode ...!
>
>
>
> Regards,
>
> Jim.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to