Bug 769321

Summary: Tracker for inclusion of Gradle
Product: [Fedora] Fedora Reporter: Carlo de Wolf <cdewolf>
Component: distributionAssignee: Bill Nottingham <notting>
Status: CLOSED CURRENTRELEASE QA Contact: Bill Nottingham <notting>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: akurtako, dennis, mgoldman, puntogil, ricardo.arguello, rvokal, stliu
Target Milestone: ---Keywords: Tracking
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-15 11:25:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 809950    
Bug Blocks:    

Description Carlo de Wolf 2011-12-20 14:02:49 UTC
Please include a gradle package in Fedora.

http://gradle.org - Gradle, A better way to build.

Comment 1 Carlo de Wolf 2011-12-20 14:04:57 UTC
JBoss AS 7 currently uses Hibernate components for JPA, Bean Validation and other techs. Hibernate components currently use Gradle as their build tool.

Comment 2 Carlo de Wolf 2011-12-20 14:07:06 UTC
Currently Gradle downloads itself during build so it can build itself with itself. This leads to a chicken/egg problem as it should either use the local source or an alternative FOSS build tool.

http://forums.gradle.org/gradle/topics/bootstrapping_gradle_source_build_using_source_only

Comment 3 Ricardo Arguello 2012-01-02 07:23:38 UTC
We can create a "gradle-bootstrap" package with the Gradle binary distribution inside, and put "BuildRequires gradle-bootstrap" in the "gradle" spec.

I was reading the Debian package definition, and they are downloading the binaries in order to bootstrap!

More info:
http://anonscm.debian.org/gitweb/?p=pkg-java/gradle.git;a=tree
http://issues.gradle.org/browse/GRADLE-322

Comment 4 Carlo de Wolf 2012-01-02 15:20:12 UTC
I went for an alternate approach in https://github.com/wolfc/gradle. The idea is to re-create the distribution using ant (phase 0) and use that to build Gradle phase 1. Then use Gradle~1 to build the real Gradle.

Two branches:
- fedora16: try to get a clean bootstrap using ant
- code-quality: adding code-quality plugin

On the code-quality branch try:
$ cd bootstrap && ant && java -jar lib/gradle-bootstrap.jar -s

Observe interesting issues.

Comment 5 gil cattaneo 2012-08-10 10:54:43 UTC
hi
gradle 1.0 is "almost" ready
there are three problems which should be solved:
1) gradle maven plugin (this should be resolved in gradle 1.1 http://issues.gradle.org/browse/GRADLE-2210)
2) replace maven-ant-tasks (see RHBZ#723276 and RHBZ#798263), gradle build/requires with aether-ant-tasks (RHBZ#817533)
3) jmock 2.5.1, used for testing

Comment 6 gil cattaneo 2012-08-10 10:57:47 UTC
sorry wrong link 
this is the right one http://issues.gradle.org/browse/GRADLE-2238

Comment 7 gil cattaneo 2012-08-13 12:15:25 UTC
jmock 2.5.1 https://bugzilla.redhat.com/show_bug.cgi?id=847742

Comment 8 Marek Goldmann 2012-10-15 11:25:10 UTC
Gradle is in Fedora, closing.