icult
>>>> as our complete build scripts are under sub directory.
>>>>
>>>> Either we need to add Gradle scripts to top level directory also or
>> move
>>>> the
>>>> complete source tree from Fineract-provider t
gt; > this or shall I try to proceed with next release by adding "How to run
> > RAT"
> > > in readme without integrating RAT to top level directory?
> > >
> > >
> > >
> > > And I don't understand how maven is going to help here as we are giving
>
gt; >
> >
> >
> > Can you let me know your opinion on this please.
> >
> >
> >
> > Thanks,
> >
> > Nazeer
> >
> > From: Shaik Nazeer [mailto:nazeer.sh...@confluxtechnologies.com]
> > Sent: 29 December 2016 18:27
> > To:
azeer
>
> From: Shaik Nazeer [mailto:nazeer.sh...@confluxtechnologies.com]
> Sent: 29 December 2016 18:27
> To: dev@fineract.incubator.apache.org
> Subject: [Apache Fineract] Addressing review comments of 0.5.0-incubating
> release
>
>
>
> Hi all,
>
>
>
> I ha
s we are giving
complete deployable war file.
Can you let me know your opinion on this please.
Thanks,
Nazeer
From: Shaik Nazeer [mailto:nazeer.sh...@confluxtechnologies.com]
Sent: 29 December 2016 18:27
To: dev@fineract.incubator.apache.org
Subject: [Apache Fineract] Addressing review co
Hi all,
I have created a JIRA task to address all review comments of
0.5.0-incubating release.
https://issues.apache.org/jira/browse/FINERACT-357
I can handle all review comments except maven related. Does anybody know how
to include maven repo as part of Fineract release?
Thanks
Naz
