[izpack-user] Izpack backward compatibility (4.2.1 -> 4.3.1)
Mitchel99
Hi all,
I'm using izpack-maven-plugin version 1.0-alpha-5 to create my custom
installer. Every thing works fine with version 4.2.1 of
izpack-standalone-compiler, but when I try to upgrade to version 4.3.1, I
have the following error:
...
org.apache.maven.lifecycle.LifecycleExecutionException: IzPack compilation
ERROR
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:585)
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: org.apache.maven.plugin.MojoExecutionException: IzPack
compilation ERROR
at org.izpack.mojo.IzPackMojo.buildInstaller(IzPackMojo.java:256)
at org.izpack.mojo.IzPackMojo.execute(IzPackMojo.java:162)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: java.lang.UnsupportedOperationException: This parser does not
support specification "null" version "null"
at
javax.xml.parsers.SAXParserFactory.setXIncludeAware(SAXParserFactory.java:390)
at com.izforge.izpack.adaptator.impl.XMLParser.<init>(Unknown
Source)
at com.izforge.izpack.compiler.CompilerConfig.getXMLTree(Unknown
Source)
at
com.izforge.izpack.compiler.CompilerConfig.executeCompiler(Unknown Source)
at org.izpack.mojo.IzPackMojo.buildInstaller(IzPackMojo.java:247)
... 19 more
Following is the associated extract of the pom where I make references to
the izpack-standalone-compiler:
...
<plugin>
<groupId>org.codehaus.izpack</groupId>
<artifactId>izpack-maven-plugin</artifactId>
<version>1.0-alpha-5</version>
<!-- TODO Check dependencies -->
<dependencies>
<dependency>
<groupId>org.codehaus.izpack</groupId>
<artifactId>izpack-standalone-compiler</artifactId>
<version>${izpack-standalone.version}</version>
</dependency>
</dependencies>
<configuration>
<izpackBasedir>${staging.dir}</izpackBasedir>
<customPanelDirectory>${staging.dir}</customPanelDirectory>
<installerFile>${izpack-installer-filename}</installerFile>
</configuration>
<executions>
<execution>
<id>standard-installer</id>
<phase>package</phase>
<goals>
<goal>izpack</goal>
</goals>
</execution>
</executions>
</plugin>
...
<dependency>
<groupId>org.codehaus.izpack</groupId>
<artifactId>izpack-standalone-compiler</artifactId>
<version>${izpack-standalone.version}</version>
<optional>true</optional>
</dependency>
I would really appreciate if you could help me fix this issue.
Cheers,
Mitchel.
--
View this message in context: http://www.nabble.com/Izpack-backward-compatibility-%284.2.1--%3E-4.3.1%29-tp26061126p26061126.html
Sent from the izpack - users @ codehaus mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Dan Tran
I make a quick attempt run the src/it/sample with izpack 4.3.1, and
not able to produce the error your see.
So the error is likely the izpack configuration on this error
> Caused by: java.lang.UnsupportedOperationException: This parser does not
> support specification "null" version "null"
> at
> javax.xml.parsers.SAXParserFactory.setXIncludeAware(SAXParserFactory.java:390)
> at com.izforge.izpack.adaptator.impl.XMLParser.<init>(Unknown
> Source)
> at com.izforge.izpack.compiler.CompilerConfig.getXMLTree(Unknown
> Source)
> at
> com.izforge.izpack.compiler.CompilerConfig.executeCompiler(Unknown Source)
> at org.izpack.mojo.IzPackMojo.buildInstaller(IzPackMojo.java:247)
2 suggestion:
1. Fix up use izpack-maven-plugin-1.0-apha-6-SNAPSHOT to use
izpack 4.3.1 by default
and use it with your app to see if the plugin is the main cause.
2. see if you can trouble shoot your configuration and make a
producible maven project for us to look at.
Thanks
-Dan
Mitchel99
Hi Dan,
Thanks for your help.
For suggestion 1, I haven't found the
izpack-maven-plugin-1.0-apha-6-SNAPSHOT on the web repositories, but indeed
it would have been complicated since I'm using maven release plugin
(shnapshot not allowed).
I have reproduce the bug using the online example with izpack 4.3.1. Indeed,
it seems that there are some dependecies issues. For instance, if you add
the following dependency in the example, the bug appears:
<dependency>
<groupId>jboss</groupId>
<artifactId>jboss-common</artifactId>
<version>4.0.2</version>
<scope>compile</scope>
</dependency>
I need it to compile my project. Any suggestion?
Cheers,
Mitchel.
--
View this message in context: http://www.nabble.com/Izpack-backward-compatibility-%284.2.1--%3E-4.3.1%29-tp26061126p26064416.html
Dan Tran
I am able to reproduce your issue. And It is not the plugin's issue.
And It has something to do when you introduce jboss artfifact.
Looks like jboss-commons interferes with xml parser that comes with izpack
-Dan
Dan Tran
error, put it on exclusion list helps
<dependency>
<groupId>jboss</groupId>
<artifactId>jboss-common</artifactId>
<version>4.0.2</version>
<scope>compile</scope>
<exclusions>
<exclusion>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
</exclusion>
</exclusions>
</dependency>
Try that.
So this the class loader issue between izpack and jboss-comm. Ant
build will run into the same issue.
-Dan
6footplus
I've had a similar problem with the same exception message. It was due to a
transitive xercesImpl dependency. After determining where the dependency
came from (see mvn dependency:tree), I excluded it as follows:
<dependency>
<groupId>some.groupId</groupId>
<artifactId>some.acrtifact.with.xerces.dependency</artifactId>
<exclusions>
<exclusion>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
</exclusion>
</exclusions>
</dependency>
Regards,
Andreas
--
View this message in context: http://www.nabble.com/Izpack-backward-compatibility-%284.2.1--%3E-4.3.1%29-tp26061126p26067194.html
Mitchel99
Hi Dan,
Could it be possible to make it works in the other sense?
In fact, if I exclude this transitive dependency from jboss-common, lots of
errors appear in my application (which are quite impossilbe to solve...). So
I would like to know if it could be possible to solve this issue from Izpack
side?
If not, I will keep old release of Izpack (4.2.1).
Cheers,
Mitchel.
--
View this message in context: http://www.nabble.com/Izpack-backward-compatibility-%284.2.1--%3E-4.3.1%29-tp26061126p26074445.html
Dan Tran
-Dan
Dan Tran
<dependency>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
<version>2.9.1</version>
</dependency>
to override the one come with jboss, will solve the issue.
Good luck
-Dan