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

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


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

     [ http://jira.codehaus.org/browse/MEVENIDE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint updated MEVENIDE-651:
----------------------------------

    Fix Version/s: NB_3.2

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.

> 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

    [ http://jira.codehaus.org/browse/MEVENIDE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142353#action_142353 ]

Magne Nordtveit commented on MEVENIDE-651:
------------------------------------------

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.

> 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

    [ http://jira.codehaus.org/browse/MEVENIDE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156557#action_156557 ]

Jaromir Uhrik commented on MEVENIDE-651:
----------------------------------------

This bug was transferred to the NetBeans Issuezilla bug tracking system as http://www.netbeans.org/issues/show_bug.cgi?id=154506

> 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

     [ 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