> Are NBI native binaries build manually or what? and then committed to > some repo from where they are picked up by the overall build process?
I had similar questions in PR 2563 https://github.com/apache/netbeans/pull/2563 I assume it is a manual process as follows: 1. Compile binaries 2. Upload binaries following instructions on https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115507251&src=contextnavpagetreemode 3. Update external/binaries-list 4. Add license file in external/ 5. Create pull request Is this correct? Jan Lahoda, can you provide guidance as you updated the harness launchers in the past? Additional Questions: 1. Does it matter where binaries are compiled? 2. Does ASF still have a Mac jenkins build server? https://ci.apache.org/ --Christian On Sun, Jan 3, 2021 at 2:50 AM Lars Bruun-Hansen <[email protected]> wrote: > Hi > > There are fixes for NBI native binaries which have been sitting in Git > for long time but never made it into an actual release. > > Ref: > Fix for [NETBEANS-2523], Pull Request #1844 > Fix for [NETBEANS-3094], Pull Request #1504 > > I've reopened those issues in Jira as I think "Resolved" should mean > that a fix has been *released*, not just committed. (yes, for Java > code a commit will normally guarantee that a fix finds its way - > eventually - to a release ...but this is not Java code so things are a > little bit different) > > Are NBI native binaries build manually or what? and then committed to > some repo from where they are picked up by the overall build process? > > Thx > Lars > > --------------------------------------------------------------------- > 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 > > > >
