edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cazen Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-139) Adopt a build system, such as gradle, that supports transitive dependency management
Date Wed, 08 Jun 2016 02:58:21 GMT

    [ https://issues.apache.org/jira/browse/QUARKS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319894#comment-15319894

Cazen Lee commented on QUARKS-139:

Good Day [~dlaboss]

I believe that master branch can be merge with gradle branch without any problem in the current
However, the reasons that created the gradle branch are "workers are more than one person",
and "it will occurs a number of  PR", so I thought that it is better to create new one - easy
to share each other's work.(and I saw create a new branch when performing complex PR in other
Apache Project. I thought it was common to create a branch in a large-scale Issue)

However, as your advice, I think it is also good that puts the WIP state to master branch
and proceed in a stepwise manner work to the extent with it does not affect the 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

This message was sent by Atlassian JIRA

View raw message