[
https://issues.apache.org/jira/browse/FINERACT-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214215#comment-17214215
]
Michael Vorburger commented on FINERACT-1203:
---------------------------------------------
[~aleks] I had posted my comment concurrently with yours. So yes, I'm on board
with "strip all Spring Boot startup magic from the WAR file". If you want to
raise a PR for that (and just that, small! LOL), that seems useful to me. We
could even just do that as the solution "forever", and close this issue if we
make that change, from my side (unless either of you thinks we should change it
later, if we could; but we don't have to).
> Fix broken Executable WAR (and unify & ditch Executable JAR?)
> -------------------------------------------------------------
>
> Key: FINERACT-1203
> URL: https://issues.apache.org/jira/browse/FINERACT-1203
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Priority: Minor
> Attachments: war.log
>
>
> 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?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
