From: James D. <jam...@gm...> - 2023-08-27 10:28:44
|
Thanks Victor! +1 On Sun, Aug 27, 2023 at 8:23 AM VICTOR MANUEL ROMERO RODRIGUEZ < vic...@fi...> wrote: > Hello, > > Now the Pentaho Report works for the latest Apache Fineract version > > https://github.com/openMF/fineract-pentaho > > Regards > > Victor > > > El mié, 9 ago 2023 a las 4:41, Honest Chirozva (<ho...@ta...>) > escribió: > >> Thanks James, I believe all pointers were given hence we can conclude >> this thread. >> >> >> >> Thanks. >> Honest >> >> >> >> *From: *James Dailey <jam...@gm...> >> *Sent: *Wednesday, 09 August 2023 04:04 >> *To: *de...@fi... >> *Cc: *Floyd Nickson <flo...@gm...>; Mifos software development >> <mif...@li...>; mifos-users >> <mif...@li...> >> *Subject: *Re: [Mifos-developer] Fineract-pentaho build failure >> >> >> >> Let’s provide pointers and move this off of the Fineract listserv. >> >> >> >> Unless there is a Fineract issue or unless someone plans to replace the >> reports concept with something at Apache Fineract, this thread should be >> done. >> >> >> >> >> >> >> >> On Tue, Aug 8, 2023 at 12:03 AM Honest Chirozva < >> ho...@ta...> wrote: >> >> Hi Floyd >> >> >> >> I have been away for some time. Just a follow up, did you manage to get >> the help and assistance you needed? >> >> >> >> Regards. >> >> >> Honest >> >> >> >> *From: *Floyd Nickson <flo...@gm...> >> *Sent: *Wednesday, 26 July 2023 10:03 >> *To: *Honest Chirozva <ho...@ta...> >> *Cc: *Mifos software development <mif...@li...>; >> de...@fi...; mifos-users <mif...@li...> >> *Subject: *Re: [Mifos-developer] Fineract-pentaho build failure >> >> >> >> When I clone, fineract and run ' ./gradlew clean build' the build fails >> therefore making any other step impossible. >> >> >> >> >> >> >> >> On Mon, Jul 24, 2023 at 5:04 PM Floyd Nickson <flo...@gm...> >> wrote: >> >> Thanks, I'll check it out! >> >> >> >> On Mon, Jul 24, 2023 at 12:11 PM Honest Chirozva < >> ho...@ta...> wrote: >> >> Hi Floyd, >> >> >> >> The error as logged is due to missing artifacts from the mifos jfrog >> repository. >> >> fineract-core:jar:0.0.255-beffb9d7 >> >> fineract-provider:jar:plain:0.0.255-beffb9d7 >> >> To fix this, you can rebuild the artifacts on localhost like this >> >> 1. Clone apache/fineract >> >> 2. Build fineract using this command ./gradlew clean build >> >> 3. You should find fineract-core jar and fineract-provider plain >> jar in the build directories >> >> 4. Add these jars to your fineract pentaho plugin pom file as >> system scope (See below) >> >> >> >> When you build the fineract jars, they have a version at the suffix like >> fineract-core-0.0.0-a119296a.jar, do not rename them. >> >> Let’s assume you ran gradlew build and got the following artifacts, >> >> fineract-core-0.0.0-a119296a.jar >> >> fineract-provider-0.0.0-a119296a-plain.jar >> >> ***NB: the fineract provider has to be a plain jar not the full >> application jar (note the -plain.jar suffix). >> >> i. Create a libs folder at the root of >> the fineract pentaho project and copy the jars to that folder. >> >> ii. Update the fineract pentaho pom with >> the correct version, in this case 0.0.0-a119296a >> >> <properties> >> >> … >> >> <fineract.version>0.0.0-a119296a</fineract.version> >> >> … >> >> </properties> >> >> iii. In the pom update your fineract core >> and fineract plain jars dependencies like >> >> >> >> FOR FINERACT PLAIN JAR >> >> <dependency> >> >> <groupId>org.apache.fineract</groupId> >> >> <artifactId>fineract-provider</artifactId> >> >> <version>${fineract.version}</version> >> >> <classifier>plain</classifier> >> >> <scope>system</scope> >> >> >> <systemPath>${project.basedir}/libs/fineract-provider-${fineract.version}-plain.jar</systemPath> >> >> <exclusions> >> >> <exclusion> >> >> <groupId>org.apache.fineract</groupId> >> >> <artifactId>fineract-avro-schemas</artifactId> >> >> </exclusion> >> >> </exclusions> >> >> </dependency> >> >> >> >> FOR CORE JAR >> >> <dependency> >> >> <groupId>org.apache.fineract</groupId> >> >> <artifactId>fineract-core</artifactId> >> >> <version>${fineract.version}</version> >> >> <scope>system</scope> >> >> >> <systemPath>${project.basedir}/libs/fineract-core-${fineract.version}.jar</systemPath> >> >> </dependency> >> >> >> >> UPDATE jakarta >> >> <dependency> >> >> <groupId>jakarta.ws.rs</groupId> >> >> <artifactId>jakarta.ws.rs-api</artifactId> >> >> <version>3.1.0</version> >> >> <scope>compile</scope> >> >> </dependency> >> >> >> >> I think it its missing a version. Also update >> PentahoReportingProcessServiceImpl.java to import MultivaluedMap and >> Response form the jakarta api. Line 36 and 37 >> >> >> >> import jakarta.ws.rs.core.MultivaluedMap; >> >> import jakarta.ws.rs.core.Response; >> >> >> >> >> >> Build with this command on bash shell >> >> ./mvnw -Dmaven.test.skip=true clean package >> >> >> >> If you’re using PowerShell >> >> mvnw.cmd --% -Dmaven.test.skip=true clean package >> >> >> >> Regards. >> >> Honest Chirozva >> Technical Consultant >> >> TAAT Consulting >> >> >> >> *From: *Floyd Nickson <flo...@gm...> >> *Sent: *Monday, 24 July 2023 10:38 >> *To: *Mifos software development <mif...@li...>; >> Honest Chirozva <ho...@ta...> >> *Cc: *de...@fi...; mifos-users >> <mif...@li...> >> *Subject: *Re: [Mifos-developer] Fineract-pentaho build failure >> >> Thank you @ho...@ta... <ho...@ta...> for >> the information. I tried to follow the responses in the previous emails and >> applied the suggested modifications but still when I run ./mvnw >> -Dmaven.test.skip=true clean package it fails. >> >> >> >> >> >> >> >> >> >> On Mon, Jul 24, 2023 at 11:08 AM Honest Chirozva < >> ho...@ta...> wrote: >> >> Hi Floyd, >> >> >> >> I’m quite new to the Mifos community so I wouldn’t know what you mean by >> “similar fashion as it is done on 18 and 21”. However, due to licensing >> issues the apache fineract cannot be released together with pentaho reports >> but separate as a plugin. The fineract pentaho plugin is maintained by >> Mifos on this repo https://github.com/openMF/fineract-pentaho and has >> instructions on how to build and deploy the plugin with fineract. >> >> >> >> If you face issues with the setup refer to previous mails on this thread >> and if not clear enough I am happy to assist. >> >> >> >> It seems that many people are facing issues with the pentaho plugin >> installation thereby critical that we update the docs/README on the pentaho >> plugin repo. I am willing to help on this >> >> >> >> Regards. >> >> Honest Chirozva >> Technical Consultant >> >> TAAT Consulting >> >> >> >> *From: *Floyd Nickson <flo...@gm...> >> *Sent: *Sunday, 23 July 2023 15:01 >> *To: *Mifos software development <mif...@li...> >> *Cc: *de...@fi...; mifos-users >> <mif...@li...> >> *Subject: *Re: [Mifos-developer] Fineract-pentaho build failure >> >> >> >> Good Day everyone, Is there a way to build these reports and use them in >> a similar fashion as it is done in the official releases 18 and 21? >> >> It would be great if that could be done. If anyone is willing to help me >> out I will appreciate it. Thank you. >> >> >> >> On Wed, Jul 12, 2023 at 7:20 PM James Dailey <jam...@gm...> >> wrote: >> >> Thanks Honest for that answer. >> >> I don't see anything here for the Fineract community to work on, but >> correct me if I am wrong. >> >> Perhaps someone over on the Mifos project (openMF) can update the >> documentation and change the way that the pentaho configuration is >> handled. i.e. cp files in deploy script/ add a gradle task? >> >> In any case, this is a useful set of instructions so thank you for that. >> >> James >> >> On Wed, Jul 12, 2023 at 8:16 AM Honest Chirozva >> <ho...@ta...> wrote: >> > >> > Hi Jamui, >> > >> > >> > >> > + Adding the Mifos community list to this thread as the >> fineract-pentaho repo is currently managed under OpenMF Umbrella. >> > >> > >> > >> > Please note that this is not a FINERACT topic, but you should be able >> to add the Pentaho plugin if you follow the instructions under the readme >> here https://github.com/openMF/fineract-pentaho >> > >> > Please see FAQ about separation of projects. >> > >> > >> > >> > I was also facing issues with the fineract pentaho plugin and managed >> to fix it. >> > >> > >> > >> > The error as logged is due to missing artifacts from the mifos jfrog >> repository. >> > >> > fineract-core:jar:0.0.255-beffb9d7 >> > >> > fineract-provider:jar:plain:0.0.255-beffb9d7 >> > >> > To fix this >> > >> > Clone apache/fineract >> > Build fineract using this command ./gradlew clean build >> > You should find fineract-core jar and fineract-provider plain jar in >> the build directories >> > Add these jars to your fineract pentaho plugin pom file as system scope >> (Notify if you face issues doing this step) >> > Build the plugin again >> > >> > >> > >> > Note that this will only build the pentaho plugin jar. For running the >> plugin with fineract you should follow the steps at >> https://github.com/openMF/fineract-pentaho/blob/develop/README.md. Again >> if you encounter problems feel free to ask for assistance >> > >> > >> > >> > Regards. >> > >> > Honest Chirozva >> > Technical Consultant >> > >> > TAAT Consulting >> > >> > >> > >> > From: Jamiu Ayomide Olawale >> > Sent: Wednesday, 12 July 2023 16:09 >> > To: de...@fi... >> > Subject: Fineract-pentaho build failure >> > >> > >> > >> > >> > dear team >> > >> > >> > >> > tried building the plugin from git but got the below error >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > [INFO] >> ------------------------------------------------------------------------ >> > [INFO] BUILD FAILURE >> > [INFO] >> ------------------------------------------------------------------------ >> > [INFO] Total time: 03:31 min >> > [INFO] Finished at: 2023-07-12T13:08:26Z >> > [INFO] >> ------------------------------------------------------------------------ >> > [ERROR] Failed to execute goal on project pentaho-plugin: Could not >> resolve dependencies for project >> community.mifos:pentaho-plugin:jar:1.8.4-SNAPSHOT: Failed to collect >> dependencies at >> org.apache.fineract:fineract-provider:jar:plain:0.0.255-beffb9d7 -> >> org.apache.fineract:fineract-core:jar:0.0.255-beffb9d7: Failed to read >> artifact descriptor for >> org.apache.fineract:fineract-core:jar:0.0.255-beffb9d7: Could not transfer >> artifact org.apache.fineract:fineract-core:pom:0.0.255-beffb9d7 from/to >> fineract-snapshot (https://mifos.jfrog.io/artifactory/libs-snapshot-local): >> Transfer failed for >> https://mifos.jfrog.io/artifactory/libs-snapshot-local/org/apache/fineract/fineract-core/0.0.255-beffb9d7/fineract-core-0.0.255-beffb9d7.pom >> 409 -> [Help 1] >> > [ERROR] >> > [ERROR] To see the full stack trace of the errors, re-run Maven with >> the -e switch. >> > [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> > [ERROR] >> > [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> > [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > -- >> > >> > Sybarite Networks >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> >> >> Mifos-developer mailing list >> mif...@li... >> Unsubscribe or change settings at: >> https://lists.sourceforge.net/lists/listinfo/mifos-developer >> >> >> >> Mifos-developer mailing list >> mif...@li... >> Unsubscribe or change settings at: >> https://lists.sourceforge.net/lists/listinfo/mifos-developer >> >> >> >> >> >> -- >> >> Sent from Gmail Mobile >> >> >> > Mifos-developer mailing list > mif...@li... > Unsubscribe or change settings at: > https://lists.sourceforge.net/lists/listinfo/mifos-developer -- Sent from Gmail Mobile |