Anyway, I got this to point I am pretty happy with. There is still the minor issue of jdbc3 and jdbc4 producing jars even though their classes are consumed into the core jar, but that's really just a minor annoyance (would be great if there were an option to not generate the jars at some point though I think).
http://www.jboss.org/community/wiki/Hibernate-JDBC4support http://in.relation.to/Bloggers/SimultaneouslySupportingJDBC3AndJDBC4WithMavenII Anyway, thanks again to Hans, Adam and Jason for all the help. On Fri, 2009-10-09 at 20:53 +1100, Adam Murdoch wrote: > > [email protected] wrote: > > We must be doing something wrong Adam. > > > > project structure: > > |____build.gradle > > |____core > > | |____src > > | | |____main > > | | | |____java > > |____jdbc3 > > | |____build.gradle > > | |____src > > | | |____main > > | | | |____java > > | | |____test > > | | | |____java > > | | | |____resources > > |____jdbc4 > > | |____build.gradle > > | |____src > > | | |____main > > | | | |____java > > | | |____test > > | | | |____java > > | | | |____resources > > |____settings.gradle > > > > Here are the build files > > [main] > > usePlugin 'java' > > > > jar { > > from this.project(':core').sourceSets.main.classes > > from this.project(':jdbc3').sourceSets.main.classes > > from this.project(':jdbc4').sourceSets.main.classes > > } > > > > I'm not sure why this doesn't work - I'll have to dig into this. > > In the meantime, a workaround is to add .asFileTree to the end of each > classes set: > > jar { > from project(':core').sourceSets.main.classes.asFileTree > .... > } > > -- Steve Ebersole <[email protected]> Hibernate.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
