[
https://issues.apache.org/jira/browse/SOLR-11541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-11541:
----------------------------
Attachment: SOLR-11541_bulk_change.patch
SOLR-11541_code_and_metadocs.patch
I'm attaching 2 patches for this change that work in compliment with
eachother...
* {{SOLR-11541_code_and_metadocs.patch}}
** updates the {{meta-docs}} to no longer refer to these attributes, and
updates {{BuildNavAndPDFBody.java}} to fail if someone adds them to a page (or
adds a new page with them) to reduce confusion down the road.
* {{SOLR-11541_bulk_change.patch}}
** the bulk change to all {{src/*.adoc}} files
** generated via:{code}
find solr/solr-ref-guide/src/ -name \*.adoc | xargs perl -i -nle 'print unless
m/^:page-(shortname|permalink):.*$/;'
{code}
If you apply the first patch to master, you should see build failures
until/unless you apply the second patch.
[~ctargett]; see any problems? (i'm mainly curious about the meta-doc changes
and if you think they still make sense)
> purge unneccessary page-shortname and page-permalink attributes from all
> source docs
> ------------------------------------------------------------------------------------
>
> Key: SOLR-11541
> URL: https://issues.apache.org/jira/browse/SOLR-11541
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Hoss Man
> Assignee: Hoss Man
> Attachments: SOLR-11541_bulk_change.patch,
> SOLR-11541_code_and_metadocs.patch
>
>
> once SOLR-11540 is done, we can remove all explicitly declared
> {{page-shortname}} and {{page-permalink}} variables from our source files and
> update BuildNavAndPDFBody to fail if someone tries to declare them
> unnecessarily/redundantly/contradictory
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
