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.

Bug 239309 - Needs to define netbeans.run.params.ide after update to 7.4 patch1
Summary: Needs to define netbeans.run.params.ide after update to 7.4 patch1
Status: RESOLVED DUPLICATE of bug 238819
Alias: None
Product: apisupport
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-10 12:09 UTC by arittner
Modified: 2013-12-10 12:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Message screenshot (26.54 KB, image/png)
2013-12-10 12:09 UTC, arittner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description arittner 2013-12-10 12:09:41 UTC
Created attachment 143008 [details]
Message screenshot

I've updated my IDE to:

Product Version: NetBeans IDE 7.4 (Build 201310111528)
Updates: NetBeans IDE is updated to version NetBeans 7.4 Patch 1
Java: 1.8.0-ea; Java HotSpot(TM) 64-Bit Server VM 25.0-b60
Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b118
System: Windows 7 version 6.1 running on amd64; Cp1252; de_DE (nb)
User directory: C:\Users\arittner\AppData\Roaming\NetBeans\7.4
Cache directory: C:\Users\arittner\AppData\Local\NetBeans\Cache\7.4

But now, I can't debug my application. 

My pom.xml contains this section:

    <properties>
        <all.clusters>${project.build.directory}/${brandingToken}</all.clusters>
        <netbeans.run.params.ide/>
        <netbeans.run.params>${netbeans.run.params.ide}</netbeans.run.params>
    </properties>


but I get any time on "debug" the message to add "netbeans.run.params.ide". If I remove the property, the dialog adds the property, but the application doesn't start. Build and run works, but not debug.

Attached a screenshot from the dialog message. No corresponding message.log entries.
Comment 1 Milos Kleint 2013-12-10 12:26:07 UTC
duplicate of issue 238819, will appear in patch2 soon

*** This bug has been marked as a duplicate of bug 238819 ***