On Sep 9, 2009, at 6:40 PM, Jason Porter wrote:
Never mind, I got it. Added another configuration and then added that
configuration to the war.
In the future Gradle will allow to define custom version conflict
strategies. That would provide another solution for this problem (e.g.
in your case one could define a custom rule that hibernate validator
version conflicts are ignored).
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
On Wed, Sep 9, 2009 at 09:51, Jason Porter <[email protected]>
wrote:
I'm playing around with Hibernate Validator 4 in a Seam 2.2 project.
Emmanuel Bernard said to include both version 3.1 and 4.0 to get
around a NoClassDefFound issue. I'm using Gradle as the build and
dep
management tool. Is there a way to force both versions to be
available?
--
Jason Porter
Real Programmers think better when playing Adventure or Rogue.
PGP key id: 926CCFF5
PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5
PGP key available at: keyserver.net, pgp.mit.edu
--
Jason Porter
Real Programmers think better when playing Adventure or Rogue.
PGP key id: 926CCFF5
PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5
PGP key available at: keyserver.net, pgp.mit.edu
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
