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

Michael Vorburger commented on MIFOS-4071:
------------------------------------------

I've just spent a few hours to look into this.

My findings from some research re. how to get WTP and m2e to play nicely are on 
https://sites.google.com/site/michaelvorburger/m2e-and-wtp - it's possible.

I've attempt to apply what I've described in my article to MIFOS.  The current 
state is pushed to 
https://github.com/vorburger/mifos-head/commits/MIFOS-4071__Eclipse-M2%2BWTP.  
It... "partially works" - all non-binary (compiled) Web resources are in 
application\target\ECLIPSE\mifos-webapp\WEB-INF, copied into WTP's e.g. 
.metadata\.plugins\org.eclipse.wst.server.core\tmp2\wtpwebapps\mifos-gazelle.  
However the mifos-gazelle/WEB-INF/lib there is "partial" - only SOME of the 
JARs from the Maven Dependencies Eclipse Classpath container are pushed there 
(7 in my case, no apparent logic which ones).  May be a WTP bug.

Am giving up at this point, to directly focus on MIFOS-4099 instead.

> Eclipse Build and Maven build conflict
> --------------------------------------
>
>                 Key: MIFOS-4071
>                 URL: http://mifosforge.jira.com/browse/MIFOS-4071
>             Project: mifos
>          Issue Type: Bug
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>
> As reported in 
> http://mifosforge.jira.com/browse/MIFOS-3925?focusedCommentId=60756&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_60756,
>  due to the particular way MIFOS is using Eclipse Build configuration, the 
> Eclipse Build and Maven build often conflict one ends up have one and the 
> same resource twice in two different places on the classpath.
> IMHO it would be best to completely separate them, and have e.g. 
> {module}/target as usual for Maven, and a separate top-level 
> mifos-head/target/ECLIPSE for everything that eclipse compiles.
> What prevents this is that the way WTP is used in the current set-up, the 
> *.jar MUST be in application\target\mifos-webapp\WEB-INF\lib - but I believe 
> a better WTP/m2e integration would be feasible - somehow.

-- 
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