I am open to discuss whether some particular bits should be hosted
elsewhere from their current location, but moving all to a new file
sounds like un-rooting many of those pieces from their natural biotope.
E.g. for artifactId: everybody knows the master value is in pom.xml,
copying it to a new file will introduce a new problem of keeping the two
in sync. -- P
On 16/04/2020 17:05, Claus Ibsen wrote:
Hi
The information we put together for camel-catalog are assembled from
source code, pom.xml, and potentially other places.
>
I have thought of having a csv file (or whatever format) in the root
of components folder, where we can override the information that are
being used. As this allows to easily maintain that information instead
of having to go to each .java source code for the @UriEndpoiint and
whatnot.
So the csv file could be something like
artifactId=camel-ftp,name=ftps,description=Bla bla,supportLevel=Preview
We can of course use other formats. Or have different files for
components, languages, data formats, others, etc and then have a fixed
order, so you can easily edit this from even a spreadsheet
Any thoughts?
