This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
We get many identical api change e-mails at api-changes@netbeans.org Can someone please stop this flood?
I'm also not interested in spam like this: From: SYMPA <sympa@netbeans.org> To: mentlicher@netbeans.org Subject: Message distribution : Authorization denied Your message for list 'nb-re@netbeans.org' (attached below) was rejected. You are not allowed to send this message for the following reason : you are not allowed to perform this action. For further information, please contact nb-re-request@netbeans.org
The "flood" is not nice, but it is a result of the fact that nbms-and-javadoc build is not stable (actually is failing) - e.g. the comparision is done against older version of the API. So the change is reported again and again and again. The right fix is to make sure nbms-and-javadoc passes OK.
Issue #248073 submitted. IMHO the right fix would be not to have the e-mails distribution sensitive on build failures, since this situation can reappear at any time in the future again.
And PLEASE do not send e-mails from *my* mailing address to nb-re@netbeans.org when I'm not allowed to post there! I'm really not interested in spamming like this: Your message for list 'nb-re@netbeans.org' (attached below) was rejected. You are not allowed to send this message for the following reason : you are not allowed to perform this action. For further information, please contact nb-re-request@netbeans.org
(In reply to Martin Entlicher from comment #3) > Issue #248073 submitted. > IMHO the right fix would be not to have the e-mails distribution sensitive > on build failures, since this situation can reappear at any time in the > future again. Sounds like a "chicken and egg" problem. The email distribution is part of the build. If something goes wrong with the build after the email is sent, it is hard to cancel it. We don't have transactional builds. As far as I can say from http://deadlock.netbeans.org/job/nbms-and-javadoc/2252/console the build really fails in the last possible moment, trying to sent notification to com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 <David>... User unknown com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 <Strupl>... User unknown com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 <Strupl>... User unknown I don't know why!? The "notify people who broke the build" option is disabled. Anyway I at least unchecked all email notifications about broken builds I see in the configuration. It might be enough.
Martin, are you still facing the same problem ?
The described situation probably did not occur since then, so no, we do not get many duplicated API change e-mails currently. The fix would probably not be easy as Jarda pointed out.
> I at least unchecked all email notifications about broken > builds I see in the configuration. It might be enough. So closing for now. Martin, please reopen if you'll still feel like more needs to be done.