10:59 a.m.
[ERROR] Failed to execute goal
org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate (default-generate) on project
gatein-user-guide-en: XSLT problem: unable to build transformer [null] : Failed to compile
stylesheet. 1 error detected. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.jboss.maven.plugins:maven-jdocbook-plugin:2.1.1:generate (default-generate) on project
gatein-user-guide-en: XSLT problem
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: XSLT problem
at
org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:285)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.jboss.jdocbook.xslt.XSLTException: unable to build transformer [null] :
Failed to compile stylesheet. 1 error detected.
at
org.jboss.jdocbook.xslt.TransformerBuilder.buildTransformer(TransformerBuilder.java:94)
at
org.jboss.jdocbook.xslt.TransformerBuilder.buildTransformer(TransformerBuilder.java:78)
at org.jboss.jdocbook.render.impl.BasicRenderer.buildTransformer(BasicRenderer.java:139)
at org.jboss.jdocbook.render.impl.BasicRenderer.performRendering(BasicRenderer.java:119)
at org.jboss.jdocbook.render.impl.BasicRenderer.render(BasicRenderer.java:115)
at org.jboss.maven.plugins.jdocbook.GenerationMojo.process(GenerationMojo.java:117)
at
org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.doExecute(AbstractDocBookMojo.java:250)
at
org.jboss.maven.plugins.jdocbook.AbstractDocBookMojo.execute(AbstractDocBookMojo.java:282)
... 21 more
Caused by: javax.xml.transform.TransformerConfigurationException: Failed to compile
stylesheet. 1 error detected.
at com.icl.saxon.PreparedStyleSheet.prepare(PreparedStyleSheet.java:136)
at com.icl.saxon.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:127)
at com.icl.saxon.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:79)
at
org.jboss.jdocbook.xslt.TransformerBuilder.buildTransformer(TransformerBuilder.java:88)
... 28 more
On Apr 26, 2011, at 5:43 PM, Marko Strukelj wrote:
I’ve done some fixes on the portal build …
I’ve added parent.relativePath to many modules to fix ‘chicken or egg’ problem that
caused failures when building from scratch with empty repository, without additional
settings.xml. Might be that I just patched up the ‘bugs’, not really fixed them, as the
modules involved might have wrong parents set in the first place. But it clean builds now
when before it didn’t (using maven3).
Also, in jboss packaging we have a dependency on
org.exoplatform.portal:exo.portal.server.jboss.plugin
Looking at the contents of this artifact it’s obvious that it has no effect at all. It
contains one conf/portal/configuration.xml file whose content is completely commented
out.
This is the only artifact for jboss-as5 and jboss-as6 packaging that depends on exo maven
repository - it’s not available in jboss repo.
So I commented it out for both jboss-as5 and jboss-as6 packaging, and it now builds OOTB
without having to create settings.xml with repositories definitions.
Also I’d prefer if we mandate maven3 for build. It’s double work to test build for
maven2, as well as for maven3, and there’s constant dilemma if someone claims build
doesn’t work - what version of maven they used. I see no good reason to maintain
compatibility with maven2, when build works perfectly fine with maven3.
There’s the issue of packaging/profiles.xml which has no effect when building with
maven3, so currently you have to specify extra settings via CLI. That can be fixed by
moving properties into packaging/pom.xml.
- marko
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev