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

Adam Monsen commented on MIFOS-3925:
------------------------------------

Running {{mvn war:war}} indeed got the WTP working again, thanks!

I'm hesitant to apply the patch to head/master because

# it's a work-in-progress... it still doesn't solve the problem of having to 
run {{mvn war:war}}
# it moves every .ftl file, quickly making merges from 1.7.x impossible

The first one can be mitigated if you just say "ah, it's fine, go for it--the 
.classpath improvements are worth it" (especially if you're around to help 
clean up the mess if developer workstations somehow get mucked up).

The second one can be mitigated if you will base this patch on the 1.7.x 
branch. That way we can continue to merge .ftl changes from 1.7.x for a while, 
maybe for months. If you think this second one also won't be a problem, I'd 
trust your judgment.

Thoughts?

> userInterface/src/main/webapp/ not configured in WTP
> ----------------------------------------------------
>
>                 Key: MIFOS-3925
>                 URL: http://mifosforge.jira.com/browse/MIFOS-3925
>             Project: mifos
>          Issue Type: Bug
>          Components: Build and Testing
>            Reporter: Michael Vorburger
>            Assignee: Adam Monsen
>            Priority: Major
>             Fix For: Gazelle Backlog
>
>         Attachments: MIFOS-3925_review.patch.gz, wtp_startup_errors.txt
>
>
> Resources in userInterface/src/main/webapp, e.g. 
> /userInterface/src/main/webapp/pages/css/maincss.css do not seem to be 
> available in the recommended WTP-based set-up, because they are not copied to 
> application/target/mifos-webapp (where WTP looks for the "WAR").
> It may work for some people after CLI mvn.  This is very cumbersome of 
> course, as it would mean that you have to do CLI mvn after each change in 
> userInterface/src/main/webapp - not acceptable.
> I've tried simply adding a new Eclipse Project Properties Java Build Path 
> Source folder userInterface/src/main/webapp -> 
> application/target/mifos-webapp, but that doesn't work due to an error 
> message "Cannot nest output folder 
> 'vorburger-mifos-head/application/target/mifos-webapp/WEB-INF/freemarker' 
> inside output folder 'vorburger-mifos-head/application/target/mifos-webapp'" 
> -- which doesn't really make sense to me - may be it's obvious what Eclipse 
> is trying to say and I'm just too tired, but I don't yet get it.
> PS: Personally I would set-up the entire workspace differently, via a fully 
> Classpath-based embedded Jetty container.  (Happy to illustrate on a branch, 
> if there is interest in re-integrating - doesn't seem to meet much interest 
> though?)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to