Le vendredi 5 février 2021, 18:32:39 CET Oleg Kalnichevski a écrit :
> > and why is it Central rules for javadocs and sources?
> > because it is useful for IDEs lookup for every end-user (which
> > honestly
> > nowadays only require sources, not javadocs any more: Central rules
> > could
> > probably be lightened, but that's another story)
> > other reports are not useful for any normal end-user (through their
> > IDE or any
> > other tools): other reports are purely project internal details, to
> > publish to
> > project's website = what svnpubsub and its internal svn storage are
> > done for
> 
> and why would not an API compatibility report to useful for every
> normal end-user? Why do no we publish those reports on our project
> website if they are not useful?
Yes, useful on your website for users using their web browsers to look at it

But not useful as a zip file pushed to Maven Central

Don't hesitate to test such a report for example with japicmp-maven-plugin
https://siom79.github.io/japicmp/
And publish the SNAPSHOT doc to LATEST
That's what the current structure makes easy.

> 
> > I hope it can help build better mutual understanding
> 
> I am fine agreeing to disagree here.
it seems mutual efforts are not mutual: ok, no problem, I was just helping, job 
done, I can get back to use my time where it is enjoyable

> 
> Anyways, website content management should be working now exactly as
> you have recommended.
the last point will be to move /components to a separate svn tree: @Michael, I 
suppose you understand and know how to do that (and I can't do it for you, 
require INFRA tasks)

> 
> The last thing I would really appreciate you could help us do is
> migration from APT to Markdown.
sorry, I don't have any tools for that: it's a job to be done file by file, at 
your own pace

bye

Hervé

> 
> Oleg
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to