Giter VIP home page Giter VIP logo

docbkx-tools's People

Contributors

mimil avatar wspringer avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docbkx-tools's Issues

JSP-style <?eval ${project.version}?> entity replacement also for attributes

In the attached example file, the following expression 

  <para>Testing: <?eval ${project.version}?></para>

compiles and generates the expected output, e.g. for a version of 1.2.3 you get

  Testing: 1.2.3

However, the following expression

  <para>Testing: <ulink url="http://<?eval ${project.version}?>"/></para>

fails with

Error on line 11 column 108 of file:///C:/Users/.../src/docbkx/entity
-test.xml:
  Error reported by XML parser: The value of attribute "url" associated
with an element type "ulink" must not contain th
e '<' character.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to transform entity-test.xml.

Embedded error: org.xml.sax.SAXParseException: The value of attribute "url"
associated with an element type "ulink" must
 not contain the '<' character.

It would be nice if the entity replacement could also be applied to
attributes, as in this example. This is especially relevant for e.g. links
to API documentation which will frequently contain references to project
names and versions.

Versions:

Plugin version: 2.0.9
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_17
Java home: C:\Program Files\Java\jdk1.6.0_17\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"

Original issue reported on code.google.com by [email protected] on 25 Feb 2010 at 7:34

Attachments:

Xinclude (chapters) with images raise a generation bug

sometimes,  you can use XInclude in your docbook document, to divide
content into small parts (chapters). if you use some images in chapters,
block content ('sec2' or 'caution' element for example)after the first
image is empty.

this display bug is present only locally to the chapter which contains images.

this bug has been raised with this maven2 plugin declaration:
 <plugin>
                        <groupId>com.agilejava.docbkx</groupId>
                        <artifactId>docbkx-maven-plugin</artifactId>
                        <executions>
                          <execution>
                                            <!--
<id>html-with-single-output</id>-->
                            <goals>
                              <goal>generate-html</goal>
                            </goals>
                            <phase>pre-site</phase>

                          </execution>

                        </executions>
                        <dependencies>
                          <dependency>
                            <groupId>org.docbook</groupId>
                            <artifactId>docbook-xml</artifactId>
                            <version>4.4</version>
                            <scope>runtime</scope>
                          </dependency>
                        </dependencies>
<configuration>
                             <sourceDirectory>${basedir}/src/docbkx</sourceDirectory>

<includes>**/jguard_step_by_step_eclipse.xml,**/en_jGuard_reference_master.xml,*
*/en_jGuard_reference_master_1.xml</includes>

<chunkedOutput>false</chunkedOutput>

<targetDirectory>${basedir}/target/site/docbkx</targetDirectory>

<xincludeSupported>true</xincludeSupported>

<imgSrcPath>../../../images/</imgSrcPath>

<monospaceVerbatimProperties>wrap</monospaceVerbatimProperties>

<htmlStylesheet>../../../css/jguard-docbook.css</htmlStylesheet>

<sectionAutolabel>1</sectionAutolabel>

<sectionLabelIncludesComponentLabel>1</sectionLabelIncludesComponentLabel>
                                                <!-- 
<htmlCustomization>${basedir}/src/docbkx/resources/xsl/jguard-docbook-html.xsl</
htmlCustomization>-->

<!--<foCustomization>src/docbook/resources/xsl/jguard-docbook-fopdf.xsl</foCusto
mization>
-->
<!--  <entities>
                                                                      <entity>

<name>version</name>

<value>${version}</value>

</entity>
/entities>-->
   </configuration>
</plugin>                       

cheers,

Charles.
http://www.jguard.net

Original issue reported on code.google.com by [email protected] on 30 Jun 2007 at 2:48

archetype: '\' instead of '/' in project path

What steps will reproduce the problem?
1. follow instructions at /wiki/UsingArchetypeTemplate

What is the expected output? What do you see instead?

expected successful 'mvn pre-site' run, but got error:

"Failure reading
/home/.../doc/\/home/.../doc/target/docbkx/generated/(gen)book.xml: no
protocol /home/.../doc/\/home/.../doc/target/docbkx/generated/(gen)book.xml"


What version of the product are you using? On what operating system?

2.0.10-SNAPSHOT on Linux

Please provide any additional information below.

The simple fix is to replace the leading '\' with '/' in
<generatedSourceDirectory>\${project.build.directory}/docbkx/generated</generate
dSourceDirectory>


Original issue reported on code.google.com by [email protected] on 1 Dec 2009 at 9:38

NullPointerException in docbkx:generate-pdf 2.0.8

What steps will reproduce the problem?
1.  mvn -e clean install

2. Plugin-declaration in the POM:

 <plugin>
                <groupId>com.agilejava.docbkx</groupId>
                <artifactId>docbkx-maven-plugin</artifactId>
                <version>2.0.8</version>
                <configuration>

<sourceDirectory>${basedir}/src/docbkx/sad</sourceDirectory>
                    <chapterAutolabel>1</chapterAutolabel>
                    <sectionAutolabel>1</sectionAutolabel>
                    <appendixAutolabel>1</appendixAutolabel>
                    <sectionLabelIncludesComponentLabel>
                        1
                    </sectionLabelIncludesComponentLabel>
                    <bodyStartIndent>0pt</bodyStartIndent>
                    <paperType>A4</paperType>
                    <fopExtensions>1</fopExtensions>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>generate-html</goal>
                            <goal>generate-pdf</goal>
                        </goals>
                        <phase>compile</phase>
                    </execution>
                </executions>
                <dependencies>
                    <dependency>
                        <groupId>org.docbook</groupId>
                        <artifactId>docbook-xml</artifactId>
                        <version>4.4</version>
                        <scope>runtime</scope>
                    </dependency>
                </dependencies>
            </plugin>

I can send you the docbook xml source separately if you need it to
reproduce this problem.

What is the expected output? What do you see instead?

Expected "BUILD SUCCESFUL" and a pdf-file.

Instead:

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to transform document.

Embedded error: java.lang.NullPointerException
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to transform
document.
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:564)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def
aultLifecycleExecutor.java:480)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor.java:459)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:311)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:278)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.java:143)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a: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: org.apache.maven.plugin.MojoExecutionException: Failed to
transform document.
        at
com.agilejava.docbkx.maven.AbstractPdfMojo.postProcessResult(AbstractPdfMojo.jav
a:93)
        at
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:174)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:447)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:539)
        ... 16 more
Caused by: javax.xml.transform.TransformerException:
java.lang.NullPointerException
        at
com.icl.saxon.IdentityTransformer.transform(IdentityTransformer.java:61)
        at
com.agilejava.docbkx.maven.AbstractPdfMojo.postProcessResult(AbstractPdfMojo.jav
a:85)
        ... 19 more
Caused by: java.lang.NullPointerException
        at
org.apache.fop.area.AreaTreeHandler.endDocument(AreaTreeHandler.java:264)
        at org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:171)
        at com.icl.saxon.aelfred.SAXDriver.parse(SAXDriver.java:334)
        at
com.icl.saxon.IdentityTransformer.transform(IdentityTransformer.java:59)
        ... 20 more
[INFO] ------------------------------------------------------------------------




What version of the product are you using? On what operating system?

Maven version: 2.0.8
Java version: 1.6.0_03
OS name: "linux" version: "2.6.22-14-generic" arch: "i386" Family: "unix"

Original issue reported on code.google.com by [email protected] on 10 Mar 2008 at 10:05

&myentity; entity replacement via <entites> configuration fails

What steps will reproduce the problem?
1. Run mvn compile on the attached entity-test.xml

What is the expected output? What do you see instead?

According to the description at
http://docbkx-tools.sourceforge.net/docbkx-samples/manual.html, "Example 6.
Entity substitution", the entity &version; should be replaced. Instead,
generation fails with

[INFO] Processing entity-test.xml
Error on line 5 column 40 of
file:///C:/Users/aphillips/Workspaces/Xebia/deployit/core/documentation/src/docb
kx/entity-t
est.xml:
  Error reported by XML parser: The entity "version" was referenced, but
not declared.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to transform entity-test.xml.

Embedded error: org.xml.sax.SAXParseException: The entity "version" was
referenced, but not declared.

What version of the product are you using? On what operating system?

Plugin version: 2.0.9
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_17
Java home: C:\Program Files\Java\jdk1.6.0_17\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"

Original issue reported on code.google.com by [email protected] on 25 Feb 2010 at 7:28

Attachments:

Problem to convert docbook file while using this plugin bhind a proxy with authentification

What steps will reproduce the problem?
1. if you use doc book through a proxy that require authentification you
got an error

mvn compile
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Docbkx Maven Samples
[INFO]    task-segment: [compile]
[INFO] ------------------------------------------------------------------------
[INFO] [docbkx:generate-html {execution: default}]
[INFO] Processing specification.xml
Error 
  Failure reading
/local/home/pdeville/Work/Java/storetech/build/latest/src/documentation/src/docb
kx/specification.xml:
Server returned HTTP response code: 401 for URL:
http://www3.cfauth.com/?cfru=aHR0cDovL3d3dy5vYXNpcy1vcGVuLm9yZy9kb2Nib29rL3htbC8
0LjIvZG9jYm9va3guZHRk
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to transform specification.xml.

Embedded error: Failure reading
/local/home/pdeville/Work/Java/storetech/build/latest/src/documentation/src/docb
kx/specification.xml
Server returned HTTP response code: 401 for URL:
http://www3.cfauth.com/?cfru=aHR0cDovL3d3dy5vYXNpcy1vcGVuLm9yZy9kb2Nib29rL3htbC8
0LjIvZG9jYm9va3guZHRk
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20 seconds
[INFO] Finished at: Wed Oct 01 08:48:53 CEST 2008
[INFO] Final Memory: 8M/26M
[INFO] ------------------------------------------------------------------------
pdeville@gislt1703:~/Work/Java/storetech/build/latest/src/documentation$
mvn -e compile
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Docbkx Maven Samples
[INFO]    task-segment: [compile]
[INFO] ------------------------------------------------------------------------
[INFO] [docbkx:generate-html {execution: default}]
[INFO] Processing specification.xml
Error 
  Failure reading
/local/home/pdeville/Work/Java/storetech/build/latest/src/documentation/src/docb
kx/specification.xml:
Server returned HTTP response code: 401 for URL:
http://www3.cfauth.com/?cfru=aHR0cDovL3d3dy5vYXNpcy1vcGVuLm9yZy9kb2Nib29rL3htbC8
0LjIvZG9jYm9va3guZHRk
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to transform specification.xml.

Embedded error: Failure reading
/local/home/pdeville/Work/Java/storetech/build/latest/src/documentation/src/docb
kx/specification.xml
Server returned HTTP response code: 401 for URL:
http://www3.cfauth.com/?cfru=aHR0cDovL3d3dy5vYXNpcy1vcGVuLm9yZy9kb2Nib29rL3htbC8
0LjIvZG9jYm9va3guZHRk
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to transform
specification.xml.
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:583)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def
aultLifecycleExecutor.java:499)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor.java:478)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:330)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:291)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.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.jav
a: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: Failed to
transform specification.xml.
        at
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:182)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:451)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:558)
        ... 16 more
Caused by: javax.xml.transform.TransformerException: Failure reading
/local/home/pdeville/Work/Java/storetech/build/latest/src/documentation/src/docb
kx/specification.xml
        at com.icl.saxon.om.Builder.build(Builder.java:267)
        at com.icl.saxon.Controller.transform(Controller.java:936)
        at
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:173)
        ... 18 more
Caused by: java.io.IOException: Server returned HTTP response code: 401 for
URL:
http://www3.cfauth.com/?cfru=aHR0cDovL3d3dy5vYXNpcy1vcGVuLm9yZy9kb2Nib29rL3htbC8
0LjIvZG9jYm9va3guZHRk
        at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.jav
a:1152)
        at
org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
        at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
        at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown
Source)
        at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown
Source)
        at
org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown
Source)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
        at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333)
        at com.icl.saxon.om.Builder.build(Builder.java:265)
        ... 20 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17 seconds
[INFO] Finished at: Wed Oct 01 08:49:34 CEST 2008
[INFO] Final Memory: 8M/26M
[INFO] ------------------------------------------------------------------------

Original issue reported on code.google.com by [email protected] on 1 Oct 2008 at 6:49

generate-manpages broken with the namespaced stylesheets

It seems that the namespaced docbook stylesheets are broken for the manpage
generation.

Version: 2.0.9-SNAPSHOT from trunk

How to reproduce?

mvn -Pdocbkx.multipleFormats generate-sources

What is the expected output? 

Build Successful

What do you see instead?

[INFO] [docbkx:generate-manpages {execution: default}]
[INFO] Processing sample2.xml
Error at xsl:strip-space on line 120 of
jar:file:/C:/Documents%20and%20Settings/Mimil/.m2/repository/com/agilejava/docbk
x/docbkx-maven-plugin/2.0.9-SNAPSHOT/docbkx-maven-plugin-2.0.9-SNAPSHOT.jar!/MET
A-INF/docbkx/manpages/other.xsl:
  Element name d:manvolnumdb:abstract is not a valid QName
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to build Transformer from jar:file:/C:/Documents and
Settings/Mimil/.m2/repository/com/agilejava/docbkx/docbkx-maven-plugin/2.0.9-SNA
PSHOT/docbkx-maven-plugin-2.0.9-SNAPSHOT.jar!/META-INF/docbkx/manpages/docbook.x
sl
Failed to compile stylesheet. 1 error detected.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
com.agilejava.docbkx.maven.TransformerBuilder$TransformerBuilderException:
Failed to build Transformer from jar:file:/C:/Documents and
Settings/Mimil/.m2/repository/com/agilejava/docbkx/docbkx-maven-plugin/2.0.9-SNA
PSHOT/docbkx-maven-plugin-2.0.9-SNAPSHOT.jar!/META-INF/docbkx/manpages/docbook.x
sl
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.cre
ateTransformer(AbstractTransformerMojo.java:637)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.bui
ld(AbstractTransformerMojo.java:582)
    at
com.agilejava.docbkx.maven.CachingTransformerBuilder.build(CachingTransformerBui
lder.java:34)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:223)
    at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:451)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:558)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def
aultLifecycleExecutor.java:499)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor.java:478)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:330)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:291)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.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.jav
a: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: 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:12
7)
    at
com.icl.saxon.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:
79)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.cre
ateTransformer(AbstractTransformerMojo.java:607)
    ... 21 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12 seconds
[INFO] Finished at: Fri Jan 30 20:58:24 CET 2009
[INFO] Final Memory: 14M/32M
[INFO] ------------------------------------------------------------------------

Please use labels and text to provide additional information.


Original issue reported on code.google.com by [email protected] on 30 Jan 2009 at 8:02

  • Merged into: #31

not compilable on Linux due to use of backslash

What steps will reproduce the problem?
1. just trying to compile the whole project on Linux

What version of the product are you using? On what operating system?
svn trunk rev. #33

Please provide any additional information below.

This patch fixes the problem:

pk@shrek ~/src/docbkx $ svn di
Index:
docbkx-builder-maven-plugin/src/main/java/com/agilejava/maven/docbkx/GeneratorMo
jo.java
===================================================================

---
docbkx-builder-maven-plugin/src/main/java/com/agilejava/maven/docbkx/GeneratorMo
jo.java
    (revision 33)
+++
docbkx-builder-maven-plugin/src/main/java/com/agilejava/maven/docbkx/GeneratorMo
jo.java
    (working copy)
@@ -281,7 +281,7 @@
     private void copyResources(ZipFileProcessor processor)
             throws MojoExecutionException {
         final File actualDirectory = new File(targetResourcesDirectory,
-                "META-INF\\docbkx");
+                "META-INF/docbkx");
         try {
             FileUtils.forceMkdir(actualDirectory);
         } catch (IOException ioe) {

Original issue reported on code.google.com by [email protected] on 30 Aug 2007 at 4:17

Docbkx Maven Plugin not in central Maven Repository

The Docbkx Maven Plugin is currently not available in the central Maven
Repository. The reason for that is mainly that uploading Maven plugins
requires a procedure that requires a server on the web with rsync
capabilities, registered on a domain that clearly identifies the unit of
work that you are trying to upload.

Or phrased differently:

"This is the preferred process. You first have to setup your project to
deploy to a remote repository .

You must make sure the remote repository server has rsync or rsync over
ssh, there are free services like Sourceforge that provide you ssh server
access .

After you are able to deploy to your remote repository make sure you only
deploy releases . Then you can provide a script like the current scripts ,
open an issue under MAVENUPLOAD and attach the script, and we'll add it to
the automatically synced repos.

Make sure you provide proof of owning the domain that matches the groupId
(see groupId considerations above). Proof means either the server to sync
from has a name under that domain, your name shows up in a prominent place
in the domain, or you provide a link to a whois database where your name
shows up as the domain owner.

If you are using ssh in your own server you need to add the maven public
key to the authorized ones to allow us to log in the machine."

Original issue reported on code.google.com by [email protected] on 24 Sep 2007 at 5:49

fo:flow is missing child elements

What steps will reproduce the problem?
1. mvn install

What is the expected output? What do you see instead?
Expected: Finished HTML and PDF files.
Instead: Error building:

[INFO] Failed to transform to PDF

Embedded error: org.apache.fop.fo.ValidationException: null:1:45993: 
Error(1/45993): fo:flow is 
missing child elements. 
Required Content Model: marker* (%block;)+


What version of the product are you using? On what operating system?
2.0.9 and 2.0.10-SNAPSHOT, linux

Please provide any additional information below.
This project had been building fine with docbkx-maven-plugin 2.0.8 for a long 
time, but 
recently we've started seeing this error:

[INFO] Trace
java.lang.ClassCastException: java.lang.String
        at com.agilejava.docbkx.maven.ExpressionUtils.splitToTree(ExpressionUtils.java:40)
        at com.agilejava.docbkx.maven.ExpressionUtils.splitToTree(ExpressionUtils.java:43)
        at com.agilejava.docbkx.maven.ExpressionUtils.createTree(ExpressionUtils.java:31)
        at 
com.agilejava.docbkx.maven.AbstractTransformerMojo$1.<init>(AbstractTransformerM
ojo.java:
151)
        at 
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:1
48)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:483)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:
678)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def
aultLifecycleEx
ecutor.java:540)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor.java:5
19)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecy
cleExecutor.java:371)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecu
tor.java:332)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.java:181)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a: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)

...and found the fix described in issue 20:
  http://code.google.com/p/docbkx-tools/issues/detail?id=20

I tried updating to 2.0.9 and get the failure mentioned above.  2.0.10-SNAPSHOT 
shows the 
same behavior.

I've tried disabling our custom fo, and it doesn't seem to help.

Attached is the project.

Original issue reported on code.google.com by [email protected] on 24 Feb 2010 at 7:18

Attachments:

Have a better handling of stylesheets generating their own output filenames

Some stylesheets (like manpages) seem to not allow the specification of the
output filename. The stylesheet is responsible of the filename.

As for now an empty output file is created in addition of what the
stylesheet generates and this may cause some misunderstandings of what is
supposed to be generated. 

Original issue reported on code.google.com by [email protected] on 16 Nov 2009 at 9:29

Processing instructions ignored with the embedded stylesheet

Hi, I noticed an issue with the plugin when trying the implement hard page
breaks as described in TCG
(http://www.sagehill.net/docbookxsl/PageBreaking.html). It seems that the
processing instructions are ignored if the stylesheet included in the
plugin is used.

I have a custom stylesheet defined like this:

<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0">

  <xsl:import href="urn:docbkx:stylesheet"/>

  <xsl:template match="processing-instruction('hard-pagebreak')">
    <fo:block break-after='page'/>
  </xsl:template>
</xsl:stylesheet>

With this the <?hard-pagebreak?> instructions in the document are ignored.

If I change the xsl:import to point to the stylesheet installed manually on
the system, the instruction is properly processed:

<xsl:import href="file:/C:/dev/docbook-xsl-1.73.2/fo/docbook.xsl"/>

This was tested with the 2.0.9 plugin.



Original issue reported on code.google.com by [email protected] on 30 Apr 2009 at 9:02

Bug in ExpressionUtils for certain property definitions

What steps will reproduce the problem?

1. In the POM that uses the docbkx plugin, add two properties of the form 
"a.b.c" and "a.b.c.d"
2. Run "mvn clean docbkx:generate-html" to process a DocBook file

What is the expected output? What do you see instead?

Instead of transforming the DocBook as usual, I get an exception:

java.lang.ClassCastException: java.lang.String cannot be cast to java.util.Map
    at com.agilejava.docbkx.maven.ExpressionUtils.splitToTree(ExpressionUtils.java:40)
    at com.agilejava.docbkx.maven.ExpressionUtils.splitToTree(ExpressionUtils.java:43)
    at com.agilejava.docbkx.maven.ExpressionUtils.createTree(ExpressionUtils.java:31)
    at 
com.agilejava.docbkx.maven.AbstractTransformerMojo$1.<init>(AbstractTransformerM
ojo.java:
165)
    at 
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:1
62)
    at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:451)
    at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:
558)
    at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(Defaul
tLifecycleExec
utor.java:512)
    at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor.java:4
82)
    at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecy
cleExecutor.java:330)
    at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecu
tor.java:291)
    at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.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.jav
a: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)

What version of the product are you using? On what operating system?

docbkx-maven-plugin 2.0.8

Please provide any additional information below.

This problem is caused by a bug in ExpressionUtils. The following code 
reproduces the error:

        Properties properties = new Properties();
        properties.setProperty("a.b.c", "foo");
        properties.setProperty("a.b.c.d", "bar");
        Map tree = ExpressionUtils.createTree(properties);


Original issue reported on code.google.com by [email protected] on 18 Dec 2008 at 7:47

Allow new languages to be added to the syntax highlighter

The syntax highlight works nicely but it cannot be easily extended - the
default languages are available in the jar alone and the user needs to set
a system property set already by the DocBkx.
It would be nice if the user could customize the languages by adding its
own language in, possibly even overriding the default ones without fiddling
with system properties but only by specifying the file and the language
that it belongs to.

Thanks,
 Costin

Original issue reported on code.google.com by [email protected] on 5 Apr 2008 at 12:38

Add a generate-text goal

It would be useful to also have a generation goal for a plain text document 
besides html and pdf.

Original issue reported on code.google.com by marcello.teodori on 8 Nov 2008 at 2:46

Add support for ePub format

Please add support for the ePub format.  Attached is a patch that I have tested 
against a forked 
version of the nexus-book project (http://github.com/jaxzin/nexus-book)

Original issue reported on code.google.com by brian.richard.jackson on 17 Mar 2010 at 7:10

NullPointerException if a language highlighting is not available

The docbkx plugin crashes with a NullPointerException if a language
highlighting is not available (for instance, bash) when defining the
language attribute of a programlisting element.

What steps will reproduce the problem?
1. put the following piece of code in a docbook xml file :
<programlisting language="bash">export APP_HOME=/some/path</programlisting>
2. activate the hightlighting in your pom :
<highlightSource>true</highlightSource>
3. run the generation

The expected output is as following :
java.lang.NullPointerException
        at net.sf.xslthl.ConnectorSaxon6.highlight(Unknown Source)
        at net.sf.xslthl.ConnectorSaxon6.highlight(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.icl.saxon.expr.FunctionProxy.call(FunctionProxy.java:582)
        at com.icl.saxon.expr.FunctionProxy.enumerate(FunctionProxy.java:462)
        at
com.icl.saxon.expr.NodeListExpression.enumerate(NodeListExpression.java:80)
        at com.icl.saxon.Controller.applyTemplates(Controller.java:206)
        at
com.icl.saxon.style.XSLApplyTemplates.process(XSLApplyTemplates.java:135)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLWhen.process(XSLWhen.java:72)
        at com.icl.saxon.style.XSLChoose.process(XSLChoose.java:96)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLWhen.process(XSLWhen.java:72)
        at com.icl.saxon.style.XSLChoose.process(XSLChoose.java:96)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at
com.icl.saxon.style.XSLCallTemplate.process(XSLCallTemplate.java:187)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at
com.icl.saxon.style.LiteralResultElement.process(LiteralResultElement.java:289)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLOtherwise.process(XSLOtherwise.java:48)
        at com.icl.saxon.style.XSLChoose.process(XSLChoose.java:96)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyTemplates(Controller.java:246)
        at
com.icl.saxon.style.XSLApplyTemplates.process(XSLApplyTemplates.java:135)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at
com.icl.saxon.style.LiteralResultElement.process(LiteralResultElement.java:289)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyImports(Controller.java:298)
        at com.icl.saxon.style.XSLApplyImports.process(XSLApplyImports.java:71)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at
com.icl.saxon.style.XSLGeneralVariable.getSelectValue(XSLGeneralVariable.java:23
8)
        at com.icl.saxon.style.XSLParam.process(XSLParam.java:76)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at
com.icl.saxon.style.XSLCallTemplate.process(XSLCallTemplate.java:187)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLOtherwise.process(XSLOtherwise.java:48)
        at com.icl.saxon.style.XSLChoose.process(XSLChoose.java:96)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyTemplates(Controller.java:246)
        at
com.icl.saxon.style.XSLApplyTemplates.process(XSLApplyTemplates.java:135)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at
com.icl.saxon.style.LiteralResultElement.process(LiteralResultElement.java:289)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyImports(Controller.java:298)
        at com.icl.saxon.style.XSLApplyImports.process(XSLApplyImports.java:71)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at
com.icl.saxon.style.XSLGeneralVariable.getSelectValue(XSLGeneralVariable.java:23
8)
        at com.icl.saxon.style.XSLParam.process(XSLParam.java:76)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at
com.icl.saxon.style.XSLCallTemplate.process(XSLCallTemplate.java:187)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLOtherwise.process(XSLOtherwise.java:48)
        at com.icl.saxon.style.XSLChoose.process(XSLChoose.java:96)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyTemplates(Controller.java:255)
        at
com.icl.saxon.style.XSLApplyTemplates.process(XSLApplyTemplates.java:135)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at
com.icl.saxon.style.LiteralResultElement.process(LiteralResultElement.java:289)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyImports(Controller.java:298)
        at com.icl.saxon.style.XSLApplyImports.process(XSLApplyImports.java:71)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at
com.icl.saxon.style.XSLGeneralVariable.getSelectValue(XSLGeneralVariable.java:23
8)
        at com.icl.saxon.style.XSLParam.process(XSLParam.java:76)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at
com.icl.saxon.style.XSLCallTemplate.process(XSLCallTemplate.java:187)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLOtherwise.process(XSLOtherwise.java:48)
        at com.icl.saxon.style.XSLChoose.process(XSLChoose.java:96)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyTemplates(Controller.java:255)
        at
com.icl.saxon.style.XSLApplyTemplates.process(XSLApplyTemplates.java:135)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyTemplates(Controller.java:255)
        at com.icl.saxon.Controller.defaultAction(Controller.java:271)
        at com.icl.saxon.Controller.applyTemplates(Controller.java:236)
        at
com.icl.saxon.style.XSLApplyTemplates.process(XSLApplyTemplates.java:135)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLIf.process(XSLIf.java:78)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLOtherwise.process(XSLOtherwise.java:48)
        at com.icl.saxon.style.XSLChoose.process(XSLChoose.java:96)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLOtherwise.process(XSLOtherwise.java:48)
        at com.icl.saxon.style.XSLChoose.process(XSLChoose.java:96)
        at
com.icl.saxon.style.StyleElement.processChildren(StyleElement.java:634)
        at com.icl.saxon.style.XSLTemplate.expand(XSLTemplate.java:225)
        at com.icl.saxon.style.XSLTemplate.start(XSLTemplate.java:198)
        at com.icl.saxon.Controller.applyTemplates(Controller.java:246)
        at com.icl.saxon.Controller.run(Controller.java:178)
        at com.icl.saxon.Controller.transformDocument(Controller.java:1086)
        at com.icl.saxon.Controller.transform(Controller.java:953)
        at
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:173)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:451)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:558)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def
aultLifecycleExecutor.java:499)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor.java:478)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:330)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:291)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.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.jav
a: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)
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR

What version of the product are you using? docbkx-maven-plugin 2.0.8
On what operating system? Ubuntu
Maven version: 2.0.9
Java version: 1.6.0_12
OS name: "linux" version: "2.6.24-23-generic" arch: "i386" Family: "unix"


Thank you for this great tool (the only really usable I found)!
Christophe.

Original issue reported on code.google.com by [email protected] on 20 Feb 2009 at 4:19

Enhance verbatim stylesheet in DocBook to be able to use dp.SyntaxHighlighter

Currently, the pre tag that is generated is lacking a language attribute
that SyntaxHighlighter can use to highlight the code. 
SyntaxHighlighter is a bit more extensible than the embedded highlighting.
The change is non invasive, it requires the addition of 

<xsl:if test="@language != ''">
  <xsl:attribute name="language">
     <xsl:value-of select="@language"/>  
  </xsl:attribute>
</xsl:if>

at line 56 and 64 in verbatim.xsl. The pre tag will then also contain the
language attribute.

Original issue reported on code.google.com by [email protected] on 3 Jul 2009 at 2:58

QandASet works for html generation but fails for pdf generation.

Hi Wilfred,
i've tried to use QandASet (questions and answers docbook set)  but it only
works for html generation.
the issue seems to be caused by FOP.

i've not saved the stack trace, but it was saying  'ID already exists' for
a 'question' (the id generated was used on the previous page).

one good thing would be to highlight this bug on your documentation.

cheers,

Charles.
www.jguard.net

ps: you can see some html and pdf documentation generated by your great
plugin here:
http://jguard.sourceforge.net/mvnsite/
ps2: when will you upgrade the docbook XSL used by your plugin?
ps3: many thanks for your great work!

Original issue reported on code.google.com by [email protected] on 20 Jul 2007 at 8:13

TransformerConfigurationException while building man pages

When I built the man pages for an app I am working on with docbkx version
2.0.9 I received the following exception:

Error at xsl:strip-space on line 120 of
jar:file:/Users/thomas/.m2/repository/com/agilejava/docbkx/docbkx-maven-plugin/2
.0.9/docbkx-maven-plugin-2.0.9.jar!/META-INF/docbkx/manpages/other.xsl:
  Element name d:manvolnumdb:abstract is not a valid QName
Exception in thread "main"
com.agilejava.docbkx.maven.TransformerBuilder$TransformerBuilderException:
Failed to build Transformer from
jar:file:/Users/thomas/.m2/repository/com/agilejava/docbkx/docbkx-maven-plugin/2
.0.9/docbkx-maven-plugin-2.0.9.jar!/META-INF/docbkx/manpages/docbook.xsl
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.cre
ateTransformer(AbstractTransformerMojo.java:634)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.bui
ld(AbstractTransformerMojo.java:579)
    at
com.agilejava.docbkx.maven.CachingTransformerBuilder.build(CachingTransformerBui
lder.java:34)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:220)
    at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:579)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:498)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject
(DefaultLifecycleExecutor.java:265)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:180)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.java:149)
    at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
    at
org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
    at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:9
04)
    at
org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder
.java:304)
    at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
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:12
7)
    at
com.icl.saxon.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:
79)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.cre
ateTransformer(AbstractTransformerMojo.java:604)
    ... 17 more

After some digging we fixed the issue by changing the line:
d:manvolnumdb:abstract
to:
d:manvolnum
db:abstract

in /META-INF/docbkx/manpages/other.xsl.


Original issue reported on code.google.com by [email protected] on 26 Mar 2009 at 3:31

Enhancement of urn:docbkx:stylesheet

Enhancement of urn:docbkx:stylesheet which points to the docbook release
stylesheet to allow urn:docbkx:stylesheet/xxxx to point to other files of
the docbook release.
Usefull for docbook XSLT customization

Example: <import href="urn:docbkx:stylesheet/pagesetup.xsl" />

Original issue reported on code.google.com by [email protected] on 18 Mar 2009 at 9:44

Generation is slow

The generation is very slow. I think docbkx is downloading
all the dtds for each file from the internet. If i remove
the dtds from the xml, generation is fast.

Original issue reported on code.google.com by [email protected] on 18 Jan 2010 at 8:45

plugin does not support attribute-set

Hi,
i want to break long lines in a programlisting automatically.
i've seen here
(http://www.sagehill.net/docbookxsl/ProgramListings.html#BreakLongLines ) ,
that we can do it with docbook by 'setting the wrap-option attribute in the
monospace.verbatim.properties attribute-set'.
'monospaceVerbatimProperties' maven2 parameter matches the original XSL
attribute 'monospace.verbatim.properties'.

how to set the 'wrap-option' attribute to the 'wrap' value?
in the same way, i want to set the 'hyphenation-character' to '\' to
highlight break lines.

thanks for your great plugin!

cheers,

Charles.
http://www.jguard.net

Original issue reported on code.google.com by [email protected] on 6 Jun 2007 at 8:44

html generation accept relative img src path , but not pdf generation

Hi,
i'v got many issues with images src directory path to geenrate html and pdf.
i can include a relative path in the configuration and this path  will be
included in the html generated : all is fine.
but when i generate pdf, it does not resolve relative url; we have to put
the absolute url.
but if we put the absolute url, the html generated willnot be sueful for
other people which read the html content (image path will be different).

one way would be to set the imgSrcPath  with the ${baseUrl}, and to set the
keepRelativeImageUris too, but it doesn't seem to work.

so, to solve this problem, i've put all the images in the same drirectory
than docbook xml files, and i've set the absolute path of the img src
directory in the XSL used to generate PDF. with this configuration, only 
the pdf generation use absolute url.
cheers,

Charles.
http://www.jguard.net
http://www.jguard.net

Original issue reported on code.google.com by [email protected] on 7 Jul 2007 at 5:14

xsl:number not evaluated correctly in custom layer template

What steps will reproduce the problem?
1. I tried to to a "striped" table as mentioned in
http://www.sagehill.net/docbookxsl/PrintTableStyles.html#table.row.properties

What is the expected output? What do you see instead?
The striped style wasn't applied to the table. I think it's because
<xsl:number ../> isn't evaluated correctly, i.e. it isn't able to determine
the current row number.

What version of the product are you using? On what operating system?
I tried docbkx 2.0.9 and 2.0.10-SNAPSHOT





Original issue reported on code.google.com by [email protected] on 23 Feb 2010 at 7:20

Allow static urn:docbkx:... reference for images

As explained in
http://groups.google.com/group/docbkx-tools-users/browse_thread/thread/1c1cdce1c
eda9c5f?hl=en
it would be nice to allow urn:docbkx:... static reference to be used in
image paths.

Original issue reported on code.google.com by [email protected] on 2 May 2009 at 6:27

Tables built with 2.0.8 no longer build with 2.0.9, column-number ValidationException

What steps will reproduce the problem?
1. xml (with several long tables) was created and built successfully using
a local xsl to create pdf using docbkx-maven-plugin 2.0.8
2. same xml and same xsl build attempted using 2.0.9 fails with following error
3.

What is the expected output? What do you see instead?
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to transform to PDF

Embedded error: org.apache.fop.fo.ValidationException: Error(1180/1188):
column-number or number of
cells in the row overflows the number of fo:table-column specified for the
table.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to transform
to PDF
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecuto
.java:719)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def
aultLife
ycleExecutor.java:556)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor
java:535)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(Default
ifecycleExecutor.java:387)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycle
xecutor.java:348)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.jav
: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.jav
a: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: org.apache.maven.plugin.MojoExecutionException: Failed to
transform to PDF
        at
com.agilejava.docbkx.maven.AbstractPdfMojo.postProcessResult(AbstractPdfMojo.jav
a:117)
        at
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:
24)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:490)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecuto
.java:694)
        ... 17 more
Caused by: javax.xml.transform.TransformerException:
org.apache.fop.fo.ValidationException: Error(1
80/1188): column-number or number of cells in the row overflows the number
of fo:table-column speci
ied for the table.
        at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdenti
tyImpl.j
va:501)
        at
com.agilejava.docbkx.maven.AbstractPdfMojo.postProcessResult(AbstractPdfMojo.jav
a:105)
        ... 20 more
Caused by: org.apache.fop.fo.ValidationException: Error(1180/1188):
column-number or number of cell
 in the row overflows the number of fo:table-column specified for the table.
        at
org.apache.fop.fo.flow.table.TableCellContainer.addTableCellChild(TableCellConta
iner.jav
:50)
        at org.apache.fop.fo.flow.table.TableRow.addChildNode(TableRow.java:94)
        at
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:31
7)
        at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:163)
        at
org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIde
ntityImp
.java:1072)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
        at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.
dispatch
Unknown Source)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdenti
tyImpl.j
va:484)
        ... 21 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21 seconds
[INFO] Finished at: Fri Nov 13 15:36:38 EST 2009
[INFO] Final Memory: 54M/254M
[INFO] ------------------------------------------------------------------------

What version of the product are you using? On what operating system?
moved from 2.0.8. to 2.0.9 in a windows environment w/ maven 4.0

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 13 Nov 2009 at 8:58

Accept http url for foCustomization parameter

What steps will reproduce the problem?
1. Add any http:// url to the foCustomization parameter and run plugin to
generate pdf.

Got the trace below.  Any plans support remote stylesheets?

[INFO] Trace
com.agilejava.docbkx.maven.TransformerBuilder$TransformerBuilderException:
Failed to read stylesheet from
file:/home/all/work/project/http:/testserver/docbkx/fo-styles.xsl
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.cre
ateTransformer(AbstractTransformerMojo.java:491)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.bui
ld(AbstractTransformerMojo.java:453)
    at
com.agilejava.docbkx.maven.CachingTransformerBuilder.build(CachingTransformerBui
lder.java:34)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:171)
    at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:451)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycl
eExecutor.java:558)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Def
aultLifecycleExecutor.java:499)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycle
Executor.java:478)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:330)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultL
ifecycleExecutor.java:291)
    at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExec
utor.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.jav
a: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.FileNotFoundException:
/home/all/work/project/http:/testserver/docbkx/fo-styles.xsl (No such file
or directory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at java.io.FileInputStream.<init>(FileInputStream.java:66)
    at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
    at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.jav
a:161)
    at java.net.URL.openStream(URL.java:1009)
    at
com.agilejava.docbkx.maven.AbstractTransformerMojo$DefaultTransformerBuilder.cre
ateTransformer(AbstractTransformerMojo.java:476)

Original issue reported on code.google.com by [email protected] on 29 Jan 2009 at 12:22

profiles

Hi, 
I would like to know if profiles works with docbkx. 
I have tried to put some "audience" parameters in my book and 
add a profile.audience xsl parameter but it doesnot seem to work. 
I have changed the stylesheet to docbook-profile.xsl too. 
Thanks for your answer. 

Original issue reported on code.google.com by [email protected] on 21 Jan 2010 at 8:30

profiling stylesheets partly missing

What steps will reproduce the problem?
1. create a simple maven project using this plugin
2. write a stylesheet that uses <xsl:import
href="urn:docbkx:stylesheet/profile-chunk.xsl"/> and reference it with
htmlCustomization
3. try to build


What is the expected output? What do you see instead?
I'd like to use profiling with the standard stylesheets to prduce different
outputs using different profiles.
This is what I get:
Error at xslo:include on line 398 of
jar:file:/home/bvoigt/.m2/repository/com/agilejava/docbkx/docbkx-maven-plugin/2.
0.9/docbkx-maven-plugin-2.0.9.jar!/META-INF/docbkx/html/profile-chunk-code.xsl:
  Failure reading
jar:file:/home/bvoigt/.m2/repository/com/agilejava/docbkx/docbkx-maven-plugin/2.
0.9/docbkx-maven-plugin-2.0.9.jar!/META-INF/docbkx/profiling/profile-mode.xsl:
JAR entry META-INF/docbkx/profiling/profile-mode.xsl not found in
/home/bvoigt/.m2/repository/com/agilejava/docbkx/docbkx-maven-plugin/2.0.9/docbk
x-maven-plugin-2.0.9.jar

And thats right, dockbx-plugin jar is missing the profiling folder, which
is included in the docbook-xsl distribution.


What version of the product are you using? On what operating system?
2.0.9 of the plugin, but all versions are missing the folder.

Original issue reported on code.google.com by [email protected] on 10 Jul 2009 at 1:29

ClassCastException in transform when cargo.container.url property is present in pom.xml

What steps will reproduce the problem?
1. create a project using an archetype from appfuse, where you can see the 
following property in 
the pom.xml:
<cargo.container.url>http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.14/bin/
apache-
tomcat-6.0.14.zip</cargo.container.url>
2. add a docbkx plugin definition and some docbook files
3. execute mvn clean site

What is the expected output? What do you see instead?
The transform should be performed, instead I get:

[INFO] [docbkx:generate-pdf {execution: build-pdf-doc}]
[INFO] ---------------------------------------------------------------------

---
[ERROR] FATAL ERROR
[INFO] ---------------------------------------------------------------------

---
[INFO] java.lang.String
[INFO] ---------------------------------------------------------------------

---
[INFO] Trace
java.lang.ClassCastException: java.lang.String
    at com.agilejava.docbkx.maven.ExpressionUtils.splitToTree(ExpressionUtils.java:40)
    at com.agilejava.docbkx.maven.ExpressionUtils.splitToTree(ExpressionUtils.java:43)
    at com.agilejava.docbkx.maven.ExpressionUtils.createTree(ExpressionUtils.java:31)
    at 
com.agilejava.docbkx.maven.AbstractTransformerMojo$1.<init>(AbstractTransformerM
ojo.java:
148)
    at 
com.agilejava.docbkx.maven.AbstractTransformerMojo.execute(AbstractTransformerMo
jo.java:1
45)
    at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.ja
va:447)

If I remove the cargo.container.url property, everything works correctly, looks 
like somehow 
Maven does not interpret it as a string and issues the ClassCastException.

Original issue reported on code.google.com by marcello.teodori on 15 Feb 2008 at 2:08

PostProcess doesn't resolve parent properties

What steps will reproduce the problem?
1. Define a copy action on postProcess configuration parameter using
properties of the parent project
2. Run docbkx:generate-html

What is the expected output? What do you see instead?

Properties of the parent project are properly resolved.
Properties are not resolved and stays ${xxx} in the ant script.

What version of the product are you using? On what operating system?

Using version 2.0.8 on Windows XP.

Please provide any additional information below.

Example:
<postProcess>
  <copy todir="${project.build.directory}/site/css"
file="${parent.basedir}/src/manual/css/manual.css" />
</postProcess>

The "project.build.directory" is correctly replaced but anything starting
with "parent." is not.

Original issue reported on code.google.com by [email protected] on 18 Feb 2009 at 8:05

Chunked HTML output to separate directories

When using chunked HTML output, files could potentially get in each others
way. In order to prevent this, it would be ideal to have dedicated
directories for each chunked HTML document.

Original issue reported on code.google.com by [email protected] on 11 Jun 2007 at 5:33

generate-javahelp goal

I recently started using docbkx to generate html and pdf docs for a java
tool I'm working on. Would it be possible to add a javahelp target along
with these?


Original issue reported on code.google.com by thomas%[email protected] on 20 Feb 2009 at 11:07

Add olink support

olink allows cross-document linking.

I think there are 2 phases:
- modify the plugin in order to allow targetsFilename (*.target.db) to be
specified when multiples docbook sources are proceeded within a single
maven execution
- create a mojo in order to generate the targetDatabaseDocument file

@see
http://groups.google.com/group/docbkx-tools-users/browse_thread/thread/252f0ca5a
02b2590

Original issue reported on code.google.com by [email protected] on 8 May 2009 at 11:01

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.