I think it's a good idea to have information in a central location, but I do believe the csv approach is a bit error prone.
Maybe we could focus on improving the information we already have in terms of @UriEndpoint and java source code Il giorno gio 16 apr 2020 alle ore 17:06 Claus Ibsen <[email protected]> ha scritto: > 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? > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
