Adalennis commented on issue #3297:
URL: https://github.com/apache/hop/issues/3297#issuecomment-6586143655
@hansva I'd like to pick this one up. A proposal for the scope, which I
tried locally on three pages:
Attributes in the `asciidoc.attributes` of both antora.yml files (user
manual and dev manual), with the values from the poms on main:
- `java-version`: 21
- `beam-version`: 2.74.0
- `beam-spark-version`: 3.5.8 (the Spark the Beam Spark runner uses)
- `spark-version`: 4.1.3 (the native Spark engine)
- `flink-version`: 1.19
The current Hop version is already available as `{page-component-version}`.
Both antora.yml files are already edited at every release (Change documentation
version in release branch), so the values would be updated in the same step.
Pages would use these where the text means "the version Hop uses now". Code
blocks only replace attributes with `subs="attributes+"`, so those blocks get
that option. Historical mentions ("since version 2.15.0", "Deprecated since
2.18.0", "Measured support (Hop 2.19 / Beam 2.74, client submit)") and examples
(`hop.version=2.19.0`) would stay as they are, since they shouldn't change with
a release.
While going through the pages I'd also fix two outdated passages: the Hop
Web dev page says "Verify Java 21: Run `java -version` (should show version
17)", and the Flink samples page still refers to Hop 1.2, Flink 1.13 and JDK 8.
Does that match what you had in mind, or would you like other values (or
fewer) centralized?
--
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 specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
