Chris Pettitt wrote:
I was able to get the build working by making the change in this message: http://www.mail-archive.com/[EMAIL PROTECTED]/msg04406.html
Appearantly the problem is with the way the ClassLoader is obtained.
Thanks, Chris
Chris Pettitt wrote:
Due to some trouble with another component, I am upgrading my maven and maven-plugins to the latest in CVS. The build for both maven and maven-plugins went really smoothly and even had a bit of the cool factor (bootstrapping to build it in itself :)).
The problem I am having is with the maven hibernate plugin. In the past we were using the version that came with RC1 with no problem (I think it was called maven-hibernate-plugin-1.0-SNAPHOT). Once we moved to the new CVS and new hibernate plugin (now properly called 1.0-SNAPSHOT), I noticed that our schema-export is no longer working. Here is what Maven tells me:
BUILD FAILED
File...... file:/C:/Documents and Settings/Administrator/.maven/plugins/maven-hibernate-plugin-1.0-SNAPSHOT/
Element... h:schema-export Line...... 27 Column.... 53 net/sf/hibernate/UserType Total time: 13 seconds Finished at: Sat Nov 01 08:37:23 CST 2003
Our project has a dependency on hibernate 2.0.3 and the plugin has a dependency on hibernate 2.0 beta 6. Both are showing up in "maven.dependency.classpath" when I do maven -X jar. I also looked at both JARs and they both have the class that the plugin is looking for (net.sf.hibernate.UserType). I temporarily changed our build to use 2.0 beta 6 just to make sure there wasn't some odd classpath conflict, but I had no luck.
One other odd behavior is that each build displays the following at the begining:
Attempting to download maven-hibernate-plugin-1.0-SNAPSHOT.jar
We already have the plugin (I built it locally and installed it into our repository) and it is getting called during the build. We normally put specific versions on our dependencies, so maybe this is a side effect of having SNAPSHOT in the name? I have no idea, but though, maybe it is related.
Finally, I will include a call stack if that would be of any use.
Thanks, Chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
