[mevenide-dev] [jira] Closed: (MEVENIDE-651) Update mainClass in jar-plugin configuration if present when selecting main class in UI

"Milos Kleint (JIRA)" <jira-yCVjj/[email protected]> Wed, 3 Dec 2008 11:49:23 -0600 (CST)
Newsgroups gmane.comp.jakarta.turbine.maven.mevenide.devel
Message-ID <6188351.1228326563048.JavaMail.haus-jira@codehaus01.managed.contegix.com>
     [ http://jira.codehaus.org/browse/MEVENIDE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint closed MEVENIDE-651.
---------------------------------

    Resolution: Duplicate

closing the issue as duplicate of the newly created one in netbeans.org issuezilla. 
Please post your additional comments to the new issue.

> Update mainClass in jar-plugin configuration if present when selecting main class in UI
> ---------------------------------------------------------------------------------------
>
>                 Key: MEVENIDE-651
>                 URL: http://jira.codehaus.org/browse/MEVENIDE-651
>             Project: mevenide
>          Issue Type: Improvement
>          Components: mevenide2-netbeans
>    Affects Versions: NB_3.1
>            Reporter: Magne Nordtveit
>            Assignee: Milos Kleint
>            Priority: Minor
>             Fix For: NB_3.2
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email