[jbosstools-issues] [JBoss JIRA] (JBIDE-12551) Reset button in Convert to maven dependencies wizard is behaving weird

[Isaac Rooskov (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-12551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Isaac Rooskov updated JBIDE-12551:
----------------------------------

    Release Notes Docs Status: Documented as Resolved Issue
                       Writer: irooskov
           Release Notes Text: When pressing the Reset button within the Convert to maven dependencies wizard, the dependencies lookup was still not reset. The issue has been correct by replacing the Reset button with a Identify Dependencies button. Through this new button a user can relaunch dependency identification after updating the Maven repositories list within settings.xml, or enabling new remote nexus repositories.

    
> Reset button in Convert to maven dependencies wizard is behaving weird
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-12551
>                 URL: https://issues.jboss.org/browse/JBIDE-12551
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 4.0.0.Alpha1
>            Reporter: Rastislav Wagner
>            Assignee: Fred Bricon
>              Labels: maven_conversion, new_and_noteworthy
>             Fix For: 4.0.0.Beta1
>
>         Attachments: relaunch_dependency_identification.png
>
>
> If I press Reset button in Convert to maven dependencies wizard during dependencies lookup then the status of already found dependencies is reset to "Unidentified dependency" and wizard continues in lookup but it wont bother with "reseted" dependencies anymore.
> Another case: When lookup ends and then I press Reset button, status of all dependencies is changet to "Unidentified dependency" and lookup is not restarted. Then no dependencies are added to pom.xml
> I would expect that pressing Reset button resets dependencies lookup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira