Eclipse Workspace with individual projects for Maven modules (instead of
current one big project)
-------------------------------------------------------------------------------------------------
Key: MIFOS-4394
URL: http://mifosforge.jira.com/browse/MIFOS-4394
Project: mifos
Issue Type: Dev Task
Reporter: Michael Vorburger
Assignee: Michael Vorburger
Priority: Major
http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTikxh4805bYP0mwrUEaEgAfYHLA7RRPxmtqXTpVW%40mail.gmail.com&forum_name=mifos-developer
When I upgraded to m2e 0.12.0 today, and did an Update Dependencies, my Maven
Dependencies Classpath Container (in Eclipse) remained empty (no JARs), or not
shown, and all classes from JARs were (logically) "not found".
A possible cause one could suspect for this may be (I'm just guessing) that the
somewhat "unconventional" m2e usage of having one big Eclipse projects for all
the Maven modules (instead of individual Eclipse projects per Maven module) may
not be supported in the latest m2e anymore?
I had been meaning to propose to change this, to switch the Mifos workspace to
using individual Eclipse projects for each Maven module, in the context of the
overall change in this JIRA parent task, and will work on and propose something
here.
--
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
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
