On Fri, 2021-02-05 at 08:36 +0100, Hervé BOUTEMY wrote: > Le jeudi 4 février 2021, 19:14:03 CET Oleg Kalnichevski a écrit : > > > Please note that one can push generated non-stable stuff to this > > > while > > > the stable will point to. I consider it logically. Since we are > > > tagging > > > our source code and finalize its produced binaries in Maven > > > Central, > > > so > > > should this apply to any other generated content. > > > > This is precisely why versioned reports should also go into Maven > > Central. That is what we do with javadocs and sources. > just FYI: > > javadocs and sources go to Central because it's Central rules to > require them: > other reports are not part of these rules > > 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? > I hope it can help build better mutual understanding > I am fine agreeing to disagree here. Anyways, website content management should be working now exactly as you have recommended. The last thing I would really appreciate you could help us do is migration from APT to Markdown. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
