-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add capability to profile the project and test #106
Comments
Currently it is only possible to attach the profiler manually. This is of course, isn't enough if the process won't wait for manual attach (which is usually the case for tests). Since, there is no standard way to provide jvm arguments from the command line for the started process, I'll probably need to add a task like "profileNetBeans" in the init script. |
Please take a look on what maven plugin execute when you run "Profile Test" and there is no configuration in pom. "JAVA_HOME=C:\\Program Files\\Java\\jdk1.7.0_45" cmd /c "\"\"C:\\Program Files\\NetBeans 7.4\\java\\maven\\bin\\mvn.bat\" -Dtest=com.mycompany.transactionhooksysjournal.AppTest -DforkMode=once -Dmaven.surefire.debug=${exec.args} -Dexec.args=\"-agentpath:\\\"C:/Program Files/NetBeans 7.4/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\Program Files\\NetBeans 7.4\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=\\\"C:\\HOME\\Locale Settings\\Application Data\\NetBeans\\7.4-2\\cache\\mavencachedirs\\1105333645\\org-netbeans-modules-profiler\\\" \" -DnetbeansProjectMappings= -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans 7.4\\java\\maven-nblib\\netbeans-eventspy.jar\" surefire:test\"" I think, there is not too much developers is waiting for this feature. |
I am waiting for this feature. |
👍 |
I could also really use this. |
+1 |
1 similar comment
+1 |
Any progress on this feature request? I am in need of profiling a gradle project and the only way for me to do it is to get rid of the gradle.build script and change the project into a standard NetBeans project. This requires linking all necessary jars by hand which obviously is a pain. |
I think a pull request is appreciated ;) |
If I remember correctly, I needed the pid of the started process, something I cannot access. However, I personally workaround the issue by manually connecting the profiler to the process. That is still possible, you don't need to create a new standard NB project. Though, if someone knows the NB API better than me, just point me there and I can add this feature. |
+1 (for convenience sake) |
This is to request to add a plugin capability of profiling the project and per test file.
The text was updated successfully, but these errors were encountered: