Actions
Feature #5356
open
Web installer
Status:
Assigned
Priority:
Low
Assigned To:
Category:
Packaging/documentation
Target version:
-
Start date:
10/16/2013
Due date:
% Done:
0%
Estimated time:
Description
Evaluate solutions for installing JSAGA through a Web interface.
This would avoid to generate the 130MB graphical installer.
Updated by Schwarz Lionel about 12 years ago
After upgrading to izPack5, the installer JAR is 50MB big.
To build a web installer, add the config param kind in the izpack-maven-plugin section in jsaga-installer.pom.xml:
<plugin>
<groupId>org.codehaus.izpack</groupId>
<artifactId>izpack-maven-plugin</artifactId>
<version>5.0.0-rc1</version>
<configuration>
...
<kind>web</kind>
</configuration>
...
and param webdir in assembly/izpack.xsl:
<info>
<appname>JSAGA</appname>
...
<webdir>http://maven.in2p3.fr/fr/in2p3/jsaga</webdir>
</info>
see http://izpack.org/documentation/advanced-features.html#web-installers
This gives the following error:
Copying the skeleton installer
Copying 12 files into installer
Merging 0 jars into installer
Writing 22 Packs into installer
Writing Pack 0: Core
Writing Pack 1: Integration tests
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] java.io.IOException: Stream has already been finished
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.AssertionError: java.io.IOException: Stream has already been finished
at org.izpack.mojo.IzPackNewMojo.execute(IzPackNewMojo.java:184)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.io.IOException: Stream has already been finished
at org.apache.tools.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:635)
at com.izforge.izpack.compiler.stream.JarOutputStream.putNextEntry(JarOutputStream.java:145)
at com.izforge.izpack.compiler.packager.impl.Packager.writePacks(Packager.java:144)
at com.izforge.izpack.compiler.packager.impl.PackagerBase.writeInstaller(PackagerBase.java:452)
at com.izforge.izpack.compiler.packager.impl.PackagerBase.createInstaller(PackagerBase.java:404)
at com.izforge.izpack.compiler.Compiler.createInstaller(Compiler.java:143)
at com.izforge.izpack.compiler.CompilerConfig.executeCompiler(CompilerConfig.java:332)
at org.izpack.mojo.IzPackNewMojo.execute(IzPackNewMojo.java:180)
Updated by Schwarz Lionel over 11 years ago
reproduced with izpack-maven-plugin 5.0.0-rc2
Actions