You need to log in before you can comment on or make changes to this bug.
Steps to reproduce: 1. Create/open a project with "jar" packaging. 2. Select "Profile" action on that project 3. Choose "Part of application", click "define" and "Add From Project..." The result is the following exception: ava.lang.IllegalArgumentException: setSelectedIndex: 0 out of bounds at javax.swing.JComboBox.setSelectedIndex(JComboBox.java:601) at org.netbeans.modules.profiler.ui.panels.ProjectSelectRootMethodsPanel.refreshBuilderList(ProjectSelectRootMethodsPanel.java:361) at org.netbeans.modules.profiler.ui.panels.ProjectSelectRootMethodsPanel.access$000(ProjectSelectRootMethodsPanel.java:90) at org.netbeans.modules.profiler.ui.panels.ProjectSelectRootMethodsPanel$1.propertyChange(ProjectSelectRootMethodsPanel.java:154) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:347) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) at java.awt.Component.firePropertyChange(Component.java:7961) at org.netbeans.modules.profiler.selector.ui.RootSelectorTree.setContext(RootSelectorTree.java:123) at org.netbeans.modules.profiler.ui.panels.ProjectSelectRootMethodsPanel$2.run(ProjectSelectRootMethodsPanel.java:164) at org.netbeans.modules.profiler.ui.panels.ProjectSelectRootMethodsPanel.updateSelector(ProjectSelectRootMethodsPanel.java:383) at org.netbeans.modules.profiler.ui.panels.ProjectSelectRootMethodsPanel.getRootMethods(ProjectSelectRootMethodsPanel.java:161) at org.netbeans.modules.profiler.ui.panels.RootMethodsPanel$1.run(RootMethodsPanel.java:153) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:573) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1005)
Resolving this issue required a bit bigger overhaul of the profiling support infrastructure. Originally, the root methods, marker methods and categorization relied on the fact that there was one project type per application type (read - j2se, web app, ejb, ear, etc.). This is not true for maven based projects. There is only one project type (maven) and the application type is derived from the maven packaging. Fixed in http://hg.netbeans.org/profiler-main/rev/f9564966572e
Integrated into 'main-golden', will be available in build *200902131548* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/f9564966572e User: Jaroslav Bachorik <yardus@netbeans.org> Log: #158395 - adjusting the profiling support infrastructure to the fact that instead of various project types there is only one project type for maven - but exposing different functionality depending on the packaging type
marking verified
