[
http://mifosforge.jira.com/browse/MIFOS-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
keithwoodlock updated MIFOS-4747:
---------------------------------
Component/s: Build and Testing
Fix Version/s: (was: Release G)
Unscheduled
Assignee: mifosdeveloperqueue
> mvn package or test in root dir should work, without mvn install in
> reporting-libs
> ----------------------------------------------------------------------------------
>
> Key: MIFOS-4747
> URL: http://mifosforge.jira.com/browse/MIFOS-4747
> Project: mifos
> Issue Type: Dev Task
> Components: Build and Testing
> Reporter: Michael Vorburger
> Assignee: mifosdeveloperqueue
> Fix For: Unscheduled
>
> Attachments: patch
>
>
> It's a little bit annoying that as a new user one must first do an 'mvn
> install' inside reporting-libs/ and cannot do e.g. 'mvn package' or 'mvn
> test' in the root directory.
> The reporting-libs modules is actually part of the maven reactor, but the
> maven-install-plugin ignores package or test and only copies the JARs on
> install. (If you do 'mvn install' in the root directory it actually works!
> Just package and test, which is what you typically do, don't work.)
> Somehow it should be possible to configure the pom.xml in reporting-libs to
> have the maven-install-plugin also work on e.g. test and package?
--
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
