[ https://issues.apache.org/jira/browse/EDGENT-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dale LaBossiere updated EDGENT-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 EDGENT-240 [TODO final updates when flipping the switch] - Java7 build support EDGENT-240 - Android build support EDGENT-240 - add manifest classpath entries EDGENT-240 - Release target, creating the target/… structure - QUARKS-204, EDGENT-240 - Junit parity - QUARKS-223, QUARKS-237, QUARKS-239 - need top level aggregating report - Javadoc parity - QUARKS-205 - Jacoco parity - QUARKS-237 - building from Eclipse - EDGENT-251 - .classpath files have refs to ext jars that will be removed from the repo - switch travis-ci to gradle - EDGENT-252 (mostly done) - 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 - QUARKS-203 - Update build doc EDGENT-240 - Java7 build support EDGENT-240 - Android build support EDGENT-240 - add manifest classpath entries EDGENT-240 - Release target, creating the target/… structure - QUARKS-204, EDGENT-240 - Junit parity - QUARKS-223, QUARKS-237, QUARKS-239 - need top level aggregating report - Javadoc parity - QUARKS-205 - Jacoco parity - QUARKS-237 - 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: EDGENT-139 > URL: https://issues.apache.org/jira/browse/EDGENT-139 > Project: Edgent > 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 EDGENT-240 [TODO final updates when flipping the switch] > - Java7 build support EDGENT-240 > - Android build support EDGENT-240 > - add manifest classpath entries EDGENT-240 > - Release target, creating the target/… structure - QUARKS-204, EDGENT-240 > - Junit parity - QUARKS-223, QUARKS-237, QUARKS-239 > - need top level aggregating report > - Javadoc parity - QUARKS-205 > - Jacoco parity - QUARKS-237 > - building from Eclipse - EDGENT-251 > - .classpath files have refs to ext jars that will be removed from the > repo > - switch travis-ci to gradle - EDGENT-252 (mostly done) > - 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)