[
http://mifosforge.jira.com/browse/MIFOSBI-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Chau updated MIFOSBI-264:
-----------------------------
Assignee: Van Mittal-Henkle (was: mifosdeveloperqueue)
> release zip should explode into a subdirectory matching the archive filename
> ----------------------------------------------------------------------------
>
> Key: MIFOSBI-264
> URL: http://mifosforge.jira.com/browse/MIFOSBI-264
> Project: mifos business intelligence
> Issue Type: Bug
> Reporter: Adam Monsen
> Assignee: Van Mittal-Henkle
> Fix For: Mifos BI 1.2 - Iteration 7, Mifos BI 1.2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> The zip explodes directly into the current directory. Instead, I'd like it to
> explode into a directory matching the name of the zip file.
> For instance, instead of
> {noformat}
> $ unzip -l mifos_bi-1.1.0.zip
> BUILD_ENV.txt
> README
> ETL/MifosDataWarehouseETL/
> ...
> {noformat}
> I expect:
> {noformat}
> $ unzip -l mifos_bi-1.1.0.zip
> mifos_bi-1.1.0/BUILD_ENV.txt
> mifos_bi-1.1.0/README
> mifos_bi-1.1.0/ETL/MifosDataWarehouseETL/
> ...
> {noformat}
> This is pretty standard for archives and software releases. It avoids
> cluttering up the current directory where the archive is unpacked.
> See also: [How to release software].
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
