I am not super familiar with Netbeans ant build system. I am presently working on building Netbeans from source without using ant. But I may be able to help some.
On Sun, 3 Dec 2017 22:06:27 +0100 Danny van Heumen <[email protected]> wrote: > Hi all, > > I am interested in seeing the progress on Netbeans. I've cloned the > (new) repo location (https://github.com/apache/incubator-netbeans.git) > and started a build using just the command "ant". It fails on some > missing "defaultManifest" file. (cli output to follow below.) I have > also tried calling "ant clean" first. It makes no difference. I've > tried repeatedly, every time on current master (i.e. origin/master > after fetch). What is your entire ant command? Are you passing properties? > [jarwithmoduleattributes] Building > jar: > /home/danny/dev/incubator-netbeans/nbbuild/netbeans/websvccommon/modules/org-netbeans-modules-websvc-saas-api.jar > [nbmerge] Failed to build target: all-websvc.saas.api > manifest: /org/apache/tools/ant/defaultManifest.mf The project/target seems unrelated to the error. The error comes from customized ant tasks within the project. This is the only file I found a reference to defaultManifest.mf. https://github.com/apache/incubator-netbeans/blob/master/nbbuild/antsrc/org/netbeans/nbbuild/LocalizedJar.java#L484 It seems to have something to do with localization and there are a couple properties mentioned in the first block of comments. As follows; "You can use the "branding" and "locale" subelements to control the branded and localized .jar files that will be produced. Also, you can set the global properties "locjar.brands" and "locjar.locales" to comma-separated lists of branding or locale identifiers so that NetBeans-based projects can brand or localize NetBeans without having to maintain modified versions of all the individual Ant scripts" No clue if your setting either of those. If you are, may try without. If you are not, may try with. You need not repeat the entire build. Just go into websvc.saas.api and invoke ant again. Though may not need a target, like all, etc. Just run it in there it will detect just that target and not others, unless dependencies. After you should be able to resume normal build. I have built pieces at time when I ran into problems with my packaging. That is what I did to build just the piece I needed. Though it did build all stuff up to that point. Hope that helps some. If nothing else at least know where the message is coming from. That should help with finding out whats going wrong. -- William L. Thomson Jr.
pgpLWmCmwfHKQ.pgp
Description: OpenPGP digital signature
