[
https://issues.apache.org/jira/browse/QUARKS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328038#comment-15328038
]
BJ Hargrave commented on QUARKS-139:
------------------------------------
The main description for this issue is holding the TODOs. But a wiki page could
also work.
Looking at the current ant build, analytics.math3 has:
Class-Path: ../../../lib/quarks.api.topology.jar ../ext/commons-math3-
3.4.1/commons-math3-3.4.1.jar ../../../ext/google-gson-2.2.4/gson-2.2.4.jar
../../../ext/slf4j-1.7.12/slf4j-api-1.7.12.jar
../../../ext/metrics-3.1.2/metrics-core-3.1.2.jar
Building a Class-Path to the built jars would be straight forward but to
include the external dependencies would be a bit more complicated since the
build logic will need to pull the jars out of the gradle file cache into a
folder in the distribution folder. I think it can be done if the goal it to
build and fully self-contained distribution.
> 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,
> Documentation, 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 management,
> 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 of the
> dependencies.
> [~bjhargrave] has created the initial set of gradle files with PR-131. The
> gradle work is still WIP. The existing build mechanisms are still in place
> 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/… 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.
> Question: ext contains LICENSE/NOTICE/README files.
> Note needed anymore as Quarks repo won’t 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. Nearly
> all sub-projects build at this time--the notable exception being the
> android-dependent sub-projects. The other notable missing element is the
> integration of JaCoCo. In both cases, these should be simple additions. ]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
