stevedlawrence commented on PR #381:
URL: https://github.com/apache/daffodil-vscode/pull/381#issuecomment-1359875484
> So what should be done is I add pandoc to the release-canidate container,
then update the process to create the Makefile, clone the repo and make the
docs?
Yep. You might not even need the Makefile? Just need to update the
release-candidate script to run the couple of commands that are needed. It's
just a git clone and pandoc, right?
> After making the docs how would I upload them to the daffodil-site or
would I upload somewhere similar to where the bin and source are stored?
The release candidate script already clones and updates the site repo with
java/scala docs, so it should be similar. For example, it currenly does this:
```
echo "Installing Site Docs..."
rm -rf $DAFFODIL_DOCS_DIR
mkdir -p $DAFFODIL_DOCS_DIR/{javadoc,scaladoc}/
cp -R target/javaunidoc/* $DAFFODIL_DOCS_DIR/javadoc/
cp -R target/scala-2.12/unidoc/* $DAFFODIL_DOCS_DIR/scaladoc/
```
Note ha DAFFODIL_DOCS_DIR is just subdirecory in DAFFODIL_SITE_DIR specific
to java/scaladocs.
So in the "daffodil-vscode" section of the container scrip, you can clone
the vscode wiki, run pandoc, and copy the resulting file somewhere to
$DAFFODIL_SITE_DIR.
Whatever changes you make to the site repo are automatically committed and
pushed when "complete-release" is run, so it's just a matter of building and
installing the resulting pdf's to the right directory in the site repo and
everything else should just work.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
