[
https://issues.apache.org/jira/browse/QUARKS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321916#comment-15321916
]
ASF GitHub Bot commented on QUARKS-139:
---------------------------------------
Github user Cazen commented on a diff in the pull request:
https://github.com/apache/incubator-quarks/pull/131#discussion_r66384667
--- Diff: console/servlets/build.gradle ---
@@ -0,0 +1,23 @@
+distsDirName = 'webapps'
+
+plugins.apply 'war'
+
+dependencies {
+ providedCompile 'javax.servlet:javax.servlet-api:3.1.0'
+ providedCompile project(':utils:streamscope')
+ providedCompile ext_classpath
+}
+
+war {
--- End diff --
Does all the test case passed? In my case, build failed due to console.war
location
Could you tell me if there is something forgotten setting that I missed?
> 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 additions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
