vidakovic commented on a change in pull request #1417:
URL: https://github.com/apache/fineract/pull/1417#discussion_r506988127



##########
File path: build.gradle
##########
@@ -454,3 +459,89 @@ configure(project.fineractJavaProjects) {
         }
     }
 }
+
+configure(project.fineractPublishProjects) {
+    apply plugin: 'maven'
+    apply plugin: 'maven-publish'
+    apply plugin: 'com.jfrog.bintray'
+
+    publishing {
+        publications {
+            mavenJava(MavenPublication) {
+                from components.java
+
+                versionMapping {
+                    usage('java-api') {
+                        fromResolutionOf('runtimeClasspath')
+                    }
+                    usage('java-runtime') {
+                        fromResolutionResult()
+                    }
+                }
+
+                pom {
+                    name = 'Fineract'
+                    description = 'A secure, multi-tenanted microfinance 
platform'
+                    url = 'https://fineract.apache.org'
+                    licenses {
+                        license {
+                            name = 'The Apache License, Version 2.0'
+                            url = 
'http://www.apache.org/licenses/LICENSE-2.0.html'
+                        }
+                    }
+                    // TODO: should we only list the Fineract contributors 
here? Or everyone that sent a PR (ca. 150; a bit much)? Or should we just omit 
this?

Review comment:
       Yeah, the developer section didn't make too much sense to me neither. 
People can see this - if they are interested - here on Github a lot better.
   
   As for the dependencies: yes, this is done automatically by the "maven" 
Gradle plugin. You get proper pom.xml with dependencies per module.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to