[TIMOB-8607] MobileWeb: Packaging: all javascript files are duplicated with "uncompressed" in filename
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Won't Fix |
|---|
| Resolution Date | 2012-04-10T16:06:28.000+0000 |
|---|
| Affected Version/s | Release 2.0.0, Release 1.8.2, Release 2.0.1 |
|---|
| Fix Version/s | n/a |
|---|
| Components | MobileWeb |
|---|
| Labels | parity, regression |
|---|
| Reporter | Dustin Hyde |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2012-04-06T10:42:50.000+0000 |
|---|
| Updated | 2013-05-01T20:15:01.000+0000 |
|---|
Description
When a project is packaged for production, every javascript file is duplicated and the duplicate contains "uncompressed" in the filename.
This does not occur in 1.8.1. This does not occur when "previewed in browser".
This also does not occur in iOS or Android, so any apps using the filesystem would behave differently in a MobileWeb production.
Steps to Reproduce:
1. Create a new project.
2. Package for distribution.
3. Navigate to package directory.
Expected Result:
There should only be one copy of each javascript file.
Actual Result:
There are two copies of each javascript file, one containing "uncompressed" in the filename.
Attachments
| File | Date | Size |
|---|
| 1.8.1.png | 2012-04-06T10:42:50.000+0000 | 52298 |
| 1.8.2+.png | 2012-04-06T10:42:50.000+0000 | 53909 |
This is by design. The idea is when you do a production build, the original uncompressed version is kept. If you run into a tricky bug, you can always restore the uncompressed file and see where it is causing problems. We have already planned to have a build profile setting "keep-uncompressed" that will remove those uncompressed files when set to false.
Closing.