It doesn't look like that's what's happening. The debug action's properties
are set as:
jpda.listen=true
netbeans.run.params=-J-Xdebug
-J-Xrunjdwp:transport=dt_socket,suspend=n,server=n,address=${jpda.address}
Anyway, after seeing that RunPlatformAppMojo takes the value of
${netbeans.run.params}, I tried this, which worked just fine:
<additionalArguments>${netbeans.run.params} -J-Drepl.start=Y
-J-Dwarm.up.pdfxs=N</additionalArguments>
Not ideal, but got the job done. I'll file that issue.
Thanks,
- Chas
Milos Kleint-2 wrote:
>
> check the IDE's definition of the debug action. I think it will probably
> use
> an expression property that sets AdditionalArguments. However these
> expression props don't work when the parameter is set in the pom. It could
> be considered a bug, but there's no clear solution unfortunately. surefire
> plugin created a special "debugParams" parameter, might be handled by a
> special property within the IDE or maven could change teh order of
> preference.
> An immediate solution for you is to set your properties into the action
> definition and not in the pom, if possible.
>
> Probably should be tracked, so if you can file it into the NetBeans issue
> tracking, it would be great. Thanks.
>
> Milos
>
>
>
> On Tue, Dec 29, 2009 at 4:57 PM, cemerick <[email protected]> wrote:
>
>>
>> When I define any <additionalArguments> in the <configuration> for
>> nbm-maven-plugin, any debug parameters provided to mvn are not passed on
>> to
>> the NB application. From the log of an RCP app starting from a debug
>> action
>> in the IDE:
>>
>> NetBeans: Executing '/Users/chas/dev/mvn/bin/mvn -Djpda.listen=true
>> -Djpda.address=61488 -Dnetbeans.run.params=-J-Xdebug
>> -J-Xrunjdwp:transport=dt_socket,suspend=n,server=n,address=61488
>> -Dnetbeans.execution=true install nbm:run-platform'
>> ...
>> ...
>> ...
>> [nbm:run]
>> Executing: /bin/sh -c
>> /Users/chas/dev/Sift/application/target/sift/bin/sift
>> -J-Dnetbeans.logger.console=true -J-ea --branding sift -J-Drepl.start=Y
>> -J-Dwarm.up.pdfxs=N
>>
>> Those last two args are what I define in <additionalArguments>; when I
>> remove them, the debug parameters are properly passed on in the nbm:run
>> execution. I presume that the <additionalArguments> should be added to
>> the
>> argument list (including debug params), and not replace what is being
>> defined otherwise.
>>
>> Seems like a bug?
>>
>> - Chas
>> --
>> View this message in context:
>> http://old.nabble.com/nbm-maven-plugin%3A-debug-breaks-when-%3CadditionalArguments%3E-is-specified-tp26956244p26956244.html
>> Sent from the mojo - user mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/nbm-maven-plugin%3A-debug-breaks-when-%3CadditionalArguments%3E-is-specified-tp26956244p27011318.html
Sent from the mojo - user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
