[
https://issues.apache.org/jira/browse/FINERACT-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210432#comment-17210432
]
Petri Tuomola commented on FINERACT-1171:
-----------------------------------------
I think that's likely to be an error about the OpenJPA enhance build step that
is imported into Eclipse as an external builder. Maybe the path to the external
builder is no longer correct given the workspace being imported is now one
directory higher up in the hierarchy? I can give this a go over the weekend to
see if it works for me.
And great to hear jgitver will give us unique version numbers for each commit -
that's what I was using the "git describe" in the previous build.gradle file
for. But does it also do something sensible if the source is not in a git
repository at all? We had a problem earlier when someone downloaded the sources
as a tar and tried to build the untarred directory - the previous way of
getting the version number did not like that we were not in a git repo at all...
Also I'm assuming that the jgitver will claim develop is still version 1.3.0 as
that's the latest tag reachable from develop... is that true?
> Multi-module configuration for Gradle
> -------------------------------------
>
> Key: FINERACT-1171
> URL: https://issues.apache.org/jira/browse/FINERACT-1171
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Build
> Affects Versions: 1.5.0
> Reporter: Aleksandar Vidakovic
> Assignee: Aleksandar Vidakovic
> Priority: Major
> Fix For: 1.5.0
>
> Attachments: image-2020-10-08-21-19-43-775.png,
> image-2020-10-08-21-43-03-567.png, image-2020-10-08-21-48-56-177.png,
> image-2020-10-08-21-52-46-940.png
>
>
> Use the build.gradle file in the root folder rather than in fineract-provider
> to import the project in IDEs.
> Note: this will force everyone to re-import the project in their IDEs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
