[
http://mifosforge.jira.com/browse/MIFOS-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60756#action_60756
]
Michael Vorburger commented on MIFOS-3925:
------------------------------------------
BTW: I've had other workspace issues, technically separate from the title of
this issue, but worth mentioning in the context of WTP and stuff: Resources
(such as e.g. schedulerTestTask.xml) from application/src/test/resources/.../
are in two places on the classpath in a workspace: in
application/target/mifos-webapp/WEB-INF/classes (the Java Build Path Default
Output folder), and application/target/test-classes (where CLI Maven put it).
This can very confusing, because editing and saving a resource no longer makes
that change visible (if the application/target/test-classes happens to be first
in the classpath, which is well possible and was the case in my workspace, with
an unmodified .classpath as from Git).
One possible solution may be to not use target/classes and target/test-classes
and target/mifos-webapp in the IDE (so configure e.g. only target/eclipse as
Java Build Path Default Output - but tests would be needed if m2e digs this (I
fear it may not). An alternative solution may be, once again, a completely
different workspace set-up.
> userInterface/src/main/webapp/ not configured in WTP
> ----------------------------------------------------
>
> Key: MIFOS-3925
> URL: http://mifosforge.jira.com/browse/MIFOS-3925
> Project: mifos
> Issue Type: Bug
> Reporter: Michael Vorburger
> Priority: Major
>
> 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
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
