[
https://issues.apache.org/jira/browse/QUARKS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313019#comment-15313019
]
BJ Hargrave commented on QUARKS-139:
------------------------------------
I'd like to get involved in this. I have lots of experience with gradle builds.
I converted the builds for OSGi and bnd/bndtools from ant to gradle. I also
developed the bnd gradle plugin which is useful for adding OSGi metadata to
bundles. Having OSGi metadata will be needed to use the code in OSGi systems
like Eclipse Kura.
So is the gradle branch the central work location for developing a gradle build?
> 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
> 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.
> 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)
