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.
In a module suite's nbproject/project.properties file there is run.args.extra= -J-Dcom.raelity.jvi.motd=file:///c:/a/src/jvi-docs/htdocs/motd and in a module there is String s = System.getProperty("com.raelity.jvi.motd"); The variable 's' is always null when I debug NB from NB. I'm working on windows. Target Platform is default and using harness supplied with IDE. I tried putting a breakpoint on the debug target in the ant script suite.xml but had no success in getting the breakpoint, probably cockpit error.
(got the ant debug to work which indirectly contributed to getting a workaround) If I run the "debug" target from the context menu over suite>ImportantFiles>BuildScript then it works ok, as opposed to using the toolbar button "Debug Main Project". It looks like run.args.extra is getting usurped in the failing case With debug ant output, when the toolbar-button is used I see: Setting ro project property: run.args.extra -> --test-userdir-lock-with-invalid-arg and later Loading C:\a\src\jvi-dev\nbvi\nbvi-suite\nbproject\private\private.properties Override ignored for property "run.args.extra"
core-main #de6e08356e17, note that you need to use newer harness as well, not only IDE.
> note that you need to use newer harness as well, not only IDE. I don't understand that. Assuming referring to NetBeansPlatformManager>Harness. Could you clarify the meaining in relationship to the dialog settings. There are options o with IDE o with Platform o other: (defaults to .../NetBeans 6.7/harness) selected harness version: 6.7 In my case I had setup "Target Platform is default and using harness supplied with IDE." Would this have a problem? (If refer to harness/README, could you give me hint on what to look for :) )
> I don't understand that. Assuming referring to NetBeansPlatformManager>Harness. Yes, that's the most common method how to specify harness for project - indirectly via platform. Other option is to set harness.dir property directly in platform.properties in the project. > In my case I had setup "Target Platform is default and using harness supplied with IDE." Would this have a problem? That is the option that works out-of-the-box. It means you are using harness bundled with IDE, thus you'll get newer version of both IDE and harness. The note was primarily for those using harness bundled with platform being built against, since it is usually older than the IDE.
Issue is resolved with comment "core-main #de6e08356e17". How to find out what the change is, files and diff. From "http://hg.netbeans.org/core-main/" I don't see how to get there, entering de6e08356e17 in the search box takes a long time to do nothing. I tried http://hg.netbeans.org/core-main/rev/de6e08356e17 and that gives > An error occurred while processing your request > > 00manifest.i@de6e08356e17: no match found
I think Richard just hasn't pushed the fix yet.
Yep, I forgot to push immediately (it was Friday evening, you know :)), did it now. Otherwise you can just wait for automated comment from qa, see http://wiki.netbeans.org/HgParallelTeamIntegrationBestPractices#section-HgParallelTeamIntegrationBestPractices-IssueTracking
OK, as you said "newer harness ... not only IDE", can't just fix it with a new harness. For now I'll modify the harness and introduce property "run.args.ernie" and use that (I keep starting the IDE with the button and then have to restart from the build script, too much time). Could your fix for this be a candidate for a future patch?
Integrated into 'main-golden', will be available in build *200907150249* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/de6e08356e17 User: Richard Michalsky <rmichalsky@netbeans.org> Log: #168126: run.args.extra should not be used by IDE, reserved for user args.