ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1865137086
With the submission of the PRs above, I consider this subtask complete.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
ppkarwasz closed issue #1955: Generate reference documentation and XSD from
metadata
URL: https://github.com/apache/logging-log4j2/issues/1955
--
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 spe
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1845875643
> This translates to
>
> ```
> plugins --(Log4j)--> XML --(Modello)--> XSD
> ```
>
> How would you compare this to the following?
>
> ```
> plug
vy commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1827716745
> `log4j-plugins` will generate some XML ... We'll use Modello to parse
these XML files and generate ... XSD
This translates to
```
plugins --(Log4j)--> XML --(Mod
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1827709401
> 1. `log4j-plugins` parses Log4j plugins and generates some sort of DOM
model already – correct me if I am wrong. How would you compare us generating
an XSD out of this DO
vy commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1827628000
1. `log4j-plugins` parses Log4j plugins and generates some sort of DOM model
already – correct me if I am wrong. How would you compare us generating an XSD
out of this DOM model v
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1827612448
@vy,
These solutions are quite rigid. The one that gave the best result (Modello)
would still need some code modifications in `modello-plugin-xsd` to give an XSD
tha
vy commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1827448134
How would you compare these solutions to simply rendering an XSD/JSON and
mapping it to a `Map` passed to a [FreeMarker?] template where
we can generate whatever plain-text (Ascii
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1826088251
An experiment performed using Modello (cf. the [Log4j Documentation
Reference using Modello
gist](https://gist.github.com/ppkarwasz/2b4df90cbad54c3d15adf4a524466e35)),
sho
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1826073398
A **second** requirement from the metadata format is the availability of
tools to generate various formats of documentation:
- as far as I can tell OSGi Declarative S
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1825627975
Our plugins can be approximately modeled as
[JavaBeans](https://en.wikipedia.org/wiki/JavaBeans), i.e. as Java classes with
a set of documented properties, so a descriptor
jvz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1806543132
Oh that all sounds fantastic!
--
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
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1806540019
The main plan here is to have a documentation like Maven plugins (e.g.
[Maven Compiler
Plugin](https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html)).
jvz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1806523340
Neat, this is an idea I've had in the past. It would be great if we had
proper XSDs that made it easier to edit a log4j configuration file. Might be
useful to see if this schema
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1803494586
> @ppkarwasz, I completely support the research phase you described. Though
I will also appreciate some non-Maven-native solutions (besides an XSD) too.
Sure thing, m
vy commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1803476849
> A loose list of metadata formats we might consider:
>
> * an XML Schema itself,
> * a [Plexus component
descriptor](https://codehaus-plexus.github.io/guides/developer-g
ppkarwasz commented on issue #1955:
URL:
https://github.com/apache/logging-log4j2/issues/1955#issuecomment-1802411829
A loose list of metadata formats we might consider:
- an XML Schema itself,
- a [Plexus component
descriptor](https://codehaus-plexus.github.io/guides/developer-gu
ppkarwasz opened a new issue, #1955:
URL: https://github.com/apache/logging-log4j2/issues/1955
Log4j plugins follow a slightly modified
[JavaBean](https://en.wikipedia.org/wiki/JavaBeans) model. As a first step of
#1954 we should:
- [ ] research the available metadata formats that co
18 matches
Mail list logo
