[
http://mifosforge.jira.com/browse/MIFOSBI-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen updated MIFOSBI-264:
--------------------------------
Description:
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].
was:
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.
> 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
> Fix For: 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
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
