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] [Updated] (QUARKS-139) Adopt a build system, such as gradle, that supports transitive dependency management
Date Sat, 11 Jun 2016 07:42:21 GMT

     [ https://issues.apache.org/jira/browse/QUARKS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cazen Lee updated QUARKS-139:
-----------------------------
    Description: 
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
- 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. ]

  was:
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
- Update build doc
- Java7 build support
- Android build support
- Release target, creating the target/… structure
- Junit parity
  - need top level aggregating report
- Javadoc parity
- 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. ]


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