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 154506

Summary: [codehaus] Update mainClass in jar-plugin configuration if present when selecting main class in UI
Product: projects Reporter: Jaromir Uhrik <juhrik>
Component: MavenAssignee: Tomas Stupka <tstupka>
Status: RESOLVED WONTFIX    
Severity: blocker    
Priority: P4    
Version: 6.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description Jaromir Uhrik 2008-12-03 16:26:44 UTC 
This issue was originally reported by Magne Nordtveit in 18/Jul/08 at codehaus.org - see more details at
http://jira.codehaus.org/browse/MEVENIDE-651

===========
Description:
===========
When updating the mainClass in the UI, the UI should check the pom file and check if a mainClass is defined in a
jar-plugin configuration and update it if it is specified. It should however not update if it mainClass is in a profile.

----------------------------------------------
Comment by Milos Kleint [ 18/Jul/08 03:47 AM ]
----------------------------------------------
what do you mean by "It should however not update if it mainClass is in a profile."?
That's why the automated editing of pom.xml is so hard. Stuff can be at many different places and it depends on the
final resolution what gets actually used.

-------------------------------------------------
Comment by Magne Nordtveit [ 18/Jul/08 06:08 AM ]
-------------------------------------------------
What i ment was that the UI should just update the mainClass argument if, and only if, it already exists in the POM's
<build/> definition.
It should in my opinion not look in the <profiles/> as that might be used to activate different builds with different
main classes.
Comment 1 Milos Kleint 2009-08-03 10:18:47 UTC 
*** Issue 169714 has been marked as a duplicate of this issue. ***
Comment 2 Antonin Nebuzelsky 2010-07-30 15:17:05 UTC 
Reassigning to default owner.
Comment 3 Martin Balin 2016-07-07 08:38:16 UTC 
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss