[jira] Commented: (DOXIA-53) Pdf and Rtf support with the iText framework
[ http://jira.codehaus.org/browse/DOXIA-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189016#action_189016 ] Bruno Lowagie commented on DOXIA-53: I'm writing my second book about iText, and I still have my dayjob (to pay the bills), so currently I don't have much time. I guess that your question is about the XmlWriter and different Xml2Pdf classes. They used to work in the past, but as described in my first book: there are better ways to do it. As I suggested a year ago (I'm surprised I had the time to answer back then, because that was when my son had Cancer and a week before I got ill myself), you could 'resurrect' the XML package, but when I look at your patch, it contains several RTF files that seem irrelevant. That confuses me. The RTF package is still present in iText, why the need for those files in your patch? Also I have never heard of the ITextSinkTestCase. Please prepare a small jar with ONLY the XML package and a small standalone example that reproduces the problem. Then send a mail to the iText mailing list itext-questi...@lists.sourceforge.net and explain the problem there. > Pdf and Rtf support with the iText framework > > > Key: DOXIA-53 > URL: http://jira.codehaus.org/browse/DOXIA-53 > Project: Maven Doxia > Issue Type: New Feature >Reporter: Vincent Siveton >Assignee: Vincent Siveton > Fix For: 1.0-alpha-9 > > Attachments: doxia_itext.zip, generated-doc.zip, > itext-xmloutput2.patch, itext_plugin.zip, maven-doxia-itext2.patch > > > Propose a Pdf/Rtf support with the iText framework for Doxia. > Here is the architecture: > - added an itext module in doxia-modules > - created a doxia-doc-renderer (similar to doxia-site-renderer) > - created an iText plugin for maven > The iText module generates iText XML files. So, documents should be generated > in Pdf or Rtf format (supported by iText). > You could see the howto in the plugin for more information or try the project > tests. > According MPIR-17, we could be more generic by defining a new generated XML > Doxia (I mean another DoxiaSink) and apply XSLT to generate other formats > (like javahelp) > Known limitations: > - known limitations from the iText framework like roman list > - i18n for the "table of contents" title > - reports are not supported > - Renderer for Fml and Xdoc format should be improved. Parsers suppose that > the renderer is HTML. > Attachments are: > - doxia zip with diff (containing doxia-doc-renderer and doxia-module-itext) > and resources > - itext plugin zip with diff and resources > - a zip containing generated documents for the site project (real examples) -- 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: (DOXIASITETOOLS-32) Deployed decoration-1.0.1.xsd
Deployed decoration-1.0.1.xsd - Key: DOXIASITETOOLS-32 URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-32 Project: Maven Doxia Sitetools Issue Type: Task Components: Decoration model Affects Versions: 1.1.2 Reporter: Vincent Siveton Due to DOXIASITETOOLS-31, we need to deployed a new version of decoration-1.0.1.xsd -- 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: (DOXIASITETOOLS-32) Deployed decoration-1.0.1.xsd
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated DOXIASITETOOLS-32: -- Fix Version/s: 1.1.2 > Deployed decoration-1.0.1.xsd > - > > Key: DOXIASITETOOLS-32 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-32 > Project: Maven Doxia Sitetools > Issue Type: Task > Components: Decoration model >Affects Versions: 1.1.2 >Reporter: Vincent Siveton > Fix For: 1.1.2 > > > Due to DOXIASITETOOLS-31, we need to deployed a new version of > decoration-1.0.1.xsd -- 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: (DOXIASITETOOLS-31) Allow images in the menu items of the site.xml
[
http://jira.codehaus.org/browse/DOXIASITETOOLS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed DOXIASITETOOLS-31.
-
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 1.1.2
Fixed in [r809116|http://svn.apache.org/viewvc?rev=809116&view=rev], snap
deployed
> Allow images in the menu items of the site.xml
> --
>
> Key: DOXIASITETOOLS-31
> URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-31
> Project: Maven Doxia Sitetools
> Issue Type: New Feature
>Affects Versions: 1.1
>Reporter: Vincent Siveton
>Assignee: Vincent Siveton
> Fix For: 1.1.2
>
>
> {noformat}
> width="" height=""/>
> {noformat}
--
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: (DOXIASITETOOLS-7) site.xml attribute no more working
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed DOXIASITETOOLS-7. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 1.1.2 fixed in [r809126|http://svn.apache.org/viewvc?rev=809126&view=rev], snap deployed > site.xml attribute no more working > - > > Key: DOXIASITETOOLS-7 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-7 > Project: Maven Doxia Sitetools > Issue Type: New Feature > Components: Decoration model >Affects Versions: 1.0-alpha-9 > Environment: JDK 1.6, Maven 2.0.8 >Reporter: Bruno Marti >Assignee: Vincent Siveton > Fix For: 1.1.2 > > > In maven 1.x xdoc site documentation there could be defined the following for > menus (navigation.xml): > > http://maven.apache.org/maven-1.x/"; > target="_new" /> > ... > (creates a link to maven 1.x in a new window or tab) > In maven 2.x site.xml this doesn't work anymore. > The target attribute is ignored. -- 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: (MNG-4330) to be able to run a plugin in a given phase when the build will include a given phase
to be able to run a plugin in a given phase when the build will include a given phase - Key: MNG-4330 URL: http://jira.codehaus.org/browse/MNG-4330 Project: Maven 2 Issue Type: New Feature Affects Versions: 2.0.10 Reporter: Claus Brøndby Reimer Hi Maven Team Recently I developed a plugin checking whether the local project files were upto date with the files in the repository. My plan was to add this plugin to the build cycle and do this check automatically whenever deploy were executed - but this seems to be impossible at moment. What i would like, is something like this. dk.fujitsu.mavenplugins svn 1.0-SNAPSHOT validate deploy uptodate-check if the build will execute deploy (buildPhase) then it should execute uptodate-check in the validate phase Best regards Claus Reimer -- 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: (MCOMPILER-71) javac compilation error for package-info.java containing package annotation
[ http://jira.codehaus.org/browse/MCOMPILER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189043#action_189043 ] Stephen Connolly commented on MCOMPILER-71: --- line 622 of the above diff is one of the offending lines > javac compilation error for package-info.java containing package annotation > --- > > Key: MCOMPILER-71 > URL: http://jira.codehaus.org/browse/MCOMPILER-71 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Windows XP SP2 > JDK 1.5.0_15 >Reporter: Gabriel Forro > Attachments: compile_error_2.0.2.log > > > The package-info.java files can not be compiled in Maven 2 if the 2.0.2 > maven-compiler-plugin is used. package-info.java files can be compiled by > earlier versions of the maven-compiler-plugin (I have tried 2.0 and 2.0.1). > Newer snapshot versions does not work also and it fails in the same error (I > have tried version 2.1-snapshot). > This problem can be caused by an unusual behavior of the javac from jdk 1.5. > This behavior is as follows: > You can not use '/' file separator during compiling package-info.java (for > instance "javac sk/forro/package-info.java"). You must use '\' separator (for > instance "javac sk\forro\package-info.java"). If you use the '/' separator > you get the the compilation error reported by this bug (package annotations > should be in file package-info.java). This is javac 'feature' has been > removed in jdk 6 and in jdk 6 you can use either '/' or '\' - it does not > matter. > It looks like the maven-compiler-plugin or one of its components (I mean > plexus-x artefacts used by maven-compiler-plugin) uses '/' instead of the '\' > in the MS Windows environment. > I have attached a log file of an unsuccessful build (generated by mvn install > -X) > A possible workaround to solve this problem temporarily: > The compilation successes if I use either an older version of > maven-compiler-plugin or jdk 6 or do not use package-info.java files at all. -- 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: (MCOMPILER-71) javac compilation error for package-info.java containing package annotation
[ http://jira.codehaus.org/browse/MCOMPILER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189042#action_189042 ] Stephen Connolly commented on MCOMPILER-71: --- At least when fork is true, this issue was introduced in r5396 of plexus http://fisheye.codehaus.org/browse/plexus/plexus-components/trunk/plexus-compiler/plexus-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compiler/javac/JavacCompiler.java?r1=5395&r2=5396 > javac compilation error for package-info.java containing package annotation > --- > > Key: MCOMPILER-71 > URL: http://jira.codehaus.org/browse/MCOMPILER-71 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.0.2 > Environment: Windows XP SP2 > JDK 1.5.0_15 >Reporter: Gabriel Forro > Attachments: compile_error_2.0.2.log > > > The package-info.java files can not be compiled in Maven 2 if the 2.0.2 > maven-compiler-plugin is used. package-info.java files can be compiled by > earlier versions of the maven-compiler-plugin (I have tried 2.0 and 2.0.1). > Newer snapshot versions does not work also and it fails in the same error (I > have tried version 2.1-snapshot). > This problem can be caused by an unusual behavior of the javac from jdk 1.5. > This behavior is as follows: > You can not use '/' file separator during compiling package-info.java (for > instance "javac sk/forro/package-info.java"). You must use '\' separator (for > instance "javac sk\forro\package-info.java"). If you use the '/' separator > you get the the compilation error reported by this bug (package annotations > should be in file package-info.java). This is javac 'feature' has been > removed in jdk 6 and in jdk 6 you can use either '/' or '\' - it does not > matter. > It looks like the maven-compiler-plugin or one of its components (I mean > plexus-x artefacts used by maven-compiler-plugin) uses '/' instead of the '\' > in the MS Windows environment. > I have attached a log file of an unsuccessful build (generated by mvn install > -X) > A possible workaround to solve this problem temporarily: > The compilation successes if I use either an older version of > maven-compiler-plugin or jdk 6 or do not use package-info.java files at all. -- 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: (MNG-4330) to be able to run a plugin in a given phase when the build will include a given phase
[ http://jira.codehaus.org/browse/MNG-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189054#action_189054 ] Dan Tran commented on MNG-4330: --- I think the title should be "Need pre-deploy phase" > to be able to run a plugin in a given phase when the build will include a > given phase > - > > Key: MNG-4330 > URL: http://jira.codehaus.org/browse/MNG-4330 > Project: Maven 2 > Issue Type: New Feature >Affects Versions: 2.0.10 >Reporter: Claus Brøndby Reimer > > Hi Maven Team > Recently I developed a plugin checking whether the local project files were > upto date with the files in the repository. > > My plan was to add this plugin to the build cycle and do this check > automatically whenever deploy were executed - but this seems to be impossible > at moment. > What i would like, is something like this. > > dk.fujitsu.mavenplugins > svn > 1.0-SNAPSHOT > > > validate > deploy > > uptodate-check > > > > > if the build will execute deploy (buildPhase) then it should execute > uptodate-check in the validate phase > Best regards > Claus Reimer -- 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: (MNG-3708) Windows Installer
[ http://jira.codehaus.org/browse/MNG-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189055#action_189055 ] Robert Scholte commented on MNG-3708: - It should be possible, see http://nsis.sourceforge.net/Docs/AppendixG.html#G > Windows Installer > - > > Key: MNG-3708 > URL: http://jira.codehaus.org/browse/MNG-3708 > Project: Maven 2 > Issue Type: Wish > Components: General > Environment: Windows >Reporter: Frank Cornelis > Fix For: 2.x > > > A simple NSIS-based installer for Windows would be nice. > Procedure: > - copy to C:\Program Files\Maven2 > - add PATH env variable that points to Maven2\bin -- 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: (MJAVADOC-257) maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
[
http://jira.codehaus.org/browse/MJAVADOC-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189065#action_189065
]
Vincent Siveton commented on MJAVADOC-257:
--
Could you please provide a test case? It seems that you have 2 identical
goals...
Also, please provide debug files
http://maven.apache.org/plugins/maven-javadoc-plugin/faq.html#How_to_know_exactly_the_Javadoc_command_line
> maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
> --
>
> Key: MJAVADOC-257
> URL: http://jira.codehaus.org/browse/MJAVADOC-257
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Apache Maven 2.2.0
> Java version: 1.6.0_11
>Reporter: jcrouvi
>
> Using maven-javadoc-plugin Version 2.5 or 2.6 for a project of type
> *maven-plugin* leads to the following error message,
> even if the aggregation is not set:
> {{Error extracting plugin descriptor: 'Goal: ... already exists in the plugin
> descriptor ...}}
> *Using maven-javadoc-plugin Version 2.2 solves this problem.*
> Structure of the project:
> {code:none}
> [INFO] Reactor build order:
> [INFO] Service
> [INFO] Service: Common Dependencies
> [INFO] Service: API
> [INFO] Service: Test Fixture
> [INFO] Service: Implementation
> [INFO] Service: DI
> [INFO] Service: auth-maven-plugin
> [INFO] Service: Config
> [INFO] Service: Interceptors
> [INFO] Service: Client Module
> [INFO] Service: Web Components
> [INFO] Service: Example
> {code}
> Configuration in {{service/pom.xml}}
> {code:xml}
>
> full-site
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
>
> analyze-report
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.5
>
> true
> protected
>
> http://java.sun.com/javase/6/docs/api/
> http://java.sun.com/javaee/5/docs/api/
>
>
>
> ...
> {code}
> Also see: [http://jira.codehaus.org/browse/MJAVADOC-224]
--
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: (MJAVADOC-257) maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
[
http://jira.codehaus.org/browse/MJAVADOC-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189066#action_189066
]
Vincent Siveton commented on MJAVADOC-257:
--
Also, I tried with Doxia and Surefire and your profile seems to work.
> maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor
> --
>
> Key: MJAVADOC-257
> URL: http://jira.codehaus.org/browse/MJAVADOC-257
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.5, 2.6
> Environment: Apache Maven 2.2.0
> Java version: 1.6.0_11
>Reporter: jcrouvi
>
> Using maven-javadoc-plugin Version 2.5 or 2.6 for a project of type
> *maven-plugin* leads to the following error message,
> even if the aggregation is not set:
> {{Error extracting plugin descriptor: 'Goal: ... already exists in the plugin
> descriptor ...}}
> *Using maven-javadoc-plugin Version 2.2 solves this problem.*
> Structure of the project:
> {code:none}
> [INFO] Reactor build order:
> [INFO] Service
> [INFO] Service: Common Dependencies
> [INFO] Service: API
> [INFO] Service: Test Fixture
> [INFO] Service: Implementation
> [INFO] Service: DI
> [INFO] Service: auth-maven-plugin
> [INFO] Service: Config
> [INFO] Service: Interceptors
> [INFO] Service: Client Module
> [INFO] Service: Web Components
> [INFO] Service: Example
> {code}
> Configuration in {{service/pom.xml}}
> {code:xml}
>
> full-site
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
>
> analyze-report
>
>
>
>
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.5
>
> true
> protected
>
> http://java.sun.com/javase/6/docs/api/
> http://java.sun.com/javaee/5/docs/api/
>
>
>
> ...
> {code}
> Also see: [http://jira.codehaus.org/browse/MJAVADOC-224]
--
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: (MNG-4330) to be able to run a plugin in a given phase when the build will include a given phase
[ http://jira.codehaus.org/browse/MNG-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189067#action_189067 ] Olivier Lamy commented on MNG-4330: --- so as we have prepare-package we could have prepare-deploy phase. > to be able to run a plugin in a given phase when the build will include a > given phase > - > > Key: MNG-4330 > URL: http://jira.codehaus.org/browse/MNG-4330 > Project: Maven 2 > Issue Type: New Feature >Affects Versions: 2.0.10 >Reporter: Claus Brøndby Reimer > > Hi Maven Team > Recently I developed a plugin checking whether the local project files were > upto date with the files in the repository. > > My plan was to add this plugin to the build cycle and do this check > automatically whenever deploy were executed - but this seems to be impossible > at moment. > What i would like, is something like this. > > dk.fujitsu.mavenplugins > svn > 1.0-SNAPSHOT > > > validate > deploy > > uptodate-check > > > > > if the build will execute deploy (buildPhase) then it should execute > uptodate-check in the validate phase > Best regards > Claus Reimer -- 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: (MJAVADOC-258) Grouping example could show multiple packages per group
Grouping example could show multiple packages per group --- Key: MJAVADOC-258 URL: http://jira.codehaus.org/browse/MJAVADOC-258 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.6 Reporter: Paul Benedict Priority: Trivial One thing that I learned the hard way was grouping multiple packages together. The example (http://maven.apache.org/plugins/maven-javadoc-plugin/examples/group-configuration.html) only shows one package per group, but this could be enhanced. Could you please show the asterisk notation (subpackages) and the separator (colon or semicolon)? By the way, I erroneously tried to use multiple -- which seemed a natural expectation -- but it didn't work and was silently ignored. A note to this effect may be useful. -- 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
