Spark

Spark's build should unpack .pack'd files at build time, not at first startup

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.6.0
  • Component/s: General
  • Labels:
    None
  • Environment:

    Just about anything really

  • Acceptance Test - Add?:
    No

Description

End users don't always have access to edit the file space where Spark is installed, and therefore when the .pack files are automatically unpacked, they can't be written. We need to unpack files at build time, not at startup time.

Attachments

  1. File
    spark.install4j
    02/11/09 08:28 PM
    29 kB
    Michael Will (cstux)
  2. Text File
    SPARK-906.patch
    02/10/09 08:28 AM
    3 kB
    Michael Will (cstux)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Michael Will (cstux) added a comment -

This patch disabled pack200 after compiling
If you want to use pack200, you have to change the property "pack200.enabled" to true

Show
Michael Will (cstux) added a comment - This patch disabled pack200 after compiling If you want to use pack200, you have to change the property "pack200.enabled" to true
Hide
Permalink
wroot added a comment -

cstux, can you explain it better? Is this patch going to increase the size of the setup file?

Show
wroot added a comment - cstux, can you explain it better? Is this patch going to increase the size of the setup file?
Hide
Permalink
Michael Will (cstux) added a comment -

Pack200 compressed some(not all) jar-files, to make spark smaller for the installer.

I think the installer must be supports pack200.

For Windows:
I have read the documentation from install4j, that supports pack200.
I think we should use the pack200 from the install4j, that packs all jar-files for the installer with the pack200 compression and
decompress the jars during the installation.

For Linux:
The debian.installer doesn't support pack200 at this time. If I have time, I will change the debian installer to support pack200.
That compress all files with pack200 during building the installer and decompress the files during the installation like install4j.

Show
Michael Will (cstux) added a comment - Pack200 compressed some(not all) jar-files, to make spark smaller for the installer. I think the installer must be supports pack200. For Windows: I have read the documentation from install4j, that supports pack200. I think we should use the pack200 from the install4j, that packs all jar-files for the installer with the pack200 compression and decompress the jars during the installation. For Linux: The debian.installer doesn't support pack200 at this time. If I have time, I will change the debian installer to support pack200. That compress all files with pack200 during building the installer and decompress the files during the installation like install4j.
Hide
Permalink
Michael Will (cstux) added a comment -

I have use the evaluation version from install4j to update the spark.install4j.
Now it use pack200 during the installation. The new installer have a size of 9 MB.
It's a different from 5 MB.

Show
Michael Will (cstux) added a comment - I have use the evaluation version from install4j to update the spark.install4j. Now it use pack200 during the installation. The new installer have a size of 9 MB. It's a different from 5 MB.
Hide
Permalink
Neil J added a comment -

Hi guys, new installer of Spark here...
Can someone please advise how this patch actually works ie. how to patch the original installation file

I am a little confused using a .patch file and a .install4j file ...
Any help appreciated...
Thank you !

Show
Neil J added a comment - Hi guys, new installer of Spark here... Can someone please advise how this patch actually works ie. how to patch the original installation file I am a little confused using a .patch file and a .install4j file ... Any help appreciated... Thank you !
Hide
Permalink
wroot added a comment -

.patch file is for the source, so you will have to compile it if you want to apply it. I'm not sure about spark.install4j file, but i think you cant patch anything without the compiling.

Show
wroot added a comment - .patch file is for the source, so you will have to compile it if you want to apply it. I'm not sure about spark.install4j file, but i think you cant patch anything without the compiling.
Hide
Permalink
Michael Will (cstux) added a comment -

Now default is disabled. Can be enabled in the build.xml

Show
Michael Will (cstux) added a comment - Now default is disabled. Can be enabled in the build.xml

People

Vote (9)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.