[jira] (DOXIA-387) Add RandomAccessSink
[
https://jira.codehaus.org/browse/DOXIA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed DOXIA-387.
Resolution: Fixed
Fix Version/s: 1.3
Fixed in [rev. 1228615|http://svn.apache.org/viewvc?rev=1228615&view=rev]
> Add RandomAccessSink
>
>
> Key: DOXIA-387
> URL: https://jira.codehaus.org/browse/DOXIA-387
> Project: Maven Doxia
> Issue Type: New Feature
> Components: Sink API
>Affects Versions: 1.1.2
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Minor
> Fix For: 1.3
>
> Attachments: DOXIA-387.patch, DOXIA-387.patch, randomaccesssink.patch
>
>
> In some cases components have to write to different parts of a page. With the
> current implementation you can only keep appending the page.
> I've attached a new class, with which it should be possible to add subsinks
> to which you can write at any time.
> Code might look like this
> {code}
> baseSink.text("Hello World");
> Sink top = baseSink.addSink();
> baseSink.horizontalRule();
> Sink content = baseSink.addSink();
> baseSink.text("So long, farewell");
> {code}
> After flushing the basesink, subsinks will flush to the basesink.
> Closing the basesink will close al subsinks as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-387) Add RandomAccessSink
[
https://jira.codehaus.org/browse/DOXIA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated DOXIA-387:
-
Component/s: (was: Sink API)
Core
> Add RandomAccessSink
>
>
> Key: DOXIA-387
> URL: https://jira.codehaus.org/browse/DOXIA-387
> Project: Maven Doxia
> Issue Type: New Feature
> Components: Core
>Affects Versions: 1.1.2
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Minor
> Fix For: 1.3
>
> Attachments: DOXIA-387.patch, DOXIA-387.patch, randomaccesssink.patch
>
>
> In some cases components have to write to different parts of a page. With the
> current implementation you can only keep appending the page.
> I've attached a new class, with which it should be possible to add subsinks
> to which you can write at any time.
> Code might look like this
> {code}
> baseSink.text("Hello World");
> Sink top = baseSink.addSink();
> baseSink.horizontalRule();
> Sink content = baseSink.addSink();
> baseSink.text("So long, farewell");
> {code}
> After flushing the basesink, subsinks will flush to the basesink.
> Closing the basesink will close al subsinks as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-293) APT format needs some "macros" for common constructs such as links to JavaDoc
[
https://jira.codehaus.org/browse/DOXIA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287702#comment-287702
]
Robert Scholte commented on DOXIA-293:
--
The main problem is that Doxia can't determine the position of these files.
I've seen {{apidocs/}},. {{api/}}, {{javadocs/}}.
Only the maven-site-plugin can pass this information to Doxia.
So this has to be fixed in both projects.
> APT format needs some "macros" for common constructs such as links to JavaDoc
> -
>
> Key: DOXIA-293
> URL: https://jira.codehaus.org/browse/DOXIA-293
> Project: Maven Doxia
> Issue Type: New Feature
>Reporter: Howard M. Lewis Ship
>Priority: Minor
>
> Some form of macro processing for APT format files would be nice.
> I often find myself writing very verbose links form APT to documentation, i.e.
> {{{apidocs/org/package/MyClass.html}MyClass}}
> (Not that I ever get to use something that terse, more like
> org.apache.tapestry.internal.ioc.RegistryImpl, etc.).
> I would love some alternate link forms, maybe something like:
> {{{api:MyClass}}}
> or
> {{{api:org.package.MyClass}}}
> and let Maven build the links for me.
> I also do some copious cross-linking of my documentation, so something akin
> to the Forrest site: prefix would be great (a way to reference another
> document by a logical id rather than a relative path).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-236) Create a new report to show how to include the module in different build systems
[ https://jira.codehaus.org/browse/MPIR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi closed MPIR-236. --- Resolution: Fixed Assignee: Simone Tripodi fixed on trunk > Create a new report to show how to include the module in different build > systems > > > Key: MPIR-236 > URL: https://jira.codehaus.org/browse/MPIR-236 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement > Components: dependency-info >Affects Versions: 2.4.1 >Reporter: Simone Tripodi >Assignee: Simone Tripodi > > Different Maven Repositories usually show an info section to show how to > include the found artifact in different build systems (Maven, Ivy, ...), it > would be nice having it directly in the documentation site as well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
