Hi Ed,
I think I may know what's going on.
Did you deploy the same version of bean-validator with a different
artifact to the remote maven repo?
The bean-validator artifact is different between the java.net/maven/2
and Nexus:
http://download.java.net/maven/2/org/glassfish/bean-validator/3.0-JBoss-4.0.1/
http://maven.glassfish.org/content/groups/glassfish/org/glassfish/bean-validator/3.0-JBoss-4.0.1/
v3 references Nexus server so it's downloading the old bean-validator
artifact. I can fix this by refreshing the bean-validator cache on
Nexus. Nexus is a proxy of the Maven repositories used to build v3.
Like your local maven repository, it caches the artifacts and it will
not download any new artifacts unless there is a new version.
Please do not deploy the same version with different artifact.
Thanks,
Jane
Jane Young wrote:
> Hi Ed,
>
> Hudson continuous build is getting the StackOverflowError and it uses
> a clean maven repository.
> http://gf-hudson.sfbay/hudson/job/gf-trunk-build-continuous/2832/console
>
> BTW: I've reverted your commit (r32852) so builds are back to normal
> on Hudson.
>
> Jane
>
>
> Ed Burns wrote:
>> Please rm -rf ~/.m2/repository/org/glassfish/bean-validator and start
>> the build again.
>>
>> This is due to an error in the bean validator pom file that I checked in
>> two days ago and have since fixed.
>>
>> Ed
>>
>
>