OZ-627: Add step to generate and copy Ozone info file #85
Conversation
| </goals> | ||
| <configuration> | ||
| <target> | ||
| <echo file="${project.build.directory}/ozone-info.txt"> |
There was a problem hiding this comment.
I'm guessing we could add more to it.
@mks-d , this is probably the foundation of this file where all versions of a given Ozone distros will be documented.
What would you suggest for its name and format?
There was a problem hiding this comment.
You mean the format of the file itself? I guess that JSON is always better, as it will allow to nest version infos like addons explicitly added for every app, whenever applicable.
If it's indeed the file that starts stating the versions of the Ozone apps... then ozone-versions?
There was a problem hiding this comment.
JSON can be good format for representing structured & hierarchical data, but not ideal for informational text intended for human readability, however for this use case should be fine I guess since we can process the JSON further to a generate a rich & display friendly format e.g HTML or Markdown.
There was a problem hiding this comment.
Let's call this ozone-info.json for now. Let's see where that leads us.
mks-d
changed the title
Issue: https://mekomsolutions.atlassian.net/jira/software/c/projects/OZ/issues/OZ-627
maven-antrun-pluginto generate theozone-info.txtfile on the fly and another one in themaven-resources-pluginto copy the generatedozone-info.txtfile to the final distro zip.