You’re doing a build to try out any little change you make? Gj
On Mon, 9 Mar 2020 at 06:43, Korney Czukowski <[email protected]> wrote: > Mine is located at C:\Workspace\Netbeans\ > > The full build works fine for me too, and the issue I have seems to be > with the build step for the unit tests of the PHP Editor module. I think > the full build probably doesn't build the tests by default (does it?), > but I can't wait for the full build each time I want to try out any > little change I make and even if I could, I guess I wouldn't be able to > edit and build the tests :( > > > 08.03.2020 23:19, Eirik Bakke wrote: > > I build NetBeans regularly on Windows, without problems. Where are your > NetBeans sources located? Perhaps the path is too deeply nested into > folders, breaking a path name limit somewhere. > > > > (In my case, my NetBeans sources are located in a folder called > "Z:\nbsrc\incubator-netbeans", and my Java folder is at "C:\Program > Files\Java\zulu-8.0.181".) > > > > -- Eirik > > > > -----Original Message----- > > From: Korney Czukowski <[email protected]> > > Sent: Sunday, March 8, 2020 3:13 PM > > To: [email protected] > > Subject: Issues building on Windows > > > > Hi, > > > > Is there anybody else out there who still uses Windows while working on > NetBeans? I'm asking because I've hit a notorious 'java.io.IOException: > > CreateProcess error=206, The filename or extension is too long.' error > while trying to build PHP Editor module, the tests build to be more > specific. It doesn't occur with a full build and I've edited a few other > modules just as well, guess they were not large enough for this error to > appear. > > > > The command I used to build: ant -v -f php/php.editor build (or ant -v > -f php/php.editor clean build, the result is the same). Note, without -v it > just says: "common.xml:627: Error running C:\Program > Files\Java\jdk1.8.0_212\bin\javac.exe compiler" without any details [1]. > > In verbose mode it shows large lists of files for '-classpath' and > '-processorpath' arguments in compilation arguments as well as the actual > exception. > > > > I've tried to modify the build script to have it generate a jar file > with a manifest and use that in a classpath using Ant Manifestclasspath > task, but it didn't work as it's failed to generate relative paths to all > the jars in the original classpath. > > > > It would also seem like Ant Javac task can use @argfile with the > compiler to pass long command line arguments, but apparently it doesn't > happen with Nb-javac. Is there anything I can do to enable it, is there any > other workaround, or am I out of luck? > > > > Thanks. > > > > [1] > > > https://github.com/apache/netbeans/blob/master/nbbuild/templates/common.xml#L625-L631 > > > > > > > > --------------------------------------------------------------------- > > 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 > > > > > > > > > > --------------------------------------------------------------------- > > 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 > > > > > > > > > --------------------------------------------------------------------- > 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 > > > >
