Re: New PDF plugin SNAPSHOT
I found the solution by accident: you just have to remove the
'dir=${internal_pdf_workingDir}' option when you call fop in plugin.jelly.
Apparently a problem of relative url resolution (it only failed for svgs
containing relative url links within the same document, ie starting with
#, and only if they are not in the same directory as project.fo).
Cheers,
Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: New PDF plugin SNAPSHOT
I found the solution by accident: you just have to remove the
'dir=${internal_pdf_workingDir}' option when you call fop
in plugin.jelly.
Apparently a problem of relative url resolution (it only
failed for svgs containing relative url links within the same
document, ie starting with #, and only if they are not in the
same directory as project.fo).
Cheers,
Lukas
Nothing more to say !
You're my god ;-)
Thanks a lot
Arnaud
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
From: Arnaud HERITIER [EMAIL PROTECTED] I published a new snapshot which fixe incompatibilities with maven 1.0 and some jdk. ... Let us know what you think about it. I'm still getting: [java] [ERROR] file:/e:/svn/struts/current/site/target/pdf/project.fo:198:168 The id # already exists in this document I thought it had to do with the suggestion to create a separate navigation file, which I did, but it turned out to be two section tags with no 'name' attribute on the index page. Those get id=# in the .fo file, and if you have more than one, the pdf won't build. And... apparently you can't have two section tags with the same 'name' attribute, _anywhere_ in the xml you plan to convert to PDF. I added names to all the section tags, and now I'm seeing... [java] [ERROR] file:/e:/svn/struts/current/site/target/pdf/project.fo:480:175 The id #Next already exists in this document ...which is coming from the section name=Next tags at the bottom of each of the pages at the top level of the website. This is a showstopper for the Struts site-- we have multiple pages with the same section names. (And I assume it also applies to subsection.) Please let me know if you need more information, or if you want me to open a ticket for this. -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: New PDF plugin SNAPSHOT
Hi Lukas, It's weird because I downloaded the fop 0.25 distrib used in this plugin and I successfully created the pdf from our project.fo generated in our test n°2 :-( Arnaud This new snapshot has a new bug I didn't fixed actually : SVG support is broken (again :-( ) As far as I can tell, SVG is working fine really, - just not with the .svg samples I included for the test cases :-P . For them, batik fails due to a bug that has apparently only been fixed in a later version than the one included in fop. I will open another JIRA issue with more detailed explanation. Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: New PDF plugin SNAPSHOT
Hi Wendy, Thanks for your tests. You can report your problems on this issue : http://jira.codehaus.org/browse/MPPDF-40 We'll try to fix it before the next release. Arnaud -Message d'origine- De : Wendy Smoak [mailto:[EMAIL PROTECTED] Envoyé : dimanche 21 août 2005 08:20 À : Maven Users List Objet : Re: New PDF plugin SNAPSHOT From: Arnaud HERITIER [EMAIL PROTECTED] I published a new snapshot which fixe incompatibilities with maven 1.0 and some jdk. ... Let us know what you think about it. I'm still getting: [java] [ERROR] file:/e:/svn/struts/current/site/target/pdf/project.fo:198:168 The id # already exists in this document I thought it had to do with the suggestion to create a separate navigation file, which I did, but it turned out to be two section tags with no 'name' attribute on the index page. Those get id=# in the .fo file, and if you have more than one, the pdf won't build. And... apparently you can't have two section tags with the same 'name' attribute, _anywhere_ in the xml you plan to convert to PDF. I added names to all the section tags, and now I'm seeing... [java] [ERROR] file:/e:/svn/struts/current/site/target/pdf/project.fo:480:175 The id #Next already exists in this document ...which is coming from the section name=Next tags at the bottom of each of the pages at the top level of the website. This is a showstopper for the Struts site-- we have multiple pages with the same section names. (And I assume it also applies to subsection.) Please let me know if you need more information, or if you want me to open a ticket for this. -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
It's weird because I downloaded the fop 0.25 distrib used in this plugin and I successfully created the pdf from our project.fo generated in our test n°2 :-( You're right, this is very puzzling - I did the same with only the jars in my local repository in the classpath and it worked too! I have no clue for the moment, but I don't think it's anything directly fop- or batik related. Should we open a new JIRA issue for that or are you going to re-open MPPDF-32 where we can discuss that? Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
This new snapshot has a new bug I didn't fixed actually : SVG support is broken (again :-( ) As far as I can tell, SVG is working fine really, - just not with the .svg samples I included for the test cases :-P . For them, batik fails due to a bug that has apparently only been fixed in a later version than the one included in fop. I will open another JIRA issue with more detailed explanation. Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
Hi guys, I published a new snapshot which fixe incompatibilities with maven 1.0 and some jdk. I tested it on windows XP with : Maven 1.0.2 + JDK 1.3 Maven 1.0.2 + JDK 1.4 Maven 1.0.2 + JDK 1.5 Maven 1.1 + JDK 1.4 Maven 1.1 + JDK 1.5 This new snapshot has a new bug I didn't fixed actually : SVG support is broken (again :-( ) You can download it with this command : maven plugin:download -Dmaven.repo.remote=http://cvs.apache.org/repository/-DgroupId=maven -DartifactId=maven-pdf-plugin -Dversion= 2.3.1-SNAPSHOT Let us know what you think about it. Thx Arnaud On 8/15/05, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi Maven users, I applied a lot of patchs on the PDF plugin. Thanks a lot to all contributors and particularly to Lukas Theussl. I published the snapshot and the documentation. To automatically install the plugin, type the following on a single line: maven plugin:download - Dmaven.repo.remote=http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-pdf-plugin -Dversion=SNAPSHOT The documentation is available here : http://people.apache.org/~brett/maven-stage-site/reference/plugins/pdf/ Here is the list of changes since the last release : New Features: o Allow the pdf plugin to be added as a project's report. Issue: MPPDF-9. Thanks to Fabrizio Giustina. Fixed bugs: o sub-/superscripts do not work. Issue: MPPDF-43. Thanks to Lukas Theussl. o Error when logo locations are not set. Issue: MPPDF-42. Thanks to Lukas Theussl. o Suppress verbose output by default. Issue: MPPDF-41. Thanks to Lukas Theussl. o Missing patch for MPPDF-24 ( it defines a missing attribute for amp;lt;code style=indentamp;gt; tags and cleans up some layout issues with definition lists). Issue: MPPDF-39. Thanks to Lukas Theussl. o Standardize copyright notices. Issue: MPPDF-35. Thanks to Lukas Theussl. o Fix some contents overflows area errors. Issue: MPPDF-33. Thanks to Valerie Nyre. o Cannot use SVG images. batik: java.lang.NoSuchMethodError. Issue: MPPDF-32. Thanks to Lukas Theussl. o Can't insert the logo image described in the POM if its path begins with a slash (as it works for the xdoc plugin). Issue: MPPDF-31. Thanks to Lukas Theussl. o Allow copy and paste from pdf to text editor. Issue: MPPDF-22. Thanks to Lukas Theussl. o Add support for external imaging libraries like jimi and jai to use PNG images in generated pdf files. Issue: MPPDF-8. Thanks to Fabio Franco Uechi. Give us your opinion and we'll release it as soon as possible. Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
From: Lukas Theussl [EMAIL PROTECTED] Arnaud should have specified further that this plugin is for maven 1.1 only (I don't think the restriction to java 5 is correct). Maven 1.0.2 users will have to put a xalan jar into $MAVEN_HOME/lib/endorsed. Thanks, that was it. Now I'm down to a duplicate id problem, which I see is a known issue. That will take a little longer to clean up. :) -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
Thanks, that was it. Now I'm down to a duplicate id problem, which I see is a known issue. That will take a little longer to clean up. :) Yes, we are working on that right now (MPPDF-40). Currently you have to avoid identical name and id tags within one source document (which you should do anyway if you want the xdoc output to be valid HTML). Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
From: Arnaud HERITIER [EMAIL PROTECTED] http://people.apache.org/~brett/maven-stage-site/reference/plugins/pdf/ Give us your opinion and we'll release it as soon as possible. With Maven 1.0.2, JDK 1.4.2, I'm getting: BUILD FAILED File.. C:\Documents and Settings\wendy\.maven\cache\maven-pdf-plugin-SNAPSHOT\plugin.jelly Element... xslt Line.. 122 Column 177 Provider for javax.xml.transform.TransformerFactory cannot be found The whole thing is here: http://wiki.wsmoak.net/cgi-bin/wiki.pl?MavenPdfPlugin Could it have something to do with the xdoc plugin version? I constantly get the message WARNING: Plugin 'maven-xdoc-plugin' is already loaded from maven-xdoc-plugin-1.9.1; attempting to load maven-xdoc-plugin-1.8 Thanks, Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
Arnaud should have specified further that this plugin is for maven 1.1 only (I don't think the restriction to java 5 is correct). Maven 1.0.2 users will have to put a xalan jar into $MAVEN_HOME/lib/endorsed. Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
