[
http://mifosforge.jira.com/browse/MIFOS-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen resolved MIFOS-4069.
--------------------------------
Resolution: Fixed
We're now using Maven 3.0.
http://article.gmane.org/gmane.comp.finance.mifos.devel/10946
I converted unrelated, non-dependent dev tasks to issues.
# Maven version should be enforced - MIFOS-4395
# abstract findbugs-maven-plugin version into parent pom - MIFOS-4396
# remove default (super POM) settings - MIFOS-4524
> Upgrade from Maven 2.?? to Maven 3.0
> ------------------------------------
>
> Key: MIFOS-4069
> URL: http://mifosforge.jira.com/browse/MIFOS-4069
> Project: mifos
> Issue Type: Improvement
> Components: Build and Testing
> Reporter: Michael Vorburger
> Assignee: Adam Monsen
> Priority: Major
> Fix For: Elsie F - Iteration 10, Elsie F
>
>
> Now that Maven 3.0 is GA, Mifos may would like to upgrade from Maven 2.?? to
> Maven 3.0...
--
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 modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
