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] [Comment Edited] (QUARKS-139) Adopt a build system, such as gradle, that supports transitive dependency management
Date Mon, 13 Jun 2016 13:04:21 GMT

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

Cazen Lee edited comment on QUARKS-139 at 6/13/16 1:04 PM:
-----------------------------------------------------------

Hi [~dlaboss] :)
License issue is sensitive. 
Further discussion is surely necessary, but I think we should proceed with http://www.apache.org/legal/resolved.html
if we remove the ext folder.
I guess the final schema of our license schema of repo will be one of the following:
- Put together into one folder(Like Apache Spark - https://github.com/apache/spark/tree/master/licenses)
- Put together into one file(Like Apache Hive - https://github.com/apache/hive/blob/master/LICENSE)

Please advise me if there is a better way. It would be a great help to me :)


was (Author: cazen):
Hi [~dlaboss] :)
License issue is sensitive. 
Further discussion is surely necessary, but I think we should proceed with http://www.apache.org/legal/resolved.html
if we remove remove the folder.
I guess the final schema of our license schema of repo will be one of the following:
- Put together into one folder(Like Apache Spark - https://github.com/apache/spark/tree/master/licenses)
- Put together into one file(Like Apache Hive - https://github.com/apache/hive/blob/master/LICENSE)

Please advise me if there is a better way. It would be a great help to me :)

> 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)

Mime
View raw message