[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063928#comment-16063928
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/530
@ottobackwards , in general (a) make it work in github, and (b) make sure
the human-readable link reference text is the same as the human-readable anchor
text. That way the site-book generator will be able to derive the site-book
link text.
The trick is the generated tag text. As noted in the fix-md-dialect.py
script:
```
The problem with generated tags is that Github-MD forces header text to
lower-case, and
replaces blank spaces with hyphens, while doxia-markdown leaves case
unchanged, and replaces
blanks with underscores. Fortunately we seem to have a culture of using
link references that
are typographically the same as the header text, so we have some basis for
fixing most links.
```
So for example, if you want to link to an h2 header "This Is Great" in file
Mega.md, your Github-MD link tag will be "\<relative
path\>/Mega.md#this-is-great", BUT the human-readable link text must also be
"This Is Great", so that during site built we can magically generate the Doxia
html link tag of "\<relative path\>/Mega.html#This_Is_Great".
This is only for auto-generated tags for headers and such. If you are
using hand-crafted html markup, with explicitly named tags, then you don't need
to worry. Use whatever link reference and anchor text you want, and the tag
you defined. If the link reference text doesn't look like the tag, then it
won't try to auto-convert. That would be the conditional at
https://github.com/apache/metron/blob/master/site-book/bin/fix-md-dialect.py#L246-L247
> Create a plugin system for Metron based on 'NAR'
> ------------------------------------------------
>
> Key: METRON-777
> URL: https://issues.apache.org/jira/browse/METRON-777
> Project: Metron
> Issue Type: New Feature
> Reporter: Otto Fowler
> Assignee: Otto Fowler
>
> The success of the Metron project will be greatly dependent on community
> participation, and with that the ability to adapt and extend Metron without
> having to maintain a fork of the project.
> As organizations and individuals look to extend the Metron system with custom
> parsers, enrichments, and stellar functions that may be proprietary in
> nature, the ability to develop and deploy these extensions outside the Metron
> code base is critically important.
> To that end, and after community discussion and proposal we create or
> formalize the 'plugin' development story in Metron.
> The proposal is to adapt the Apache Nifi NAR system for use in Metron. This
> will provide the system with:
> * archetype(s) for developer projects and independent development
> * defined packaging and metadata for 'plugin' products
> * loading and instantiation with classloader isolation capabilities
> * removing the necessity for shading plugin jars
> These capabilities will also enable other features, such as plugin lifecycle,
> plugin configuration+redeployment, and other things.
> The plugin archetypes and their installation will be a followon
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
