Most of these appear to be added or re-instated accidentally while doing the move to sub-directory work.
The exception is the platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar, which (per my understanding) should be OK, as it is, well, empty (except for the manifest, which is a plain text). I.e., there is **no** compiled code in that. Jan On Wed, Nov 21, 2018 at 12:06 PM Geertjan Wielenga <[email protected]> wrote: > But we also need to figure out how this happened in this case, since we > released the platform cluster as part of Apache NetBeans 9, presumably > these JARs were not there at that time. > > Gj > > On Wed, Nov 21, 2018 at 12:01 PM Bertrand Delacretaz < > [email protected]> > wrote: > > > Hi, > > > > On Wed, Nov 21, 2018 at 11:45 AM Geertjan Wielenga > > <[email protected]> wrote: > > > ...If anyone (mentors, for example) have a better solution, please say > > so.... > > > > I don't have a better suggestion, the release needs to be redone > > indeed - it might be useful to have a build step that checks for (at > > least) obvious unwanted binaries in the release to avoid such issues > > in the future. > > > > >... I estimate two weeks will be needed for voting from the point the > vc4 > > is created... > > > > The theoretical minimum for a podling is 2x72 hours if people are > > available to review and vote. > > > > -Bertrand > > > > --------------------------------------------------------------------- > > 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 > > > > > > > > >
