[
https://issues.apache.org/jira/browse/TINKERPOP-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313822#comment-17313822
]
Øyvind Sæbø commented on TINKERPOP-2544:
----------------------------------------
Seeing as target/site/home/index.html corresponds to
[https://tinkerpop.apache.org|https://tinkerpop.apache.org/] an
target/site/home/gremlin.html corresponds to
[https://tinkerpop.apache.org/gremlin,] I assume if we want gremlint available
on
[https://tinkerpop.apache.org/gremlint|https://tinkerpop.apache.org/gremlin,]
the build gremlint code be copied to target/site/home/gremlint rather than
target/site/gremlint?
Modifying bin/generate-home.sh to run the build script and copy the built code
turned out to be trivial, by the way:)
> Modify site publishing scripts to include gremlint
> --------------------------------------------------
>
> Key: TINKERPOP-2544
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2544
> Project: TinkerPop
> Issue Type: Improvement
> Components: gremlint
> Affects Versions: 3.5.0
> Reporter: Stephen Mallette
> Assignee: Øyvind Sæbø
> Priority: Blocker
>
> I think `bin/generate-home.sh` just needs to run the `npm` command to
> generate the static site and copy it to `target/site/gremlint` and then
> hopefully, `bin/publish-home.sh` will automatically note the new `gremlint`
> directory and upload it svn to publish. If it doesn't, there's probably some
> minor changes to `bin/publish-home.sh` to accomplish that step.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
