Hi there, Jason! This is a valid point and I have to be honest with you, I like the idea very much :) Maybe having an option to have a flat readme or a tree-organization could be satisfy both preferences, WDYT?
Thanks for your feedback and all the best! ~Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Thu, Aug 2, 2018 at 3:26 PM Jason E Bailey <[email protected]> wrote: > This looks cool. As a selfish ask, I would love the option to cascade > everything into a single readme.md per package. This would be wonderful for > me on a number of projects, not just Sling. > > -- > Jason > > On Thu, Aug 2, 2018, at 3:57 AM, Konrad Windszus wrote: > > Hi Simone, > > this looks great. Just some comments: > > > > > > How it works: it is a plain Java8 annotations processor, able to > generate > > > documentations for: > > > > > > * SlingServlet annotated components; > > > * (Deprecated) Felix SCR annotations (we still have lot of components > in > > > the repo which use such annotations, i.e. Apache Sling Distribution > Core) > > > * OSGi Component/Metatype annotations > > > > What about instead acting on top of the generated component definitions > > or metatype resources? That way you would be independent of how they > > have been generated? > > Konrad >
