Il 12/11/2013 15:45, Marek Goldmann ha scritto:
As a follow-up to this mail:
The only package that required Gradle was Hibernate. Recently (thanks
to Gil) I migrated it from Gradle back to Maven. It works perfectly
and is way easier to maintain now. You can see the spec file here:
http://pkgs.fedoraproject.org/cgit/hibernate.git/tree/hibernate.spec
I've opened a bug report to retire Grade in Rawhide and in Fedora 20:
https://bugzilla.redhat.com/show_bug.cgi?id=1029534
--Marek
thanks to you
work on this now...
regards
gil
p.s. there is also latest groovy release (2.1.x) need gradle (circular
dep ...?...)
On 21.10.2013 17:11, Michael Ekstrand wrote:
In bug #976330[1], there's been some discussion of the desire to
upgrade Gradle from 1.0 to a new version (currently 1.8), and that
there is significant hassle to actually do so. Some of this hassle I
see in the bugs blocking 976330 - upgrading to Aether, newer Plexus
containers, and maybe Polyglot Maven.
What are the key issues that make it difficult to upgrade and maintain
Gradle in Fedora? The likely ones I see:
- Incompatible dependencies (Gradle may require package versions no
longer shipped in Fedora)
- Bootstrapping problems (the Gradle 1.8 sources won't build with
Gradle 1.8, they seem to require 1.7)
- Possibly library embedding (although the Gradle sources do seem to
pull in the dependencies from Maven)
and newer release use objectweb-asm4, but only for Fedora (maybe also
for other distros e.g. Mageia) is not possible use groovy without
bundled objectweb-asm3 commos-cli and antlr libraries (groovy-all see
Debian package)
1. https://bugzilla.redhat.com/show_bug.cgi?id=976330
--
java-devel mailing list
java-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/java-devel
begin:vcard
fn:gil
n:;gil
email;internet:puntogil@xxxxxxxxx
version:2.1
end:vcard
--
java-devel mailing list
java-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/java-devel
