On Thu, Jul 16, 2020 at 7:33 AM Jan Lahoda <lah...@gmail.com> wrote: > I would expect more complaints if we simply drop the repository.
Yes, this seems dangerous. There is no need to “support” old versions of NetBeans, but there is an expectation that Maven release artifacts are immutable and permanent, even if the repository URL must be updated from time to time. As I mentioned recently, it seems impossible to build modules using Maven that use javac APIs, a pretty basic use case for Java IDE extensions, if you update to Apache versions. So not only would existing source commits no longer be buildable, there would be no obvious and simple fix. The Jenkins project consumes some old artifacts such as `org.netbeans.modules:org-netbeans-insane:RELEASE111` (I think only for tests). Could probably update to Apache / Central versions. Currently https://repo.jenkins-ci.org/public/ mirrors bits.netbeans.org and has certain artifacts cached, so decommissioning would not cause historical commits to become unbuildable that I know of. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
