Mailing-List: contact dev-help@quarks.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@quarks.incubator.apache.org
Date: Wed, 15 Jun 2016 16:38:09 +0000 (UTC)
From: "Daniel John Debrunner (JIRA)" <jira@apache.org>
To: dev@quarks.incubator.apache.org
Message-ID: <JIRA.12957858.1460408146000.6748.1466008689557@Atlassian.JIRA>
In-Reply-To: <JIRA.12957858.1460408146000@Atlassian.JIRA>
References: <JIRA.12957858.1460408146000@Atlassian.JIRA> <JIRA.12957858.1460408146830@arcas>
Subject: [jira] [Commented] (QUARKS-139) Adopt a build system, such as
 gradle, that supports transitive dependency management
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 15 Jun 2016 16:38:16 -0000


    [ https://issues.apache.org/jira/browse/QUARKS-139?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1533=
2043#comment-15332043 ]=20

Daniel John Debrunner commented on QUARKS-139:
----------------------------------------------

One of the main reasons for this was to remove the ext jar files from the c=
ode tree. It would seem that this is possible now with the gradle build, so=
 I wonder if the ant build could continue to be used for a while but build =
the jars using gradle (e.g. ant calls out to gradle).

That would then put a subset of the TODO items as higher priority, while le=
aving things like junit and jacoco , java7 android still working with ant.

I think the TODO list would then just be:

* Update build doc
* add manifest classpath entries
* Release target (Java 8 structure with ext files under target)
* remove ext jars from repo.

> Adopt a build system, such as gradle, that supports transitive dependency=
 management
> -------------------------------------------------------------------------=
-----------
>
>                 Key: QUARKS-139
>                 URL: https://issues.apache.org/jira/browse/QUARKS-139
>             Project: Quarks
>          Issue Type: Improvement
>          Components: Analytics, API, Applications, Connectors, Console, D=
ocumentation, Miscellaneous, Runtime, Samples, Test, Utils
>            Reporter: Lance Feagan
>            Assignee: Dale LaBossiere
>              Labels: build
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> By moving to a build system that supports transitive dependency managemen=
t, the repository size can be decreased and users can more easily integrate=
 quarks with their own applications by allowing the version of a dependency=
 to float within an acceptable range, assuming proper semantic versioning o=
f the dependencies.
> [~bjhargrave] has created the initial set of gradle files with PR-131.  T=
he gradle work is still WIP.  The existing build mechanisms are still in pl=
ace and are to be used.
> TODOs
> - Add license headers to gradle files - QUARKS-203
> - Update build doc
> - Java7 build support
> - Android build support
> - Release target, creating the target/=E2=80=A6 structure - QUARKS-204
> - Junit parity
>   - need top level aggregating report
> - Javadoc parity - QUARKS-205
> - Jacoco parity
> - building from Eclipse
>   - .classpath files have refs to ext jars that will be removed from the =
repo
> - switch travis-ci to gradle
> - cleanup
>   - remove ext jars from repo. =20
>     Question: ext contains LICENSE/NOTICE/README files. =20
>       Note needed anymore as Quarks repo won=E2=80=99t contain the jars?
>       Just want something in README.md or such to list the dependencies?
>   - remove the ant build related files
> [ Original from [~lfeagan]
> I have an initial set of work for this effort completed using gradle. Nea=
rly all sub-projects build at this time--the notable exception being the an=
droid-dependent sub-projects. The other notable missing element is the inte=
gration of JaCoCo. In both cases, these should be simple additions. ]


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)