[
https://issues.apache.org/jira/browse/SOLR-13145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746461#comment-16746461
]
Gus Heck commented on SOLR-13145:
---------------------------------
Checking for gems would be ideal, but a bigger change. The error above is an
Ant level error that happens when Jekyll is not found, and not something
crafted by me. Both of these suggestions would make good separate tickets I
think :)
> Provide better error when ref guide deps are not installed
> ----------------------------------------------------------
>
> Key: SOLR-13145
> URL: https://issues.apache.org/jira/browse/SOLR-13145
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Build
> Affects Versions: 8.0
> Reporter: Gus Heck
> Assignee: Gus Heck
> Priority: Trivial
> Attachments: SOLR-13145.patch
>
>
> Recently I tried to build the ref guide only to find I didn't have the deps
> installed on that particular machine (mostly I do solr dev on my desktop
> cause it's faster). The error I got was unenlightening:
> {code:java}
> build-site:
> [java] Exception in thread "main" java.lang.NullPointerException
> [java] at CheckLinksAndAnchors.main(CheckLinksAndAnchors.java:156)
> BUILD FAILED
> {code}
> This happens because CheckLinksAndAnchors.main() is trying to list the files
> in the directory into which Jeckyll didn't put the html.... and getting null.
> I think the problem here is that we let the build continue when Jeckyll
> failed. Attaching patch to fail out when Jeckyll is not found with this
> message:
> {code:java}
> -build-site:
> [echo] Running Jekyll...
> [exec] rbenv: jekyll: command not found
> BUILD FAILED
> /Users/gus/projects/solr/lucene-solr/solr/solr-ref-guide/build.xml:299: exec
> returned: 127
> {code}
> That at least will point the dev in the right direction, since clearly
> something required is not found.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
