[ https://issues.apache.org/jira/browse/NETBEANS-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855817#comment-16855817 ]
Christian Lenz edited comment on NETBEANS-2331 at 6/4/19 3:11 PM: ------------------------------------------------------------------ {quote} Another proposal, if we still want to have the sigining, should add the not signed plugins as default to NetBeans and show the user which plugins are signed and which not. That everyone can find the plugin inside of the NetBeans plugin manager and not on both, the page and manager. That is a pain in the ass. {quote} I think that could be a good and easy solution? I think NetBeans will sort out all plugins from the view, they are not signed, right? If yes, remove that check, show everything inside it and make a mark on each plugin which means signed or not signed. Or do it on the installation dialog like a warning as it is already done so far. was (Author: chrizzly): > Another proposal, if we still want to have the sigining, should add the not > signed plugins as default to NetBeans and show the user which plugins are > signed and which not. That everyone can find the plugin inside of the > NetBeans plugin manager and not on both, the page and manager. That is a pain > in the ass. I think that could be a good and easy solution? I think NetBeans will sort out all plugins from the view, they are not signed, right? If yes, remove that check, show everything inside it and make a mark on each plugin which means signed or not signed. Or do it on the installation dialog like a warning as it is already done so far. > Make signing of plugins mandatory or remove it completely > --------------------------------------------------------- > > Key: NETBEANS-2331 > URL: https://issues.apache.org/jira/browse/NETBEANS-2331 > Project: NetBeans > Issue Type: Improvement > Components: platform - Module System, updatecenters - Pluginportal > Affects Versions: Next > Reporter: Christian Lenz > Priority: Major > > Atm the moment, the process is you can create and upload a plugin on the > plugin page. Everything is fine and you need to go to that page if you want > to download this plugin which is not signed. So you will not find it on the > plugin manager of NetBeans. > If you want to see it inside of the plugin manager inside NetBeans, you need > to sign the plugin or you can add the catalg for unsigned plugins. > The thing is, some or maybe most of plugin developers doesn't know to > generate the keystore file or it is to complicated and often a pain in the > ass. > So my proposal is either we make it mandatory for Ant and Maven (Maybe Gradle > too) to sign the plugin inside of the project settings where you can fill in > the stuff, that is needed or we remove the signing stuff completely. Afaik VS > Code or IntelliJ doesn't have such process. But only guessing. > When I had a look into the docu of IntelliJ to create a plugin, I couldn't > find an info for sigining a plugin. > Another proposal, if we still want to have the sigining, should add the not > signed plugins as default to NetBeans and show the user which plugins are > signed and which not. That everyone can find the plugin inside of the > NetBeans plugin manager and not on both, the page and manager. That is a pain > in the ass. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists