[
http://mifosforge.jira.com/browse/MIFOS-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
keithwoodlock updated MIFOS-4877:
---------------------------------
Component/s: Build and Testing
Fix Version/s: (was: Mifos Backlog)
Unscheduled
> improve MpesaImportTest: don't commit jar to source control
> -----------------------------------------------------------
>
> Key: MIFOS-4877
> URL: http://mifosforge.jira.com/browse/MIFOS-4877
> Project: mifos
> Issue Type: Improvement
> Components: Build and Testing
> Reporter: Adam Monsen
> Assignee: mifosdeveloperqueue
> Labels: volunteer
> Fix For: Unscheduled
>
>
> org.mifos.test.acceptance.admin.MpesaImportTest uses a jar committed to
> version control. This means a developer must manually keep the jar up to
> date. Use a mechanism that does not require a "hard-coded" jar file.
> Ideas:
> * use Maven... deploy built jars to our nexus server or a [Sonatype OSS
> repository|http://thread.gmane.org/gmane.comp.finance.mifos.devel/11067],
> make the acceptance test dynamically fetch a jar and test it
> This is an improvement building on MIFOS-3021.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
