[hibernate-dev] Build time downloads of ORM itself during an ORM clean build?
coladict at gmail.com
Wed Sep 21 10:43:59 EDT 2016
Well, the CI would generally have a local snapshot to use, instead of
The problem is that the package buildscripts depend on
'hibernate-gradle-plugin',but it depends on 'hibernate-core'.
I just cleared my ~/.gradle/caches and ~/.m2/repository/org/hibernate/,
switched to the '5.1' branch and it didn't download the core snapshot as it
does in 'master'.
As far as I can determine, this plugin enhances entity classes after
they're built, which I suppose is meant to speed-up the tests slightly.
2016-09-21 12:50 GMT+03:00 Sanne Grinovero <sanne at hibernate.org>:
> Hi all,
> I just happened to build Hibernate ORM's latest "master" on a clean
> machine and this is how the build log looks like:
> No compatible daemons found:
> - an idle daemon with different JVM constraints can't run this build
> Starting a new Gradle Daemon for this build: subsequent builds will be
> :buildSrc:clean UP-TO-DATE
> :buildSrc:compileJava UP-TO-DATE
> :buildSrc:processResources UP-TO-DATE
> :buildSrc:compileTestJava UP-TO-DATE
> :buildSrc:compileTestGroovy UP-TO-DATE
> :buildSrc:processTestResources UP-TO-DATE
> :buildSrc:testClasses UP-TO-DATE
> :buildSrc:test UP-TO-DATE
> :buildSrc:check UP-TO-DATE
> Download http://repository.jboss.org/nexus/content/groups/public/
> I'm not having any specific failure, but it seems very suspicious that
> the build is needing to download hibernate-core at the very beginning
> of the build?
> I'm not familiar enough with ORM's build scripts to investigate myself
> but I suspect some dependency order needs to be cleaned up, or you
> might be including some side-effects from previous builds.
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
More information about the hibernate-dev