Myrle

Assuming all is well with the first part, I took approach A as it looked
much easier:

> java -jar -Ddemoserver.provision=true demo-server-0.1.0-BUILD-SNAPSHOT.jar

which completes with 1 test and 1 failure


Time: 1,404.989

There was 1 failure:

1) startDevServer(org.apache.fineract.cn.dev.ServiceRunner)

feign.RetryableException: Connection refused (Connection refused) executing
POST
http://localhost:2020/provisioner/v1/auth/token?grant_type=password&client_id=service-runner&username=wepemnefret&password=oS%2F0IiAME%2F2unkN1momDrhAdNKOhGykYFH%2FmJN20

at feign.FeignException.errorExecuting(FeignException.java:67)

at
feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:104)

at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:76)

... snip

On Wed, Oct 31, 2018 at 2:30 PM James Dailey <[email protected]> wrote:

> Hi Myrle - That works just fine as I suspected it would (having already
> built another repo that way in this process).
>
> I am trying to provide a good way for newbies to build the project and use
> the build APIs... and to identify where it is breaking down.  I'm "testing"
> the process if you will.
>
> The script (as I believe know) is part of the process on
> https://cwiki.apache.org/confluence/display/FINERACT/How+To+Build+Apache+Fineract+CN
> and seems like a good starting point, although as you noted doesn't have a
> way to recover is something is "off".
>
> Hmm... yes, I guess it would still be useful for me to - without script -
> build the project first, and then go back to the script to figure out how
> to make it less brittle.  So, I'll continue with the instructions after
> manually going through each of the remaining repos.
>
> As one thing that may be wrong with the script, this attempt to add
> execution privilege to a file doesn't work on my bash env.
>
> chmod +x gradlew  # returns chmod: gradlew: No such file or directory
> Anyway, it would be useful to know the resulting structure of the project
> at each "Stage" of this.  For example, the script creates /tools and /core
> and places certain repos in those, but due to some error .. repos are
> getting created above the default starting directory.  Then subsequent to
> the maven call there is the .m2/repository artifacts which get put into a
> structure.   I don't know if I have a success or not, and/or if I should mv
> things (does it matter) around or re-run both the clone and ./gradlew
> publishToMavenLocal  commands.  (does relative path of the local git
> repos matter to gradelew? ).
>
> thanks,
> James
>
> On Wed, Oct 31, 2018 at 12:19 PM Myrle Krantz <[email protected]> wrote:
>
>> Hey James,
>>
>> So to be honest, I don't use the script.  And once it has failed, it isn't
>> built to be self-repairing as far as I can tell.  Let's just get the
>> demo-server build working on your machine, and then maybe you can go back
>> and figure out why the script isn't working in your environment and maybe
>> make a PR.
>>
>> Have you tried the following?
>> > cd <the_directory_you're_keeping_your_fineract_repos_in>
>> > git clone https://github.com/jdailey/fineract-cn-payroll  # this is
>> where
>> I believe you've reached successfully
>> > cd fineract-cn-payroll
>> > ./gradlew publishToMavenLocal                             # this is what
>> appears to have failed at some point here.
>>
>> That last command should publish the two artifacts in payroll (api and
>> service) to your local artifactory.  Presumably this is what has failed at
>> some point on your machine.  What error message do you get when you try to
>> execute that?
>>
>> (Please keep in mind, I haven't used a Mac computer since high school, so
>> you may have to "re-interpret" some of those commands for your
>> environment.)
>>
>> Best Regards,
>> Myrle
>>
>>
>>
>> On Wed, Oct 31, 2018 at 7:51 PM James Dailey <[email protected]>
>> wrote:
>>
>> > Myrle -
>> >
>> > I think something else is going on... with the script.
>> >
>> > When I watch it doing the Build, it is skipping over certain repos, and
>> so
>> > I'm trying to figure out where it is failing.
>> >
>> > So, I commented out one of the repos in the script which seems to be a
>> > problem for gradle and also split these repo builds into different
>> calls of
>> > get_modules()
>> >
>> > ... script:  initial-setup.sh
>> >
>> > get_modules fineract-cn-anubis fineract-cn-identity
>> > fineract-cn-permitted-feign-client fineract-cn-provisioner
>> > fineract-cn-rhythm
>> >
>> > #get modules fineract-cn-template
>> >
>> > get modules fineract-cn-office fineract-cn-customer fineract-cn-group
>> > fineract-cn-accounting fineract-cn-portfolio
>> >
>> > get modules fineract-cn-deposit-account-management fineract-cn-cheques
>> >
>> > get modules fineract-cn-payroll fineract-cn-teller fineract-cn-reporting
>> > fineract-cn-notifications
>> >
>> > ....
>> >
>> > get_modules() {
>> >
>> >   for module in $@
>> >
>> >   do
>> >
>> >     git clone https://github.com/$githubAccount/$module.git
>> >
>> >     cd $module
>> >
>> >     git remote add upstream https://github.com/apache/$module.git
>> >
>> >     # For some reason permission gets denied
>> >
>> >     chmod +x gradlew
>> >
>> >     ./gradlew publishToMavenLocal
>> >
>> >     cd ..
>> >
>> >   done
>> >
>> > }
>> >
>> > Anyway, this solves some of the issues but /and, I still have a build
>> > FAILURE , about missing payroll api
>> >
>> > Payroll is available in my git hub:
>> > https://github.com/jdailey/fineract-cn-payroll
>> >
>> >
>> > FAILURE: Build failed with an exception.
>> >
>> > * What went wrong:
>> >
>> > Could not resolve all dependencies for configuration
>> > ':detachedConfiguration5'.
>> >
>> > > Could not find org.apache.fineract.cn
>> .payroll:api:0.1.0-BUILD-SNAPSHOT.
>> >
>> >   Searched in the following locations:
>> >
>> >
>> >
>> >
>> https://jcenter.bintray.com/org/apache/fineract/cn/payroll/api/0.1.0-BUILD-SNAPSHOT/maven-metadata.xml
>> >
>> > Looking at the created local clones, which the script does, the
>> cn-payroll
>> > directory does not get created, and neither do any of the following ones
>> > for teller, reporting, notifications.
>> >
>> > Thanks,
>> > - James
>> >
>>
>

Reply via email to