[FINERACT-1203] Make WAR non-executable to avoid confusion (because it's broken anyway)

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Assignee: Aleksandar Vidakovic
• Reporter: Michael Vorburger
• Created: 14/Oct/20 18:21
• Updated: 25/Feb/21 08:09
• Resolved: 17/Oct/20 14:37

Description

I've noticed that the WAR we build is not a traditional Tomcat only WAR, but a Spring Boot Executable WAR - but a broken one! Whereas our Executable JAR works of course, our WAR with java -jar fineract-provider/build/libs/fineract-provider.war fails to start, see attached war.log.

ptuomola and aleks perhaps this is something one of you would like to look into?

If you can fix this, then it poses the question why we would build and document and distribute and support two different artifacts. My vote, if this can be fixed, could be to unify on only having a (both "traditional AND Executable") WAR and no JAR. Unless there are reasons why that may be stupid, and both are useful, even if the problem above was fixed. Thoughts?

Issue Links

• Blocked: FINERACT-1305 Release Apache Fineract v1.5.0
• is blocked by: FINERACT-849 Migrate Fineract ORM from OpenJPA to EclipseLink
• relates to: FINERACT-1177 Alt. distro? Spring Boot JAR is not great for "dropping in" Plugins
• links to: GitHub Pull Request #1404