/hi//
or obtain an
exception from FPC to build using prebuilt binaries. Currently Fedora
i don't
want use this approach,
ships Ant build.xml for Gradle, but it requires substantial amount
of
manual work to synchronize it with upstream build. (I would prefer to
use Maven here. It would not only ease dependency management, but also
allow easier installation of Gradle artifacts.)
/would be the same, because both with maven or ant must be generated for each artifact
a file properties, or more, that its contents can vary from one version to another
gradle-core 1.8
gradle-core-classpath.properties
#module definition
#Tue Sep 24 09:33:38 CEST 2013
projects=gradle-docs,gradle-base-services-groovy,gradle-resources,gradle-cli,gradle-native,gradle-base-services,gradle-messaging
runtime=groovy-all-1.8.6.jar,asm-all-4.0.jar,ant-1.9.2.jar,commons-collections-3.2.1.jar,commons-io-1.4.jar,commons-lang-2.6.jar,ivy-2.2.0.jar,logback-core-1.0.9.jar,logback-classic-1.0.9.jar,guava-11.0.2.jar,jcip-annotations-1.0.jar,jul-to-slf4j-1.7.2.jar,jarjar-1.3.jar,javax.inject-1.jar,slf4j-api-1.7.2.jar,log4j-over-slf4j-1.7.2.jar,jcl-over-slf4j-1.7.2.jar,ant-launcher-1.9.2.jar,jsch-0.1.46.jar
gradle-plugins.properties
#plugin definitions
#Tue Sep 24 09:33:50 CEST 2013
plugins=gradle-plugins,gradle-code-quality,gradle-jetty,gradle-antlr,gradle-wrapper,gradle-osgi,gradle-maven,gradle-ide,gradle-announce,gradle-scala,gradle-sonar,gradle-signing,gradle-cpp,gradle-ear,gradle-javascript,gradle-build-comparison,gradle-diagnostics,gradle-reporting,gradle-publish,gradle-ivy,gradle-jacoco,gradle-build-setup,gradle-language-jvm,gradle-language-base,gradle-build-setup
(this file properties are unusable because some modules are not importable,
e.g.
gradle-jetty use jetty 6.x
gradle-sonar use
https://bugzilla.redhat.com/show_bug.cgi?id=848096 == 3.2 and not newer
release)
That's a generic problem and it's not really Gradle-specific.
But yes,
there are some version problems, most notably Objectweb ASM. Different
Gradle dependencies use versions 3 and 4 (shaded to avoid namespace
conflicts). Fedora does not allow bundled libraries, which causes
conflict between ASM 3 and 4. (Porting from ASM 3 to ASM 4 is possible,
but non-trivial as there were major changes. This would again require
some work.)
solved ... i think ... see
http://pkgs.fedoraproject.org/cgit/gradle.git/tree/gradle-1.7-asm3.patch?...
To sum up, Gradle maintainence requires substantial amount of work.
Currently only few packages in Fedora are using Gradle which means that
maintenance costs of Gradle outweight costs of porting other packages to
different build systems.
regards
gil
/Polyglot
Maven/https://bugzilla.redhat.com/show_bug.cgi?id=855331