[
https://issues.apache.org/jira/browse/OAK-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671184#comment-16671184
]
Vikas Saurabh commented on OAK-7817:
------------------------------------
[~mreutegg], yes, that sounds like a good way moving forward. But
unfortunately, I don't really know of how to do both parts:
# move it out of oak space in oak tree - more specifically would it still show
somewhere on github (under https://github.com/apache/jackrabbit?? ... but then
how would that be different from having it in oak tree itself)
# release (well, because I haven't yet done a release or deployed a release)
I'd be happy to do it but would need some spoon feeding.
> oak-doc-railroad-macro should be built in default reactor built
> ---------------------------------------------------------------
>
> Key: OAK-7817
> URL: https://issues.apache.org/jira/browse/OAK-7817
> Project: Jackrabbit Oak
> Issue Type: Documentation
> Components: doc
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
>
> {{oak-doc}} is dependent on {{oak-doc-railroad-macro}} but the site
> generation step mentioned in {{oak-doc/README}} have {{mvn site -Pdoc}} which
> wont' build railroad macro module.
> So, on a fresh system (or cleaned .m2 folder) would fail to do {{mvn site
> -Pdoc}}.
> A simple solution (outside of mentioning this in README itself) is to build
> {{oak-doc-railroad-macro}} in default reactor build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
