Re: [hibernate-dev] Failure building 5.1 branch

2016-05-07 Thread Vlad Mihalcea
Those were used only for testing and as a runtime dependency: testRuntime( libraries.oracle ) testRuntime( libraries.mssql ) So, I don't think there was any risk of distributing the drivers. The only inconvenent was that every env should have those drivers locally installed for the tests to

Re: [hibernate-dev] Failure building 5.1 branch

2016-05-07 Thread Sanne Grinovero
Remember the licensing terms. You can not distribute those drivers. On Sat, 7 May 2016, 14:30 Vlad Mihalcea, wrote: > Hi, > > I added those for testing, but now I realized that these could be missing > from Jenkins. > I'll add a Gradle condition to include the

Re: [hibernate-dev] Failure building 5.1 branch

2016-05-07 Thread Vlad Mihalcea
Hi, I added those for testing, but now I realized that these could be missing from Jenkins. I'll add a Gradle condition to include the oracle/mssql dependencies only when we supply the -Pdb=oracle/mssql runtime property. Vlad On Fri, May 6, 2016 at 9:30 PM, Steve Ebersole

Re: [hibernate-dev] Failure building 5.1 branch

2016-05-06 Thread Steve Ebersole
On master I just removed the mssql and oracle JDBC drivers. They should never have been added there. On Tue, May 3, 2016 at 5:42 PM Gail Badner wrote: > The command I'm using is: ./gradlew clean test > > I think I remember someone mentioning this on hibernate-dev mailing

[hibernate-dev] Failure building 5.1 branch

2016-05-03 Thread Gail Badner
The command I'm using is: ./gradlew clean test I think I remember someone mentioning this on hibernate-dev mailing list, but I can't seem to find it. Here is what I'm seeing: ... :documentation:processTestResources :documentation:testClasses :documentation:test :hibernate-c3p0:compileJava