[ http://jira.codehaus.org/browse/MPXDOC-131?page=all ]
Ignacio G. Mac Dowell updated MPXDOC-131:
-
Attachment: hrefkey.patch
Support for i18n links. Tests and docs included. It might be nice to have them
for the item elements in navigation.xml a
Hi Brett,
I have 10 days off now and will be leaving in an hour or so 8-)
So if there are no answers from me on this thread is not that I am not
interested or anything. I'm just relaxing a bit...
thanks again and best regards,
nacho
PD: As soon as I get back, we'll continue with the discuss
Brett Porter wrote:
Shouldn't this retain the handling for "href" too, and just choose one
of hrefkey and href?
I was thinking that if someone uses a hrefkey and there actually is a
message for it (actually the patch only checks if the bundle and the key
exist, not the the message) then he/
Some Qs:
Shouldn't this retain the handling for "href" too, and just choose one
of hrefkey and href?
Can you submit the patch as a replacement for the other patches to the
JIRA issue?
Is there anything else you need out of that issue?
- Brett
Nacho G. Mac Dowell wrote:
> Brett Porter wrote:
>
Brett Porter wrote:
how much more effort should be put into duplicating this
The hrefkey is quite easily implemented :-) The diff would be:
maven-xdoc-plugin-1.9.1\plugin-resources\site.jsl2005-08-05
10:51:41.0 +-0200
@@ -511,14 +511,35 @@
var="escapedChunk">${escapedChunk
Yes, I think the hrefkey is definitely a better idea for this specific case.
I guess the question we have to start approaching with features now is
how much more effort should be put into duplicating this across the
m1/m2 plugins before we just cut the m1 plugin over to doxia (m2).
- Brett
Nacho
Hi Brett, thanks for the interest!
Currently we are mavenizing ws-jaxme and I'd like to be able to have the
external links of the user-docs on a single properties file (or
whatever) as we do right now with forrest. It seemed like a good idea to
me if we could use velocity on the user-docs and
Ignacio, thanks for putting the effort into this, but for significant
changes it does need to be discussed with the dev team first (thanks for
approaching us now to do so).
I'm not in favour of this change as it is against the direction we are
taking things. To introduce Jelly processing into the
[ http://jira.codehaus.org/browse/MPXDOC-131?page=comments#action_43927 ]
Brett Porter commented on MPXDOC-131:
-
Ignacio, thanks for putting the effort into this, but for significant changes
it does need to be discussed with the dev team first (thanks fo
Hi all!
I wanted to know if there is still any interest in implementing this. At
first I thought there was, but it makes quite a while since the src,
tests and docs where submitted. This feature would be nice to avoid hard
links. Another possible approach for solving this would be having a key
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Feb 2005 7:33 AM
Comment:
Cumulative patch with tests, src and docs
Changes:
Attachment changed to last.cumulative.patch
---
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Feb 2005 7:32 AM
Comment:
Docs patch for MPXDOC-131
Changes:
Attachment changed to last.docs.patch
-
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Feb 2005 7:32 AM
Comment:
Src for MPXDOC-131
Changes:
Attachment changed to last.main.patch
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Feb 2005 7:31 AM
Comment:
Tests for MPXDOC-131
Changes:
Attachment changed to last.test.patch
--
The following comment has been added to this issue:
Author: Ignacio G. Mac Dowell
Created: Tue, 15 Feb 2005 7:30 AM
Body:
The patch submitted fails when there is a directory with xdocs under the xdocs
directory. The problem is that velocity:merge doesn't seem to like generating a
Hi,
There is an error in the patch I submitted (velocity:merge seems to
dislike when the parent directory of the target file doesn't exist),
I'll fix it asap. I was thinking if you could give me some guidelines on
how to write a plugin-test (or where to find them - is there a thread
for this?)
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Mon, 14 Feb 2005 5:28 PM
Body:
It seems interesting Ignacio.
Can you add a plugin-test and a patch for the documentation please ?
---
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Fri, 11 Feb 2005 5:13 AM
Comment:
Default user-doc-templates to false
Changes:
Attachment changed to plugin.properties.patch
---
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Fri, 11 Feb 2005 5:12 AM
Comment:
Maybe it would be nice to be able to use .jelly also as user-docs. If anybody
is interested I'll supply the patch.
Changes:
Attac
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-131
Here is an overview of the issue:
-
Key:
20 matches
Mail list logo
