[ https://issues.apache.org/jira/browse/SOLR-14824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197417#comment-17197417 ]
Dawid Weiss commented on SOLR-14824: ------------------------------------ The benefit of project-resolved paths is that you are then free to shuffle projects around and things just work. As for the groovy error - the stack trace should contain script line where this occurred? The code you mention shouldn't cause this (unless project is referring to something else than the default). Ext is a property holder on objects so something is wrong. > Simplify set of Ref Guide build parameters > ------------------------------------------ > > Key: SOLR-14824 > URL: https://issues.apache.org/jira/browse/SOLR-14824 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: Build, documentation > Reporter: Cassandra Targett > Assignee: Chris M. Hostetter > Priority: Minor > Attachments: SOLR-14824.patch, SOLR-14824.patch > > > While trying to solve LUCENE-9495, I thought it might be a good idea to try > to simplify the set of variables and properties used during the Ref Guide > build. > There are 3 areas to work on: > 1. Remove the "barebones-html" build. With Gradle the build is self-contained > and {{gradlew check}} and {{gradle precommit}} could just build the full docs > and check them. > 2. Remove some properties that only existed for a hypothetical need related > to the now-removed PDF. > 3. Change remaining properties to be defined directly in build.gradle instead > of relying on ant properties functionality. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org