[
https://issues.apache.org/jira/browse/FINERACT-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234579#comment-17234579
]
Avik Ganguly commented on FINERACT-1203:
----------------------------------------
[~ptuomola] [~aleks] [~vorburger] Build is flagged as successful with both war
and bootWar tasks but neither generates the war file in build/libs as
war/bootWar step gets skipped in the end.
Flipped enabled of bootWar to true and re-ran the command to generate WAR file.
File size is 100mb against v1.4's ~70mb. Should this change be made in upstream?
> Make WAR non-executable to avoid confusion (because it's broken anyway)
> -----------------------------------------------------------------------
>
> Key: FINERACT-1203
> URL: https://issues.apache.org/jira/browse/FINERACT-1203
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Assignee: Aleksandar Vidakovic
> Priority: Minor
> Fix For: 1.5.0
>
> 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)
