[jira] Commented: (DOXIA-402) Multi-module project with .confluence content does not work
[ http://jira.codehaus.org/browse/DOXIA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=231656#action_231656 ] Nathan Sowatskey commented on DOXIA-402: Many thanks for that. For my larger project that exhibited the original problem, I did have the additional dependency for the confluence extension in my module pom.xml, but *not* in the parent, so the results I was trying to generalise were badly configured. For the record, I now have this in the parent pom or my larger project: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.1.1/version dependencies dependency groupIdorg.apache.maven.doxia/groupId artifactIddoxia-core/artifactId version1.1.3/version /dependency dependency groupIdorg.apache.maven.doxia/groupId artifactIddoxia-module-confluence/artifactId version1.1.3/version /dependency /dependencies /plugin Hopefully this will help the next person who stumbles down this path :-) Multi-module project with .confluence content does not work --- Key: DOXIA-402 URL: http://jira.codehaus.org/browse/DOXIA-402 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.1.3 Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac Reporter: Nathan Sowatskey Priority: Blocker Attachments: apt-site-test.zip, confluence-site-test.zip There are two projects attached. The apt-site-test has the parent content in apt format. When building a multi-module project the content in the apt-site-test appears as expected. The confluence-site-test has the parent content in confluence format. That content does not appear as expected. Instead a generic about page is created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-398) TOC for .confluence doesn't seem to work
[
http://jira.codehaus.org/browse/DOXIA-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=231657#action_231657
]
Nathan Sowatskey commented on DOXIA-398:
http://jira.codehaus.org/browse/DOXIA-402 has been fixed.
So, I am just left with the lack of TOC, and the linkable sections that I hope
will derive from that.
I will hang fire on giving up entirely until someone with Confluence knowledge
can comment.
TOC for .confluence doesn't seem to work
Key: DOXIA-398
URL: http://jira.codehaus.org/browse/DOXIA-398
Project: Maven Doxia
Issue Type: Bug
Components: Module - Confluence
Affects Versions: 1.1.3
Environment: mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
Reporter: Nathan Sowatskey
Attachments: toc_test_case.zip
Please see attached test case.
The {toc} macro in the index.confluence doesn't seem to work. There is no TOC
produced, just the literal text of the toc macro itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-398) TOC for .confluence doesn't seem to work
[
http://jira.codehaus.org/browse/DOXIA-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=231570#action_231570
]
Nathan Sowatskey commented on DOXIA-398:
Hi
This is a major problem, so I am trying to figure out whether I should give up
on the Confluence markup and just use the apt.
Any input would help.
Many thanks
Nathan
TOC for .confluence doesn't seem to work
Key: DOXIA-398
URL: http://jira.codehaus.org/browse/DOXIA-398
Project: Maven Doxia
Issue Type: Bug
Components: Module - Confluence
Affects Versions: 1.1.3
Environment: mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
Reporter: Nathan Sowatskey
Attachments: toc_test_case.zip
Please see attached test case.
The {toc} macro in the index.confluence doesn't seem to work. There is no TOC
produced, just the literal text of the toc macro itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-398) TOC for .confluence doesn't seem to work
[
http://jira.codehaus.org/browse/DOXIA-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=231581#action_231581
]
Nathan Sowatskey commented on DOXIA-398:
Thanks for the update.
I have seen that the macros won't work.
It isn't clear that this also implies that the Confluence syntax for generating
a TOC won't work though.
So, just to be clear, is there any way to create a TOC for .confluence content
in a Maven site?
TOC for .confluence doesn't seem to work
Key: DOXIA-398
URL: http://jira.codehaus.org/browse/DOXIA-398
Project: Maven Doxia
Issue Type: Bug
Components: Module - Confluence
Affects Versions: 1.1.3
Environment: mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
Reporter: Nathan Sowatskey
Attachments: toc_test_case.zip
Please see attached test case.
The {toc} macro in the index.confluence doesn't seem to work. There is no TOC
produced, just the literal text of the toc macro itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-402) Multi-module project with .confluence content does not work
Multi-module project with .confluence content does not work --- Key: DOXIA-402 URL: http://jira.codehaus.org/browse/DOXIA-402 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.1.3 Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac Reporter: Nathan Sowatskey Priority: Blocker Attachments: apt-site-test.zip, confluence-site-test.zip There are two projects attached. The apt-site-test has the parent content in apt format. When building a multi-module project the content in the apt-site-test appears as expected. The confluence-site-test has the parent content in confluence format. That content does not appear as expected. Instead a generic about page is created. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-398) TOC for .confluence doesn't seem to work
[
http://jira.codehaus.org/browse/DOXIA-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=231585#action_231585
]
Nathan Sowatskey commented on DOXIA-398:
Thanks for looking.
I also raised:
http://jira.codehaus.org/browse/DOXIA-402
It looks like the .confluence option for Maven sites is not really ready yet.
TOC for .confluence doesn't seem to work
Key: DOXIA-398
URL: http://jira.codehaus.org/browse/DOXIA-398
Project: Maven Doxia
Issue Type: Bug
Components: Module - Confluence
Affects Versions: 1.1.3
Environment: mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
Reporter: Nathan Sowatskey
Attachments: toc_test_case.zip
Please see attached test case.
The {toc} macro in the index.confluence doesn't seem to work. There is no TOC
produced, just the literal text of the toc macro itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-399) Links with '_' and '-' don't work
Links with '_' and '-' don't work - Key: DOXIA-399 URL: http://jira.codehaus.org/browse/DOXIA-399 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.1.3 Environment: mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac Reporter: Nathan Sowatskey Priority: Blocker Attachments: toc-test-case.zip See links.confluence in the attached project. Neither the link to PAC or WPAD are rendered properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-399) Links with '_' and '-' don't work
[ http://jira.codehaus.org/browse/DOXIA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Sowatskey updated DOXIA-399: --- Attachment: toc-test-case.zip Fixed/updated test case showing slight fix using \. Links with '_' and '-' don't work - Key: DOXIA-399 URL: http://jira.codehaus.org/browse/DOXIA-399 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.1.3 Environment: mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac Reporter: Nathan Sowatskey Priority: Blocker Attachments: toc-test-case.zip, toc-test-case.zip See links.confluence in the attached project. Neither the link to PAC or WPAD are rendered properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-399) Links with '_' and '-' don't work
[ http://jira.codehaus.org/browse/DOXIA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Sowatskey updated DOXIA-399: --- Attachment: toc-test-case.zip Workaround with '\' before all '_'s. Links with '_' and '-' don't work - Key: DOXIA-399 URL: http://jira.codehaus.org/browse/DOXIA-399 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.1.3 Environment: mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac Reporter: Nathan Sowatskey Priority: Blocker Attachments: toc-test-case.zip, toc-test-case.zip, toc-test-case.zip See links.confluence in the attached project. Neither the link to PAC or WPAD are rendered properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-399) Links with '_' and '-' don't work
[ http://jira.codehaus.org/browse/DOXIA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Sowatskey closed DOXIA-399. -- Resolution: Fixed Use '\_' in links. For example: [PAC|http://en.wikipedia.org/wiki/Proxy\_auto-config] [WPAD|http://en.wikipedia.org/wiki/Web\_Proxy\_Autodiscovery\_Protocol] Links with '_' and '-' don't work - Key: DOXIA-399 URL: http://jira.codehaus.org/browse/DOXIA-399 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.1.3 Environment: mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac Reporter: Nathan Sowatskey Priority: Blocker Attachments: toc-test-case.zip, toc-test-case.zip, toc-test-case.zip See links.confluence in the attached project. Neither the link to PAC or WPAD are rendered properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-399) Links with '_' and '-' don't work
[ http://jira.codehaus.org/browse/DOXIA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229307#action_229307 ] Nathan Sowatskey commented on DOXIA-399: I provided a workaround in the attached project. Since there is a workaround, this is not a blocker. This Jira doesn't seem to let me change the priority, so I resolved it. Anyone looking for the same bug will see the workaround. If you want to re-open this for a code change, that's good too, but your choice :-) Links with '_' and '-' don't work - Key: DOXIA-399 URL: http://jira.codehaus.org/browse/DOXIA-399 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Affects Versions: 1.1.3 Environment: mvn -version Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_20 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac Reporter: Nathan Sowatskey Priority: Blocker Attachments: toc-test-case.zip, toc-test-case.zip, toc-test-case.zip See links.confluence in the attached project. Neither the link to PAC or WPAD are rendered properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-398) TOC for .confluence doesn't seem to work
TOC for .confluence doesn't seem to work
Key: DOXIA-398
URL: http://jira.codehaus.org/browse/DOXIA-398
Project: Maven Doxia
Issue Type: Bug
Components: Module - Confluence
Affects Versions: 1.1.3
Environment: mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.6.4 arch: x86_64 Family: mac
Reporter: Nathan Sowatskey
Attachments: toc_test_case.zip
Please see attached test case.
The {toc} macro in the index.confluence doesn't seem to work. There is no TOC
produced, just the literal text of the toc macro itself.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-356) Relative URLs for images don't work with PDF
Relative URLs for images don't work with PDF Key: DOXIA-356 URL: http://jira.codehaus.org/browse/DOXIA-356 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.2 Environment: OSX 10.5.7, Java 5 Reporter: Nathan Sowatskey Hi With APT based sites only, one can use a relative URL for images: [../images/picture.jpg] With the PDF generation though, this won't work, so we need to have: [http://site/images/picture.jpg] Is there a good reason for this. Can it be changed? Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=184963#action_184963 ] Nathan Sowatskey commented on DOXIA-338: Hi What is the status on this patch please? Thanks Nathan Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Assignee: Vincent Siveton Attachments: DOXIA-338.diff, doxia-site-test.zip, doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-348) Doxia 1.1.2-SNAPSHOT won't build with a clean repository
[
http://jira.codehaus.org/browse/DOXIA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Sowatskey closed DOXIA-348.
--
Resolution: Not A Bug
A workaround is available.
Doxia 1.1.2-SNAPSHOT won't build with a clean repository
Key: DOXIA-348
URL: http://jira.codehaus.org/browse/DOXIA-348
Project: Maven Doxia
Issue Type: Bug
Affects Versions: 1.2
Environment: OSX 10.5.7, Java 5, Maven 2.1
Reporter: Nathan Sowatskey
Hi
I deleted my repository to test that 1.1.2-SNAPSHOT would build for others.
But:
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-8/doxia-decoration-model-1.0-alpha-8.jar
39K downloaded (doxia-decoration-model-1.0-alpha-8.jar)
520K downloaded (bcel-5.2.jar)
[INFO] [clirr:check {execution: default}]
[INFO] Comparing to version: 1.1
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom
14K downloaded (doxia-1.1.pom)
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Cannot open
/Users/xxx/.m2/repository/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom for
reading
error in opening zip file
[INFO]
[INFO] Trace
net.sf.clirr.core.CheckerException: Cannot open
/Users/nsowatsk/.m2/repository/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom
for reading
at
net.sf.clirr.core.internal.bcel.BcelTypeArrayBuilder.createClassSet(BcelTypeArrayBuilder.java:73)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.resolvePreviousReleaseClasses(AbstractClirrMojo.java:306)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:192)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:182)
at
org.codehaus.mojo.clirr.ClirrCheckMojo.execute(ClirrCheckMojo.java:68)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-347) Nested APT file directories and PDF generation
[ http://jira.codehaus.org/browse/DOXIA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=183649#action_183649 ] Nathan Sowatskey commented on DOXIA-347: Thanks. It doesn't work. Would you like to me to provide a test case to help facilitate a fix, or is the description sufficient? Nested APT file directories and PDF generation -- Key: DOXIA-347 URL: http://jira.codehaus.org/browse/DOXIA-347 Project: Maven Doxia Issue Type: New Feature Components: Book Affects Versions: 1.2 Environment: OSX 10.5.7, Java 5, Maven 2.2 Reporter: Nathan Sowatskey Hi I have a chapter declared like this in xxx.xml: chapter idxxx_Integration/id titlexxx Integration/title sections section idxxx/index/id /section /sections /chapter Where: src/site/apt/xxx/integraion Contains some documentation specific to xxx. When I try to use mvn site with this config in pom.xml: book directorysrc/site/apt/directory descriptorsrc/site/xxx.xml/descriptor formats format idpdf/id /format /formats /book I get this error: ERROR] BUILD ERROR [INFO] [INFO] Error while generating book in format 'pdf'. Embedded error: No document that matches section with id=xxx/index. I don't know whether this *should* work, or whether this is a new feature request. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-348) Doxia 1.1.2-SNAPSHOT won't build with a clean repository
Doxia 1.1.2-SNAPSHOT won't build with a clean repository
Key: DOXIA-348
URL: http://jira.codehaus.org/browse/DOXIA-348
Project: Maven Doxia
Issue Type: Bug
Affects Versions: 1.2
Environment: OSX 10.5.7, Java 5, Maven 2.1
Reporter: Nathan Sowatskey
Hi
I deleted my repository to test that 1.1.2-SNAPSHOT would build for others. But:
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-8/doxia-decoration-model-1.0-alpha-8.jar
39K downloaded (doxia-decoration-model-1.0-alpha-8.jar)
520K downloaded (bcel-5.2.jar)
[INFO] [clirr:check {execution: default}]
[INFO] Comparing to version: 1.1
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom
14K downloaded (doxia-1.1.pom)
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Cannot open
/Users/xxx/.m2/repository/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom for
reading
error in opening zip file
[INFO]
[INFO] Trace
net.sf.clirr.core.CheckerException: Cannot open
/Users/nsowatsk/.m2/repository/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom
for reading
at
net.sf.clirr.core.internal.bcel.BcelTypeArrayBuilder.createClassSet(BcelTypeArrayBuilder.java:73)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.resolvePreviousReleaseClasses(AbstractClirrMojo.java:306)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:192)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:182)
at
org.codehaus.mojo.clirr.ClirrCheckMojo.execute(ClirrCheckMojo.java:68)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-348) Doxia 1.1.2-SNAPSHOT won't build with a clean repository
[
http://jira.codehaus.org/browse/DOXIA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=183376#action_183376
]
Nathan Sowatskey commented on DOXIA-348:
A work around is to build doxia 1.1 locally, then mvn clean 1.1.2, then the
build works.
Doxia 1.1.2-SNAPSHOT won't build with a clean repository
Key: DOXIA-348
URL: http://jira.codehaus.org/browse/DOXIA-348
Project: Maven Doxia
Issue Type: Bug
Affects Versions: 1.2
Environment: OSX 10.5.7, Java 5, Maven 2.1
Reporter: Nathan Sowatskey
Hi
I deleted my repository to test that 1.1.2-SNAPSHOT would build for others.
But:
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-8/doxia-decoration-model-1.0-alpha-8.jar
39K downloaded (doxia-decoration-model-1.0-alpha-8.jar)
520K downloaded (bcel-5.2.jar)
[INFO] [clirr:check {execution: default}]
[INFO] Comparing to version: 1.1
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom
14K downloaded (doxia-1.1.pom)
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Cannot open
/Users/xxx/.m2/repository/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom for
reading
error in opening zip file
[INFO]
[INFO] Trace
net.sf.clirr.core.CheckerException: Cannot open
/Users/nsowatsk/.m2/repository/org/apache/maven/doxia/doxia/1.1/doxia-1.1.pom
for reading
at
net.sf.clirr.core.internal.bcel.BcelTypeArrayBuilder.createClassSet(BcelTypeArrayBuilder.java:73)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.resolvePreviousReleaseClasses(AbstractClirrMojo.java:306)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:192)
at
org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:182)
at
org.codehaus.mojo.clirr.ClirrCheckMojo.execute(ClirrCheckMojo.java:68)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-347) Nested APT file directories and PDF generation
Nested APT file directories and PDF generation -- Key: DOXIA-347 URL: http://jira.codehaus.org/browse/DOXIA-347 Project: Maven Doxia Issue Type: New Feature Components: Book Affects Versions: 1.2 Environment: OSX 10.5.7, Java 5, Maven 2.2 Reporter: Nathan Sowatskey Hi I have a chapter declared like this in xxx.xml: chapter idxxx_Integration/id titlexxx Integration/title sections section idxxx/index/id /section /sections /chapter Where: src/site/apt/xxx/integraion Contains some documentation specific to xxx. When I try to use mvn site with this config in pom.xml: book directorysrc/site/apt/directory descriptorsrc/site/xxx.xml/descriptor formats format idpdf/id /format /formats /book I get this error: ERROR] BUILD ERROR [INFO] [INFO] Error while generating book in format 'pdf'. Embedded error: No document that matches section with id=xxx/index. I don't know whether this *should* work, or whether this is a new feature request. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=183046#action_183046 ] Nathan Sowatskey commented on DOXIA-338: Hi What is the status on this patch please? Thanks Nathan Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Attachments: DOXIA-338.diff, doxia-site-test.zip, doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=181090#action_181090 ] Nathan Sowatskey commented on DOXIA-338: Has this been applied yet? Thanks Nathan Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Attachments: DOXIA-338.diff, doxia-site-test.zip, doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=180457#action_180457 ] Nathan Sowatskey commented on DOXIA-338: For the second goal you suggested, I got: Scanning for projects... [INFO] Searching repository for plugin with prefix: 'pdf'. [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-pdf-plugin: checking for updates from central [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-pdf-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 5 seconds [INFO] Finished at: Tue Jun 16 15:42:04 CEST 2009 [INFO] Final Memory: 2M/4M [INFO] Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Attachments: DOXIA-338.diff, doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Sowatskey updated DOXIA-338: --- Attachment: doxia-site-test.zip Look at the pdf in target, and maybe some other clues in target also. Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Attachments: DOXIA-338.diff, doxia-site-test.zip, doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-338) Section numbering and links
[ http://jira.codehaus.org/browse/DOXIA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=180150#action_180150 ] Nathan Sowatskey commented on DOXIA-338: Hi Thanks for looking at this. The link that does not work is in the body of the section. The TOC links work, the one in the body of the text doesn't. Regards Nathan Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Attachments: doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-338) Section numbering and links
Section numbering and links --- Key: DOXIA-338 URL: http://jira.codehaus.org/browse/DOXIA-338 Project: Maven Doxia Issue Type: Bug Components: Book Affects Versions: 1.1.1 Environment: Java 5, OSX 10.5.7, Maven 2.1.0 Reporter: Nathan Sowatskey Attachments: doxia-site-test.zip Hi The attached project exhibits two issues that I would like to discuss: - Section numbering - Internal links With section number, I see this: 1. Chapter 1 ... 1. First Section Note that the Chapter and the first section of the Chapter have the same number. I would like the first section to be numbered 1.1, i.e. prepended by the chapter number. If you look at chapter two, the chapter and first section are not the same. This is fine, but you can see that the first section in chapter 2 has the same number as the first section in chapter. Overall, then, the section numbers in the document are not unique. If we prepended with the chapter number, they would be. On internal linking, the link in See Second Section below. doesn't work. The link in the TOC does though. Thanks Nathan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-333) The name 'aMajor_Assemblies' has no local destination
[
http://jira.codehaus.org/browse/DOXIA-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=179506#action_179506
]
Nathan Sowatskey commented on DOXIA-333:
Many thanks for looking at this. Sorry for my mistake.
The name 'aMajor_Assemblies' has no local destination
-
Key: DOXIA-333
URL: http://jira.codehaus.org/browse/DOXIA-333
Project: Maven Doxia
Issue Type: Bug
Components: Book
Affects Versions: 1.1.1
Environment: OSX 10.5.7, Maven 2.1.0, Java 5
Reporter: Nathan Sowatskey
Assignee: Lukas Theussl
Attachments: doxia-site-test.zip
See attached test case.
[INFO] Scanning for projects...
[INFO]
[INFO] Building doxia-site-test
[INFO]task-segment: [site]
[INFO]
[INFO] [doxia:render-books {execution: default}]
[WARNING] [APT Parser] Modified invalid link: '#Major_Assemblies' to
'#aMajor_Assemblies'
[WARNING] [APT Parser] Modified invalid link: '#Major_Assemblies' to
'#aMajor_Assemblies'
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] The name 'aMajor_Assemblies' has no local destination.
[INFO]
[INFO] Trace
java.lang.RuntimeException: The name 'aMajor_Assemblies' has no local
destination.
at com.lowagie.text.pdf.PdfWriter.addLocalDestinations(Unknown Source)
at com.lowagie.text.pdf.PdfDocument.close(Unknown Source)
at com.lowagie.text.Document.close(Unknown Source)
at com.lowagie.text.xml.SAXiTextHandler.handleEndingTags(Unknown Source)
at com.lowagie.text.xml.SAXiTextHandler.endElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.lowagie.text.xml.XmlParser.go(Unknown Source)
at com.lowagie.text.xml.XmlParser.parse(Unknown Source)
at com.lowagie.text.xml.XmlToXXX.parse(Unknown Source)
at
org.apache.maven.doxia.module.itext.ITextUtil.writePdf(ITextUtil.java:118)
at
org.apache.maven.doxia.book.services.renderer.PdfBookRenderer.renderXML(PdfBookRenderer.java:50)
at
org.apache.maven.doxia.book.services.renderer.AbstractITextBookRenderer.renderBook(AbstractITextBookRenderer.java:165)
at
org.apache.maven.doxia.book.DefaultBookDoxia.renderBook(DefaultBookDoxia.java:142)
at
org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:265)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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:356)
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)
[jira] Created: (DOXIA-332) Problem with Tables, Doxia, APT Maven site and PDF/RTF generation
Problem with Tables, Doxia, APT Maven site and PDF/RTF generation
-
Key: DOXIA-332
URL: http://jira.codehaus.org/browse/DOXIA-332
Project: Maven Doxia
Issue Type: Bug
Components: Book
Affects Versions: 1.1.1
Environment: OSX 10.5.7, Maven 2.1.0, Java 5
Reporter: Nathan Sowatskey
Attachments: doxia-site-test.zip
When running the attached project I get:
~/Documents/java/apache-maven-2.1.0/bin/mvn clean;
~/Documents/java/apache-maven-2.1.0/bin/mvn site
[INFO] Scanning for projects...
[INFO]
[INFO] Building doxia-site-test
[INFO]task-segment: [clean]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory .../doxia-site-test/target
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jun 05 10:54:46 CEST 2009
[INFO] Final Memory: 3M/7M
[INFO]
[INFO] Scanning for projects...
[INFO]
[INFO] Building doxia-site-test
[INFO]task-segment: [site]
[INFO]
[INFO] [doxia:render-books {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] com.lowagie.text.Table
[INFO]
[INFO] Trace
java.lang.ClassCastException: com.lowagie.text.Table
at com.lowagie.text.xml.SAXiTextHandler.handleEndingTags(Unknown Source)
at com.lowagie.text.xml.SAXiTextHandler.endElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.lowagie.text.xml.XmlParser.go(Unknown Source)
at com.lowagie.text.xml.XmlParser.parse(Unknown Source)
at com.lowagie.text.xml.XmlToXXX.parse(Unknown Source)
at
org.apache.maven.doxia.module.itext.ITextUtil.writePdf(ITextUtil.java:118)
at
org.apache.maven.doxia.book.services.renderer.PdfBookRenderer.renderXML(PdfBookRenderer.java:50)
at
org.apache.maven.doxia.book.services.renderer.AbstractITextBookRenderer.renderBook(AbstractITextBookRenderer.java:163)
at
org.apache.maven.doxia.book.DefaultBookDoxia.renderBook(DefaultBookDoxia.java:142)
at
org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:265)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
[jira] Commented: (DOXIA-332) Problem with Tables, Doxia, APT Maven site and PDF/RTF generation
[
http://jira.codehaus.org/browse/DOXIA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=179414#action_179414
]
Nathan Sowatskey commented on DOXIA-332:
Hi
Thanks for looking at this. Does this mean that the anchor markers around the
table title cannot be supported?
Or does it mean that they *should* be supported and that a fix will be
available as a consequence of planned work?
Or ...?
Sorry, I am just not sure what I should do next:
- Remove the anchors
- Await a fix
- Look for a fix that exists
Regards
Nathan
Problem with Tables, Doxia, APT Maven site and PDF/RTF generation
-
Key: DOXIA-332
URL: http://jira.codehaus.org/browse/DOXIA-332
Project: Maven Doxia
Issue Type: Bug
Components: Book, Module - FO, Module - Itext
Affects Versions: 1.1.1
Environment: OSX 10.5.7, Maven 2.1.0, Java 5
Reporter: Nathan Sowatskey
Attachments: doxia-site-test.zip
When running the attached project I get:
~/Documents/java/apache-maven-2.1.0/bin/mvn clean;
~/Documents/java/apache-maven-2.1.0/bin/mvn site
[INFO] Scanning for projects...
[INFO]
[INFO] Building doxia-site-test
[INFO]task-segment: [clean]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory .../doxia-site-test/target
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jun 05 10:54:46 CEST 2009
[INFO] Final Memory: 3M/7M
[INFO]
[INFO] Scanning for projects...
[INFO]
[INFO] Building doxia-site-test
[INFO]task-segment: [site]
[INFO]
[INFO] [doxia:render-books {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] com.lowagie.text.Table
[INFO]
[INFO] Trace
java.lang.ClassCastException: com.lowagie.text.Table
at com.lowagie.text.xml.SAXiTextHandler.handleEndingTags(Unknown Source)
at com.lowagie.text.xml.SAXiTextHandler.endElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.lowagie.text.xml.XmlParser.go(Unknown Source)
at com.lowagie.text.xml.XmlParser.parse(Unknown Source)
at com.lowagie.text.xml.XmlToXXX.parse(Unknown Source)
at
org.apache.maven.doxia.module.itext.ITextUtil.writePdf(ITextUtil.java:118)
at
org.apache.maven.doxia.book.services.renderer.PdfBookRenderer.renderXML(PdfBookRenderer.java:50)
at
org.apache.maven.doxia.book.services.renderer.AbstractITextBookRenderer.renderBook(AbstractITextBookRenderer.java:163)
at
org.apache.maven.doxia.book.DefaultBookDoxia.renderBook(DefaultBookDoxia.java:142)
at
org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:265)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
[jira] Commented: (DOXIA-332) Problem with Tables, Doxia, APT Maven site and PDF/RTF generation
[
http://jira.codehaus.org/browse/DOXIA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=179446#action_179446
]
Nathan Sowatskey commented on DOXIA-332:
Fiixed! Thanks :-)
Problem with Tables, Doxia, APT Maven site and PDF/RTF generation
-
Key: DOXIA-332
URL: http://jira.codehaus.org/browse/DOXIA-332
Project: Maven Doxia
Issue Type: Bug
Components: Book, Module - FO, Module - Itext
Affects Versions: 1.1.1
Environment: OSX 10.5.7, Maven 2.1.0, Java 5
Reporter: Nathan Sowatskey
Attachments: doxia-site-test.zip
When running the attached project I get:
~/Documents/java/apache-maven-2.1.0/bin/mvn clean;
~/Documents/java/apache-maven-2.1.0/bin/mvn site
[INFO] Scanning for projects...
[INFO]
[INFO] Building doxia-site-test
[INFO]task-segment: [clean]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory .../doxia-site-test/target
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Fri Jun 05 10:54:46 CEST 2009
[INFO] Final Memory: 3M/7M
[INFO]
[INFO] Scanning for projects...
[INFO]
[INFO] Building doxia-site-test
[INFO]task-segment: [site]
[INFO]
[INFO] [doxia:render-books {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] com.lowagie.text.Table
[INFO]
[INFO] Trace
java.lang.ClassCastException: com.lowagie.text.Table
at com.lowagie.text.xml.SAXiTextHandler.handleEndingTags(Unknown Source)
at com.lowagie.text.xml.SAXiTextHandler.endElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.lowagie.text.xml.XmlParser.go(Unknown Source)
at com.lowagie.text.xml.XmlParser.parse(Unknown Source)
at com.lowagie.text.xml.XmlToXXX.parse(Unknown Source)
at
org.apache.maven.doxia.module.itext.ITextUtil.writePdf(ITextUtil.java:118)
at
org.apache.maven.doxia.book.services.renderer.PdfBookRenderer.renderXML(PdfBookRenderer.java:50)
at
org.apache.maven.doxia.book.services.renderer.AbstractITextBookRenderer.renderBook(AbstractITextBookRenderer.java:163)
at
org.apache.maven.doxia.book.DefaultBookDoxia.renderBook(DefaultBookDoxia.java:142)
at
org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:265)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at
[jira] Created: (DOXIA-333) The name 'aMajor_Assemblies' has no local destination
The name 'aMajor_Assemblies' has no local destination
-
Key: DOXIA-333
URL: http://jira.codehaus.org/browse/DOXIA-333
Project: Maven Doxia
Issue Type: Bug
Components: Book
Affects Versions: 1.1.1
Environment: OSX 10.5.7, Maven 2.1.0, Java 5
Reporter: Nathan Sowatskey
Attachments: doxia-site-test.zip
See attached test case.
[INFO] Scanning for projects...
[INFO]
[INFO] Building doxia-site-test
[INFO]task-segment: [site]
[INFO]
[INFO] [doxia:render-books {execution: default}]
[WARNING] [APT Parser] Modified invalid link: '#Major_Assemblies' to
'#aMajor_Assemblies'
[WARNING] [APT Parser] Modified invalid link: '#Major_Assemblies' to
'#aMajor_Assemblies'
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] The name 'aMajor_Assemblies' has no local destination.
[INFO]
[INFO] Trace
java.lang.RuntimeException: The name 'aMajor_Assemblies' has no local
destination.
at com.lowagie.text.pdf.PdfWriter.addLocalDestinations(Unknown Source)
at com.lowagie.text.pdf.PdfDocument.close(Unknown Source)
at com.lowagie.text.Document.close(Unknown Source)
at com.lowagie.text.xml.SAXiTextHandler.handleEndingTags(Unknown Source)
at com.lowagie.text.xml.SAXiTextHandler.endElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at com.lowagie.text.xml.XmlParser.go(Unknown Source)
at com.lowagie.text.xml.XmlParser.parse(Unknown Source)
at com.lowagie.text.xml.XmlToXXX.parse(Unknown Source)
at
org.apache.maven.doxia.module.itext.ITextUtil.writePdf(ITextUtil.java:118)
at
org.apache.maven.doxia.book.services.renderer.PdfBookRenderer.renderXML(PdfBookRenderer.java:50)
at
org.apache.maven.doxia.book.services.renderer.AbstractITextBookRenderer.renderBook(AbstractITextBookRenderer.java:165)
at
org.apache.maven.doxia.book.DefaultBookDoxia.renderBook(DefaultBookDoxia.java:142)
at
org.apache.maven.doxia.plugin.DoxiaRenderBooksMojo.execute(DoxiaRenderBooksMojo.java:265)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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:356)
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)
[INFO]
