[
https://issues.apache.org/jira/browse/OAK-7817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671246#comment-16671246
]
Marcel Reutegger commented on OAK-7817:
---------------------------------------
bq. more specifically would it still show somewhere on github
I'm also not sure how syncing to github works, but I had a setup in mind like
https://github.com/apache/jackrabbit-filevault
Maybe [~tripod] can give some pointers what steps were necessary.
bq. but then how would that be different from having it in oak tree itself
It would not be part of the Oak release anymore and have its own release cycle.
> 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)
