I think the thinking was to not do this because it would create a false impression of those plugins being approved and verified for the 9.0 release.
However, I agree with you that, seeing as how many have been asking about this, it would help to do this. The question is, now that we have released, how do we do this update, i.e., after we make this change, how do we publish it? We need a process for that so that we all know how to follow it. Gj On Fri, Aug 17, 2018 at 7:39 AM, Jaroslav Tulach <[email protected]> wrote: > Dne Čt 16. srpna 2018 09:15:37, Geertjan Wielenga napsal(a): > > > > https://www.infoq.com/news/2018/08/netbeans-apache-update-aug18 > > > > I can see the continuing effort to explain "where have all the modules > gone?" > in the article. Rather than writing long blog posts with howtos, why not > add > the 8.2 update center to the default installation? > > https://github.com/apache/incubator-netbeans/blob/ > master/updatecenters/src/org/netbeans/modules/updatecenters/resources/mf- > layer.xml > > https://github.com/apache/incubator-netbeans/blob/ > master/updatecenters/src/org/netbeans/modules/updatecenters/resources/ > Bundle.properties > > Just register new update center there, let it point to 8.2 catalog. Either > disable it by default or even enable it by default. Then no URL copying > and > pasting will be needed to activate C, C++, JavaEE & co. and they will be > seen > more as more natural part of the upcoming Apache NetBeans releases than > they > are right now. > > -jt > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
