Re: [External] : plugin verification
Hi Jiri, I did. I'm going to be on summer holidays from the 6th of July to the 4th of August. Will have limited access to my laptop, so I may not do much during that period. Have great holidays you all too! Regards, Le mer. 3 juil. 2024 à 09:37, Jiří Kovalský a écrit : > I have verified all plugins in my queue today. > > Mani, Geertjan, Carlos - please join me with your verifications. > > -Jirka > > Dne 05. 06. 24 v 18:47 Ernie Rael napsal(a): > > Every once in a while verification starts slipping, suggestions for > > automatic verification renewal gain traction, then verification starts > > up again. > > > > Wondering if there's a causal relationship. > > > > - > > 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://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!MbUm98-KfocN4w0sH5TBGyijEnjC0ChaidGKNKi9YhF_5zuVzqFiRIL0c2N99IyLG_PofBUotlTruoIzKRA$ > > > > >
Re: [External] : plugin verification
Thanks for the ping Jirka. Plus, more are welcome to join us. Gj On Wed, Jul 3, 2024 at 9:37 AM Jiří Kovalský wrote: > > I have verified all plugins in my queue today. > > Mani, Geertjan, Carlos - please join me with your verifications. > > -Jirka > > Dne 05. 06. 24 v 18:47 Ernie Rael napsal(a): > > Every once in a while verification starts slipping, suggestions for > > automatic verification renewal gain traction, then verification starts > > up again. > > > > Wondering if there's a causal relationship. > > > > - > > 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://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!MbUm98-KfocN4w0sH5TBGyijEnjC0ChaidGKNKi9YhF_5zuVzqFiRIL0c2N99IyLG_PofBUotlTruoIzKRA$ > > > > > > - > 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 > > > - 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
Re: [External] : plugin verification
I have verified all plugins in my queue today. Mani, Geertjan, Carlos - please join me with your verifications. -Jirka Dne 05. 06. 24 v 18:47 Ernie Rael napsal(a): Every once in a while verification starts slipping, suggestions for automatic verification renewal gain traction, then verification starts up again. Wondering if there's a causal relationship. - 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://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!MbUm98-KfocN4w0sH5TBGyijEnjC0ChaidGKNKi9YhF_5zuVzqFiRIL0c2N99IyLG_PofBUotlTruoIzKRA$ - 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
plugin verification
Every once in a while verification starts slipping, suggestions for automatic verification renewal gain traction, then verification starts up again. Wondering if there's a causal relationship. - 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
Re: NetBeans Plugin Verification - Changing Rules - suddenly not good enough anymore
Ahh sorry Matthias Bläsing and Fabian Bahle.
I read again and understand.
Em seg., 30 de jan. de 2023 às 18:09, Fabian Bahle
escreveu:
> Hi,
>
> I think Matthias Bläsing (correct me if I’m wrong) knows how to sign, but
> the question here is why do we need to sign plugins that were already
> verified for earlier NetBeans versions, what changed in NetBeans 17 that we
> need the signing now?
>
> I did get the same response for my plugins and I just signed them, but I
> was wondering why this is needed now as well.
> I thought I might missed something here and therefore just signed my
> plugins and did a new release.
>
>
> Kind regards,
> Fabian
>
>
> > Am 30.01.2023 um 21:09 schrieb Moacir da Roza :
> >
> > Hi a more detailed explanation, believe they need to be signed with a key
> > included on keystore a more.
> >
> > *1-* Use java key tool on command line
> >
> > keytool -genkey -keyalg RSA -alias *my-key-alias-key* -keystore
> > *keystore.jks* -validity 365
> > Answer all question and password.
> >
> > *2-* Include on pom.xml
> >
> >org.apache.netbeans.utilities
> >nbm-maven-plugin
> >4.7
> >true
> >
> >Moacir da Roza flores-moaci...@gmail.com
> >
> >GNU GENERAL PUBLIC LICENSE
> > 3.0
> >LICENSE
> >
> > *${basedir}/keystore.jks*
> >
> >
> > *${keypass}
> >my-key-alias-key *
> >
> >
> >
> >
> > *3- *Now build passing the password
> > *mvn -Dkeypass=password nbm:nbm*
> >
> >
> >
> >
> >
> > Em seg., 30 de jan. de 2023 às 17:00, Moacir da Roza >
> > escreveu:
> >
> >> I believe they need to be signed with a key included on keystore
> >>
> >> *1-* Use java key tool:
> >>
> >> keytool -genkey -keyalg RSA -alias my-key-alias-key -keystore
> keystore.jks
> >> -validity 365
> >>
> >>
> >> *2-* Include on pom.xml
> >>
> >>org.apache.netbeans.utilities
> >>nbm-maven-plugin
> >>4.7
> >>true
> >>
> >>
> >> ${netbeansInstalationPath}
> -->
> >>${basedir}/keystore.jks
> >>${keypass}
> >>my-key-alias-key
> >>
> >>
> >>
> >>
> >>
> >> Em seg., 30 de jan. de 2023 às 15:03, Matthias Bläsing
> >> escreveu:
> >>
> >>> Hi,
> >>>
> >>> I asked for reverification of three plugins. These plugins:
> >>>
> >>> - PlantUML-NB
> >>> - LDIF Editor
> >>> - LDAP Explorer
> >>>
> >>> are verified for NB 11.0/12.0 till NB 16 version. Nothing was changed
> >>> on the plugins for 17 and now the plugins are not good enough anymore.
> >>> So what is going on?
> >>>
> >>> They are rejected, because they are not signed, fine, but then why is
> >>> that an issue? The signatures gain you nothing as there is no trust
> >>> anchor, we don't distribute blocked author certificates and the
> >>> download from plugin portal is protected by the checksums.
> >>>
> >>> This is bogus, so what changed and why was this not communicated? I
> >>> assume, that I was not the only one suprised by this. What is more, I'd
> >>> need to do a full release cycle without any code changes, without any
> >>> benefit.
> >>>
> >>> Greetings
> >>>
> >>> Matthias
> >>>
> >>> PS: Jiří I added you to direct CC as I'm not sure how closely you
> >>> monitor dev@
> >>>
> >>> -
> >>> 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
> >>>
> >>>
> >>>
> >>>
> >>
> >> --
> >> Moacir R.F
> >> Desenvolvedor de Softwares
> >>
> >> https://www.moacirrf.com.br
> >>
> >
> >
> > --
> > Moacir R.F
> > Desenvolvedor de Softwares
> >
> > https://www.moacirrf.com.br
>
>
> -
> 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
>
>
>
>
--
Moacir R.F
Desenvolvedor de Softwares
https://www.moacirrf.com.br
Re: NetBeans Plugin Verification - Changing Rules - suddenly not good enough anymore
On Mon, 30 Jan 2023 at 20:08, Matthias Bläsing wrote: > yes, I know how I can sign JARs/NBMs, the point is: This was not > necessary for multiple NetBeans releases. I'm missing the explanation > why something, that was fine for at least 5, releases is now a problem. > > That communication did not happen and was not discussed here. Welcome to the "verification process isn't working" side of the conversation! :-) Yes, this doesn't seem right. These things should be discussed on dev@ We're about to switch to the NB17 plugin portal for 17-rc3 (as agreed with plugin portal verifiers off-list - so far we kept NB16 portal). The more existing plugins that are verified the better. It's one way of checking if we've introduced inadvertent changes in the IDE since the last release. IMO there are two main reasons a plugin that was verified for the last release shouldn't be in this one. The plugin was using implementation versions, in which case it shouldn't have been verified in the first place. Or we broke backwards compatibility, deliberately or inadvertently, and should consider the problem. Other than that, if it was verified fine for 16 I don't see a reason to apply different rules to 17?! Best wishes, Neil - 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
Re: NetBeans Plugin Verification - Changing Rules - suddenly not good enough anymore
Hi,
I think Matthias Bläsing (correct me if I’m wrong) knows how to sign, but the
question here is why do we need to sign plugins that were already verified for
earlier NetBeans versions, what changed in NetBeans 17 that we need the signing
now?
I did get the same response for my plugins and I just signed them, but I was
wondering why this is needed now as well.
I thought I might missed something here and therefore just signed my plugins
and did a new release.
Kind regards,
Fabian
> Am 30.01.2023 um 21:09 schrieb Moacir da Roza :
>
> Hi a more detailed explanation, believe they need to be signed with a key
> included on keystore a more.
>
> *1-* Use java key tool on command line
>
> keytool -genkey -keyalg RSA -alias *my-key-alias-key* -keystore
> *keystore.jks* -validity 365
> Answer all question and password.
>
> *2-* Include on pom.xml
>
>org.apache.netbeans.utilities
>nbm-maven-plugin
>4.7
>true
>
>Moacir da Roza flores-moaci...@gmail.com
>
>GNU GENERAL PUBLIC LICENSE
> 3.0
>LICENSE
>
> *${basedir}/keystore.jks*
>
>
> *${keypass}
>my-key-alias-key *
>
>
>
>
> *3- *Now build passing the password
> *mvn -Dkeypass=password nbm:nbm*
>
>
>
>
>
> Em seg., 30 de jan. de 2023 às 17:00, Moacir da Roza
> escreveu:
>
>> I believe they need to be signed with a key included on keystore
>>
>> *1-* Use java key tool:
>>
>> keytool -genkey -keyalg RSA -alias my-key-alias-key -keystore keystore.jks
>> -validity 365
>>
>>
>> *2-* Include on pom.xml
>>
>>org.apache.netbeans.utilities
>>nbm-maven-plugin
>>4.7
>>true
>>
>>
>> ${netbeansInstalationPath} -->
>>${basedir}/keystore.jks
>>${keypass}
>>my-key-alias-key
>>
>>
>>
>>
>>
>> Em seg., 30 de jan. de 2023 às 15:03, Matthias Bläsing
>> escreveu:
>>
>>> Hi,
>>>
>>> I asked for reverification of three plugins. These plugins:
>>>
>>> - PlantUML-NB
>>> - LDIF Editor
>>> - LDAP Explorer
>>>
>>> are verified for NB 11.0/12.0 till NB 16 version. Nothing was changed
>>> on the plugins for 17 and now the plugins are not good enough anymore.
>>> So what is going on?
>>>
>>> They are rejected, because they are not signed, fine, but then why is
>>> that an issue? The signatures gain you nothing as there is no trust
>>> anchor, we don't distribute blocked author certificates and the
>>> download from plugin portal is protected by the checksums.
>>>
>>> This is bogus, so what changed and why was this not communicated? I
>>> assume, that I was not the only one suprised by this. What is more, I'd
>>> need to do a full release cycle without any code changes, without any
>>> benefit.
>>>
>>> Greetings
>>>
>>> Matthias
>>>
>>> PS: Jiří I added you to direct CC as I'm not sure how closely you
>>> monitor dev@
>>>
>>> -
>>> 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
>>>
>>>
>>>
>>>
>>
>> --
>> Moacir R.F
>> Desenvolvedor de Softwares
>>
>> https://www.moacirrf.com.br
>>
>
>
> --
> Moacir R.F
> Desenvolvedor de Softwares
>
> https://www.moacirrf.com.br
-
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
Re: NetBeans Plugin Verification - Changing Rules - suddenly not good enough anymore
Hi a more detailed explanation, believe they need to be signed with a key
included on keystore a more.
*1-* Use java key tool on command line
keytool -genkey -keyalg RSA -alias *my-key-alias-key* -keystore
*keystore.jks* -validity 365
Answer all question and password.
*2-* Include on pom.xml
org.apache.netbeans.utilities
nbm-maven-plugin
4.7
true
Moacir da Roza flores-moaci...@gmail.com
GNU GENERAL PUBLIC LICENSE
3.0
LICENSE
*${basedir}/keystore.jks*
*${keypass}
my-key-alias-key *
*3- *Now build passing the password
*mvn -Dkeypass=password nbm:nbm*
Em seg., 30 de jan. de 2023 às 17:00, Moacir da Roza
escreveu:
> I believe they need to be signed with a key included on keystore
>
> *1-* Use java key tool:
>
> keytool -genkey -keyalg RSA -alias my-key-alias-key -keystore keystore.jks
> -validity 365
>
>
> *2-* Include on pom.xml
>
> org.apache.netbeans.utilities
> nbm-maven-plugin
> 4.7
> true
>
>
> ${netbeansInstalationPath} -->
> ${basedir}/keystore.jks
> ${keypass}
> my-key-alias-key
>
>
>
>
>
> Em seg., 30 de jan. de 2023 às 15:03, Matthias Bläsing
> escreveu:
>
>> Hi,
>>
>> I asked for reverification of three plugins. These plugins:
>>
>> - PlantUML-NB
>> - LDIF Editor
>> - LDAP Explorer
>>
>> are verified for NB 11.0/12.0 till NB 16 version. Nothing was changed
>> on the plugins for 17 and now the plugins are not good enough anymore.
>> So what is going on?
>>
>> They are rejected, because they are not signed, fine, but then why is
>> that an issue? The signatures gain you nothing as there is no trust
>> anchor, we don't distribute blocked author certificates and the
>> download from plugin portal is protected by the checksums.
>>
>> This is bogus, so what changed and why was this not communicated? I
>> assume, that I was not the only one suprised by this. What is more, I'd
>> need to do a full release cycle without any code changes, without any
>> benefit.
>>
>> Greetings
>>
>> Matthias
>>
>> PS: Jiří I added you to direct CC as I'm not sure how closely you
>> monitor dev@
>>
>> -
>> 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
>>
>>
>>
>>
>
> --
> Moacir R.F
> Desenvolvedor de Softwares
>
> https://www.moacirrf.com.br
>
--
Moacir R.F
Desenvolvedor de Softwares
https://www.moacirrf.com.br
Re: NetBeans Plugin Verification - Changing Rules - suddenly not good enough anymore
Hi,
yes, I know how I can sign JARs/NBMs, the point is: This was not
necessary for multiple NetBeans releases. I'm missing the explanation
why something, that was fine for at least 5, releases is now a problem.
That communication did not happen and was not discussed here.
Greetings
Matthias
Am Montag, dem 30.01.2023 um 17:00 -0300 schrieb Moacir da Roza:
> I believe they need to be signed with a key included on keystore
>
> *1-* Use java key tool:
>
> keytool -genkey -keyalg RSA -alias my-key-alias-key -keystore keystore.jks
> -validity 365
>
>
> *2-* Include on pom.xml
>
> org.apache.netbeans.utilities
> nbm-maven-plugin
> 4.7
> true
>
>
> ${netbeansInstalationPath} -->
> ${basedir}/keystore.jks
> ${keypass}
> my-key-alias-key
>
>
>
>
>
> Em seg., 30 de jan. de 2023 às 15:03, Matthias Bläsing
> escreveu:
>
> > Hi,
> >
> > I asked for reverification of three plugins. These plugins:
> >
> > - PlantUML-NB
> > - LDIF Editor
> > - LDAP Explorer
> >
> > are verified for NB 11.0/12.0 till NB 16 version. Nothing was changed
> > on the plugins for 17 and now the plugins are not good enough anymore.
> > So what is going on?
> >
> > They are rejected, because they are not signed, fine, but then why is
> > that an issue? The signatures gain you nothing as there is no trust
> > anchor, we don't distribute blocked author certificates and the
> > download from plugin portal is protected by the checksums.
> >
> > This is bogus, so what changed and why was this not communicated? I
> > assume, that I was not the only one suprised by this. What is more, I'd
> > need to do a full release cycle without any code changes, without any
> > benefit.
> >
> > Greetings
> >
> > Matthias
> >
> > PS: Jiří I added you to direct CC as I'm not sure how closely you
> > monitor dev@
> >
> > -
> > 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
> >
> >
> >
> >
>
-
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
Re: NetBeans Plugin Verification - Changing Rules - suddenly not good enough anymore
I believe they need to be signed with a key included on keystore
*1-* Use java key tool:
keytool -genkey -keyalg RSA -alias my-key-alias-key -keystore keystore.jks
-validity 365
*2-* Include on pom.xml
org.apache.netbeans.utilities
nbm-maven-plugin
4.7
true
${netbeansInstalationPath} -->
${basedir}/keystore.jks
${keypass}
my-key-alias-key
Em seg., 30 de jan. de 2023 às 15:03, Matthias Bläsing
escreveu:
> Hi,
>
> I asked for reverification of three plugins. These plugins:
>
> - PlantUML-NB
> - LDIF Editor
> - LDAP Explorer
>
> are verified for NB 11.0/12.0 till NB 16 version. Nothing was changed
> on the plugins for 17 and now the plugins are not good enough anymore.
> So what is going on?
>
> They are rejected, because they are not signed, fine, but then why is
> that an issue? The signatures gain you nothing as there is no trust
> anchor, we don't distribute blocked author certificates and the
> download from plugin portal is protected by the checksums.
>
> This is bogus, so what changed and why was this not communicated? I
> assume, that I was not the only one suprised by this. What is more, I'd
> need to do a full release cycle without any code changes, without any
> benefit.
>
> Greetings
>
> Matthias
>
> PS: Jiří I added you to direct CC as I'm not sure how closely you
> monitor dev@
>
> -
> 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
>
>
>
>
--
Moacir R.F
Desenvolvedor de Softwares
https://www.moacirrf.com.br
NetBeans Plugin Verification - Changing Rules - suddenly not good enough anymore
Hi, I asked for reverification of three plugins. These plugins: - PlantUML-NB - LDIF Editor - LDAP Explorer are verified for NB 11.0/12.0 till NB 16 version. Nothing was changed on the plugins for 17 and now the plugins are not good enough anymore. So what is going on? They are rejected, because they are not signed, fine, but then why is that an issue? The signatures gain you nothing as there is no trust anchor, we don't distribute blocked author certificates and the download from plugin portal is protected by the checksums. This is bogus, so what changed and why was this not communicated? I assume, that I was not the only one suprised by this. What is more, I'd need to do a full release cycle without any code changes, without any benefit. Greetings Matthias PS: Jiří I added you to direct CC as I'm not sure how closely you monitor dev@ - 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
Re: plugin verification and new NB releases
On 6/15/22 12:42 PM, Neil C Smith wrote: On Wed, 15 Jun 2022, 19:04 Ernie Rael, wrote: We effectively had automatic extension from 12.0 to 12.6, because we used the same plugins URL Look like there's still some kind of automatic extension going on. 14 has a 14 url, but there plenty of stuff in .../plugins/14/catalog.xml.gz, although the plugin portal doesn't know about 14. Truly magical. Not really! It appears my temporary redirect at feature freeze has not been able to be updated yet? So not magic, just good luck. (Written on a poster held high: "stop the plugin drain") https://github.com/apache/netbeans-website/blob/master/netbeans.apache.org/src/content/.htaccess#L31 Neil - 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
Re: plugin verification and new NB releases
On Wed, 15 Jun 2022, 19:04 Ernie Rael, wrote: > > We effectively had automatic extension from 12.0 to 12.6, because we > > used the same plugins URL > > Look like there's still some kind of automatic extension going on. 14 > has a 14 url, but there plenty of stuff in > .../plugins/14/catalog.xml.gz, although the plugin portal doesn't know > about 14. Truly magical. > Not really! It appears my temporary redirect at feature freeze has not been able to be updated yet? https://github.com/apache/netbeans-website/blob/master/netbeans.apache.org/src/content/.htaccess#L31 Neil
Re: plugin verification and new NB releases
We effectively had automatic extension from 12.0 to 12.6, because we used the same plugins URL Look like there's still some kind of automatic extension going on. 14 has a 14 url, but there plenty of stuff in .../plugins/14/catalog.xml.gz, although the plugin portal doesn't know about 14. Truly magical. Does the plugin portal exists outside of regular apache project handling? On 6/15/22 2:45 AM, Neil C Smith wrote: On Wed, 15 Jun 2022 at 03:07, Ernie Rael wrote: Might be good to add a version button for a new release early in the process, maybe during RC. +1 (again) - from a releases perspective. In fact, possibly from point of previous release, as we need to point the plugin centre URL for dev builds at something, and testing earlier might make sense. I'd guess it's very rare that a plugin stops working. If an automatic extension to the next release, or something like that, isn't acceptable, +1 (again) - I think we should work on a remove on report basis after initial verification. We effectively had automatic extension from 12.0 to 12.6, because we used the same plugins URL. A couple of plugins broke in that time too. There is no greater change from 12.3 to 12.4 than there is from 13 to 14! So, why not *stay* with automatic extension? Best wishes, Neil - 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 - 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
Re: plugin verification and new NB releases
On Wed, 15 Jun 2022 at 03:07, Ernie Rael wrote: > Might be good to add a version button for a new release early in the > process, maybe during RC. +1 (again) - from a releases perspective. In fact, possibly from point of previous release, as we need to point the plugin centre URL for dev builds at something, and testing earlier might make sense. > I'd guess it's very rare that a plugin stops working. If an automatic > extension to the next release, or something like that, isn't acceptable, +1 (again) - I think we should work on a remove on report basis after initial verification. We effectively had automatic extension from 12.0 to 12.6, because we used the same plugins URL. A couple of plugins broke in that time too. There is no greater change from 12.3 to 12.4 than there is from 13 to 14! So, why not *stay* with automatic extension? Best wishes, Neil - 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
Re: plugin verification and new NB releases
On 6/14/22 10:23 AM, Michael Bien wrote: Hello, I forgot to request verification of my little plugin for NB 13. Then i was wondering - I bet some don't even know that they have to request verification after every NetBeans release, otherwise it won't appear in the plugin manager. Thanks for mentioning this. I usually forget. Thought I'd add a request for NB-14 while I was thinking about it; but alas, new version's not there yet. Might be good to add a version button for a new release early in the process, maybe during RC. Searching through the plugin portal showed some useful plugins which weren't verified since NB 12. Could this be automated? Lets say there is a successful verification for NetBeans N-1, it would automatically request verification for N on release. I'd guess it's very rare that a plugin stops working. If an automatic extension to the next release, or something like that, isn't acceptable, then the automated request seems useful. There was some discussion around this in the "Postmortem 12.5" thread, when the new versioning scheme came about https://lists.apache.org/thread/fzojvpgh6kboh99qfpc22x66wx7jccf9 and there is some discussion about how to specify plugin compatibility, including a suggestion from Jaroslav Tulach, https://issues.apache.org/jira/browse/NETBEANS-5064 It's a shame some plugins are almost lost, I still keep the license changer around. This would increase workload for the verifiers I suppose. There is probably also the argument to be made that the plugin maintainers should care about their plugins and not forget things like I do. Maybe an automated mail to the maintainers as notification to re-request verification? I'd find that useful. -ernie best regards, michael - 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
plugin verification and new NB releases
Hello, I forgot to request verification of my little plugin for NB 13. Then i was wondering - I bet some don't even know that they have to request verification after every NetBeans release, otherwise it won't appear in the plugin manager. Searching through the plugin portal showed some useful plugins which weren't verified since NB 12. Could this be automated? Lets say there is a successful verification for NetBeans N-1, it would automatically request verification for N on release. This would increase workload for the verifiers I suppose. There is probably also the argument to be made that the plugin maintainers should care about their plugins and not forget things like I do. Maybe an automated mail to the maintainers as notification to re-request verification? best regards, michael - 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
Re: Re: Plugin verification
Hi Eric, my answers below. Regards *--* *Alessandro Falappa* Il giorno sab 5 dic 2020 alle ore 17:38 Eric Bresie ha scritto: > So does that still mean a new version of the plug-in can or cannot be used > / verified against an old version of Netbeans? > No, an old plugin version can be verified against an old version of NB. > In other words, should a given plugin version show which versions of > Netbeans it’s compatible against? > This is up to the plugin developer. For example if my plugin version X+1 would support Gradle projects I could verify it against NB12 but leave version X verified against NB11. > Eric Bresie > ebre...@gmail.com (mailto:ebre...@gmail.com) >
Re: Re: Plugin verification
So does that still mean a new version of the plug-in can or cannot be used / verified against an old version of Netbeans? In other words, should a given plugin version show which versions of Netbeans it’s compatible against? Eric Bresie ebre...@gmail.com (mailto:ebre...@gmail.com) > On December 4, 2020 at 4:42:53 AM CST, Alessandro (mailto:alex.fala...@gmail.com)> wrote: > Hi all, > Junichi's suggestion is correct and my reasoning is wrong. > > At any given time there is a single verified plugin version for one > NetBeans version. > This sound reasonable and allows for example to have a former version of a > plugin verified for an older version of NetBeans while a newer version of a > plugin verified for a newer version of NetBeans. > > Verification requested and under way, If you are a plugin verifier please > approve! > > Regards, > *--* > *Alessandro Falappa* > > > Il giorno ven 4 dic 2020 alle ore 11:36 Alessandro (mailto:alex.fala...@gmail.com)> > ha scritto: > > > Hi Junichi, > > this means a plugin cannot be verified for multiple NetBeans versions? > > > > If I understood it correctly after verification the plugin, or its new > > version thereof, "appears" on the UpdateCenter, if I remove the > > verification it "disappears" from the UpdateCenter. This would mean that as > > soon as a plugin is verified for the latest version of NetBeans it > > disappears for the users of previous versions. Sounds like an important > > limitation to me. > > > > Anyway I will try your suggestion. > > > > Thanks for helping, > > Regards > > > > *--* > > *Alessandro Falappa* > > > > > > Il giorno ven 4 dic 2020 alle ore 11:25 Junichi Yamamoto < > > junichi0...@gmail.com (mailto:junichi0...@gmail.com)> ha scritto: > > > > > Hi, > > > > > > Please try to drop verification for the old version. Then, try to go > > > to the new version page. > > > > > > HTH, > > > Junichi > > > > > > On Sun, Nov 29, 2020 at 9:16 PM Alessandro > > (mailto:alex.fala...@gmail.com)> > > > wrote: > > > > > > > > Hi all, > > > > while testing the recently released NetBeans 12.2 Linux installer I > > > > noticed that in NB12.2 the older version of my NBSpringBoot plugin is > > > > available from the Update Center. > > > > > > > > I went on the new plugin portal and realized that the last version was > > > not > > > > verified while the older was but I don't seem to find a way to request > > > > verification of the last version. > > > > I went to MyPlugins section, clicked on edit button for NBSpringBoot > > > plugin > > > > then on edit button for last version, it shows the plugin enabled for NB > > > > 11.0 and 12.0 but no way to request verification, if I recall correctly > > > > there were buttons to request verification against selected NB versions. > > > > > > > > Could someone shed some light on this? > > > > > > > > Thank you in advance for your help. > > > > > > > > Regards > > > > *--* > > > > *Alessandro Falappa* > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > > > (mailto:dev-unsubscr...@netbeans.apache.org) > > > For additional commands, e-mail: dev-h...@netbeans.apache.org > > > (mailto:dev-h...@netbeans.apache.org) > > > > > > For further information about the NetBeans mailing lists, visit: > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > >
Re: Plugin verification
Hi all, Junichi's suggestion is correct and my reasoning is wrong. At any given time there is a single verified plugin version for one NetBeans version. This sound reasonable and allows for example to have a former version of a plugin verified for an older version of NetBeans while a newer version of a plugin verified for a newer version of NetBeans. Verification requested and under way, If you are a plugin verifier please approve! Regards, *--* *Alessandro Falappa* Il giorno ven 4 dic 2020 alle ore 11:36 Alessandro ha scritto: > Hi Junichi, > this means a plugin cannot be verified for multiple NetBeans versions? > > If I understood it correctly after verification the plugin, or its new > version thereof, "appears" on the UpdateCenter, if I remove the > verification it "disappears" from the UpdateCenter. This would mean that as > soon as a plugin is verified for the latest version of NetBeans it > disappears for the users of previous versions. Sounds like an important > limitation to me. > > Anyway I will try your suggestion. > > Thanks for helping, > Regards > > *--* > *Alessandro Falappa* > > > Il giorno ven 4 dic 2020 alle ore 11:25 Junichi Yamamoto < > junichi0...@gmail.com> ha scritto: > >> Hi, >> >> Please try to drop verification for the old version. Then, try to go >> to the new version page. >> >> HTH, >> Junichi >> >> On Sun, Nov 29, 2020 at 9:16 PM Alessandro >> wrote: >> > >> > Hi all, >> > while testing the recently released NetBeans 12.2 Linux installer I >> > noticed that in NB12.2 the older version of my NBSpringBoot plugin is >> > available from the Update Center. >> > >> > I went on the new plugin portal and realized that the last version was >> not >> > verified while the older was but I don't seem to find a way to request >> > verification of the last version. >> > I went to MyPlugins section, clicked on edit button for NBSpringBoot >> plugin >> > then on edit button for last version, it shows the plugin enabled for NB >> > 11.0 and 12.0 but no way to request verification, if I recall correctly >> > there were buttons to request verification against selected NB versions. >> > >> > Could someone shed some light on this? >> > >> > Thank you in advance for your help. >> > >> > Regards >> > *--* >> > *Alessandro Falappa* >> >> - >> 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 >> >> >> >>
Re: Plugin verification
Hi Junichi, this means a plugin cannot be verified for multiple NetBeans versions? If I understood it correctly after verification the plugin, or its new version thereof, "appears" on the UpdateCenter, if I remove the verification it "disappears" from the UpdateCenter. This would mean that as soon as a plugin is verified for the latest version of NetBeans it disappears for the users of previous versions. Sounds like an important limitation to me. Anyway I will try your suggestion. Thanks for helping, Regards *--* *Alessandro Falappa* Il giorno ven 4 dic 2020 alle ore 11:25 Junichi Yamamoto < junichi0...@gmail.com> ha scritto: > Hi, > > Please try to drop verification for the old version. Then, try to go > to the new version page. > > HTH, > Junichi > > On Sun, Nov 29, 2020 at 9:16 PM Alessandro wrote: > > > > Hi all, > > while testing the recently released NetBeans 12.2 Linux installer I > > noticed that in NB12.2 the older version of my NBSpringBoot plugin is > > available from the Update Center. > > > > I went on the new plugin portal and realized that the last version was > not > > verified while the older was but I don't seem to find a way to request > > verification of the last version. > > I went to MyPlugins section, clicked on edit button for NBSpringBoot > plugin > > then on edit button for last version, it shows the plugin enabled for NB > > 11.0 and 12.0 but no way to request verification, if I recall correctly > > there were buttons to request verification against selected NB versions. > > > > Could someone shed some light on this? > > > > Thank you in advance for your help. > > > > Regards > > *--* > > *Alessandro Falappa* > > - > 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 > > > >
Re: Plugin verification
That could work too. Sorry, haven’t heard back yet from Jirka and Jan. Matthias has also done some work in this area recently and might be able to help. Gj On Fri, 4 Dec 2020 at 11:25, Junichi Yamamoto wrote: > Hi, > > Please try to drop verification for the old version. Then, try to go > to the new version page. > > HTH, > Junichi > > On Sun, Nov 29, 2020 at 9:16 PM Alessandro wrote: > > > > Hi all, > > while testing the recently released NetBeans 12.2 Linux installer I > > noticed that in NB12.2 the older version of my NBSpringBoot plugin is > > available from the Update Center. > > > > I went on the new plugin portal and realized that the last version was > not > > verified while the older was but I don't seem to find a way to request > > verification of the last version. > > I went to MyPlugins section, clicked on edit button for NBSpringBoot > plugin > > then on edit button for last version, it shows the plugin enabled for NB > > 11.0 and 12.0 but no way to request verification, if I recall correctly > > there were buttons to request verification against selected NB versions. > > > > Could someone shed some light on this? > > > > Thank you in advance for your help. > > > > Regards > > *--* > > *Alessandro Falappa* > > - > 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 > > > >
Re: Plugin verification
Hi, Please try to drop verification for the old version. Then, try to go to the new version page. HTH, Junichi On Sun, Nov 29, 2020 at 9:16 PM Alessandro wrote: > > Hi all, > while testing the recently released NetBeans 12.2 Linux installer I > noticed that in NB12.2 the older version of my NBSpringBoot plugin is > available from the Update Center. > > I went on the new plugin portal and realized that the last version was not > verified while the older was but I don't seem to find a way to request > verification of the last version. > I went to MyPlugins section, clicked on edit button for NBSpringBoot plugin > then on edit button for last version, it shows the plugin enabled for NB > 11.0 and 12.0 but no way to request verification, if I recall correctly > there were buttons to request verification against selected NB versions. > > Could someone shed some light on this? > > Thank you in advance for your help. > > Regards > *--* > *Alessandro Falappa* - 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
Re: Plugin verification
Yes, though pinged some people who might be able to help. Gj On Thu, Dec 3, 2020 at 4:43 PM Alessandro wrote: > Hi all, > is this the right mailing list to discuss plugin portal issues? > > Regards, > *--* > *Alessandro Falappa* > > > Il giorno dom 29 nov 2020 alle ore 13:16 Alessandro < > alex.fala...@gmail.com> > ha scritto: > > > Hi all, > > while testing the recently released NetBeans 12.2 Linux installer I > > noticed that in NB12.2 the older version of my NBSpringBoot plugin is > > available from the Update Center. > > > > I went on the new plugin portal and realized that the last version was > not > > verified while the older was but I don't seem to find a way to request > > verification of the last version. > > I went to MyPlugins section, clicked on edit button for NBSpringBoot > > plugin then on edit button for last version, it shows the plugin enabled > > for NB 11.0 and 12.0 but no way to request verification, if I recall > > correctly there were buttons to request verification against selected NB > > versions. > > > > Could someone shed some light on this? > > > > Thank you in advance for your help. > > > > Regards > > *--* > > *Alessandro Falappa* > > >
Re: Plugin verification
Hi all, is this the right mailing list to discuss plugin portal issues? Regards, *--* *Alessandro Falappa* Il giorno dom 29 nov 2020 alle ore 13:16 Alessandro ha scritto: > Hi all, > while testing the recently released NetBeans 12.2 Linux installer I > noticed that in NB12.2 the older version of my NBSpringBoot plugin is > available from the Update Center. > > I went on the new plugin portal and realized that the last version was not > verified while the older was but I don't seem to find a way to request > verification of the last version. > I went to MyPlugins section, clicked on edit button for NBSpringBoot > plugin then on edit button for last version, it shows the plugin enabled > for NB 11.0 and 12.0 but no way to request verification, if I recall > correctly there were buttons to request verification against selected NB > versions. > > Could someone shed some light on this? > > Thank you in advance for your help. > > Regards > *--* > *Alessandro Falappa* >
Plugin verification
Hi all, while testing the recently released NetBeans 12.2 Linux installer I noticed that in NB12.2 the older version of my NBSpringBoot plugin is available from the Update Center. I went on the new plugin portal and realized that the last version was not verified while the older was but I don't seem to find a way to request verification of the last version. I went to MyPlugins section, clicked on edit button for NBSpringBoot plugin then on edit button for last version, it shows the plugin enabled for NB 11.0 and 12.0 but no way to request verification, if I recall correctly there were buttons to request verification against selected NB versions. Could someone shed some light on this? Thank you in advance for your help. Regards *--* *Alessandro Falappa*
