[ http://jira.codehaus.org/browse/MPXDOC-80?page=all ]
Lukas Theussl updated MPXDOC-80:
--------------------------------
Attachment: MPXDOC-80.patch
Hi Joerg,
I had to adapt your patch quite a bit to the current Maven trunk. Can you test
please if the attached patch still does what you want? Also, I couldn't get it
to work with the ${maven.multiproject.basedir} property as you suggested.
Instead the maven.xdoc.theme.file should be specified as relative to the
current project's ${basedir}. Let me know if you are happy (or not) and I will
commit it.
> Support global theme
> --------------------
>
> Key: MPXDOC-80
> URL: http://jira.codehaus.org/browse/MPXDOC-80
> Project: maven-xdoc-plugin
> Type: Improvement
> Reporter: Joerg Schaible
> Assignee: Lukas Theussl
> Fix For: 1.10
> Attachments: MPXDOC-80.patch, plugin.jelly.diff, properties.xml.diff,
> xdoc-theme.diff
>
> Original Estimate: 10 minutes
> Remaining: 10 minutes
>
> While it is possible to set an URL for an own theme using the new property
> maven.xdoc.theme.url, you cannot tell the xdoc plugin which local file you
> are using. The current approach enforces every project to have its own copy
> of the theme. This is extremly nasty in combination with multiproject.
> Proposal: Support a new property maven.xdoc.theme.file, that defines the
> local location of the theme file. This file is copied into the
> ${maven.docs.dest}/style directory.
> Please have a look at jakarta-commons, they suffer from this problem also:
> http://www.mail-archive.com/commons-dev%40jakarta.apache.org/index.html#35557
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
