Hi,
Would not be easier to allow plug-in developers to register their
updates center "on the fly".
We would do a git repository on github.
There plug-in developer would add an xml file with a link, name, etc.,
to his update center via PR.
The approval process would remain preserved...
And on the Settings tab, the "Show Available Update Centers" button
would be added.
This would download the current list of update centers from the git
repository and allow to add it...
Then it will be up to the developer preference to use
raw.githubusercontent.com or any other server...
Arsi
------------------------------------------------------------------------
*From:* Geertjan Wielenga <geertjan.wiele...@googlemail.com.INVALID>
*Sent:* Friday, April 05, 2019 8:31PM
*To:* Dev <dev@netbeans.incubator.apache.org>
*Subject:* Re: plugins.netbeans.org / netbeans.org
Here's the rough proposal:
1. Move all the plugins to Maven Central. Blockers: we don't know how to do
that, if someone can advise, that will help.
2. Refactor the plugins.netbeans.org application so that (1) NBM files
cannot be uploaded anymore and (2) instead of uploading, references need to
be registered to the location of the NBM on Maven Central. Blockers: this
is being investigated at the moment, timelines not known yet. This is
doable because the plugins.netbeans.org application has been donated to
Apache as part of the 3rd donation.
3. Deploy the plugins.netbeans.org application from the Apache NetBeans VM.
There should be no problem with that since we'll not be distributing the
NBMs from Apache (which would have been a problem since Apache distributes
source code only) but only pages or references to Maven Central.
4. Enable the Plugin Manager inside Apache NetBeans to install NBM files
directly from Maven Central, based on the references retrieved via the
Update Center from the plugins.netbeans.org application running on the
Apache NetBeans VM.
5. Continue using the plugins.netbeans.org URL, except that this will now
be running at Apache and pointing to the plugins.netbeans.org application
running on the Apache NetBeans VM.
So, the above would mean that nothing is running on Oracle servers anymore,
all NBMs that we care about are on Maven Central (and source code could
mostly be on GitHub, except where plugin owners don't want their source
code exposed, in which case they'd have it in their local proprietary
backends), and we have the plugins.netbeans.org application refactored and
simply showing Maven co-ordinated to the plugins on Maven Central.
How does that sound?
Gj
On Fri, Apr 5, 2019 at 8:21 PM Antonio <anto...@vieiro.net> wrote:
Hi all,
After the 11.0 release announcement, where we migrated most of
bits.netbeans.org, shall we tackle the plugins.netbeans.org website and
infrastructure for 12.0? Or is it too early? Also, what's missing in
netbeans.apache.org that still exists in netbeans.org and we want to keep?
I can't remember when the infra @ Oracle for plugins.netbeans.org is
going to be shutdown, but the sooner we start thinking on hosting the
plugins, the better. This is something that is going to take us long, I
think.
Thoughts?
Thanks,
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
