[ 
http://mifosforge.jira.com/browse/MIFOS-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=70755#comment-70755
 ] 

Michael Vorburger commented on MIFOS-4919:
------------------------------------------

This is now (finally) on master.  For background, see thread "Executable WAR: 
java -jar mifos.war (MIFOS-4919)" on 
https://groups.google.com/d/msg/mifosdeveloper/O7wvuLMjmIE/C9dcmdQ2wAEJ. FTR, 
copy/paste of the main point re. 'USAGE' here:

You'll find that the war/ module now packages two WAR files: the 
mifos-TEMP-nonexec.war (which is the same as the one before), and the (new) 
mifos.war (81 MB instead of the previous 76 MB; this mifos.war is ultimately 
the final mifos.war artifact that gets deployed into Maven and bundled in the 
mifos-${env.BUILD_TAG}.zip). For simplicity's sake and to avoid any end-user 
confusion, I suggest that only that new one shall be distributed as mifos.war, 
not two different ones. One could then start Mifos, without requiring an 
external Jetty (or Tomcat 7.0), simply via:

{noformat}java -Xmx1024m -XX:MaxPermSize=256m -jar mifos.war 9090{noformat}

The last (and only) CLI arg is the HTTP port. Configuration incl. DB etc. is 
"as usual 
(http://mifosforge.jira.com/wiki/display/MIFOS/Mifos+Configuration+Locations), 
nothing changes about that with this approach.

The same mifos.war works, of course, still like a "normal" WAR that can be 
deployed into a "classic" (non-embedded) external Jetty container.
                
> Executable WAR: java -jar mifos.war
> -----------------------------------
>
>                 Key: MIFOS-4919
>                 URL: http://mifosforge.jira.com/browse/MIFOS-4919
>             Project: mifos
>          Issue Type: New Feature
>          Components: Build and Testing
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Major
>             Fix For: Unscheduled
>
>
> Based on the work I've done for Workspace 2.0 with Jetty 
> (http://mifosforge.jira.com/wiki/display/MIFOS/Workspace+2.0), I think it 
> should (hopefully) be reasonably simple to now support Mifos as an 
> "Executable WAR", i.e. launching it simply via java -jar mifos.war (no Jetty 
> download).
> This could be useful e.g. for test servers or demos, and may be even in 
> (some?) production scenarios.
> It will be an alternative - dropping the mifos.war into an 'normal' Jetty 
> container will still work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World™ now supports Android™ Apps 
for the BlackBerry® PlayBook™. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
Mifos-issues mailing list
Mifos-issues@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to