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 233321 - Profiling does not start when main class is set in Maven project
Summary: Profiling does not start when main class is set in Maven project
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Ide (show other bugs)
Version: 7.4
Hardware: PC All
: P2 normal (vote)
Assignee: Petr Cyhelsky
URL:
Keywords:
: 220500 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-07-24 13:32 UTC by Jiri Skrivanek
Modified: 2013-09-21 02:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2013-07-24 13:32:12 UTC 
It is not possible to profile Maven project when main class is set in project properties. To reproduce:

- create new "Maven|Java Application" project
- right-click project node and choose Properties
- select Run category and browse for App as main class
- click OK to save options
- right-click project node and choose Profile
- click Run to start profiling but it fails

Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (default-cli) on project mavenproject4: The parameters 'executable' for goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec are missing or invalid -> [Help 1]

Product Version: NetBeans IDE Dev (Build 201307232300)
Java: 1.7.0_25; Java HotSpot(TM) 64-Bit Server VM 23.25-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_25-b15
System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
Comment 1 Tomas Hurka 2013-07-25 07:06:51 UTC 
Please evaluate.
Comment 2 Petr Cyhelsky 2013-07-25 10:29:02 UTC 
reproduced, the setting of the main class through the properties dialog also simultaneously changes VM arguments for profile project action to incorrect ones.
Comment 3 Petr Cyhelsky 2013-07-26 14:23:05 UTC 
fixed in http://hg.netbeans.org/profiler-main/rev/8706fd4eb41b
Comment 4 Quality Engineering 2013-07-27 02:18:16 UTC 
Integrated into 'main-silver', will be available in build *201307262300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/8706fd4eb41b
User: Petr Cyhelsky <cyhelsky@netbeans.org>
Log: #233321 - Do not use obsolete maven profiler integration parameters
Comment 5 Petr Cyhelsky 2013-07-31 14:26:39 UTC 
*** Bug 220500 has been marked as a duplicate of this bug. ***
Comment 6 mexer 2013-09-21 02:05:34 UTC 
Hi
I am using NB 7.4 RC1
java 8
Windows 7
In a JavaFX maven project. I'm having the same issue
Do you know when will this fix be integrated?
Comment 7 mexer 2013-09-21 02:14:10 UTC 
(In reply to mexer from comment #6)
> Hi
> I am using NB 7.4 RC1
> java 8
> Windows 7
> In a JavaFX maven project. I'm having the same issue
> Do you know when will this fix be integrated?

Im sorry, I solve the problem. I was trying to run the project without cleaning and Build  it first.
Nevertheless I  think this is an issue. When the user clicks on run the first time, the project should run without problems or telling to the user that he needs to run the build option first