edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-139) Adopt a build system, such as gradle, that supports transitive dependency management
Date Wed, 15 Jun 2016 16:38:09 GMT

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

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

One of the main reasons for this was to remove the ext jar files from the code 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 leaving 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, 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