[jbosstools-issues] [JBoss JIRA] (JBIDE-12529) Use refactoring API to delete converted dependencies

[Fred Bricon (JIRA)]

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

Fred Bricon updated JBIDE-12529:
--------------------------------

    Attachment: convert-me-to-maven.zip


Test project failing containing references to embedded jars.

For some reason, the refactoring doesn't manage to properly delete the jars after conversion (on windows).

- unzip !convert-me-to-maven.zip!
- import convert-me as existing project
- Configure > Convert to maven project
- select default GAV coordinates
- on the references identification page, make sure the delete button is checked
- click finish : referenced file can not be deleted.


If you delete a jar manually from the lib/ folder, the same refactoring wizard is displayed but this time it actually works!
                
> Use refactoring API to delete converted dependencies
> ----------------------------------------------------
>
>                 Key: JBIDE-12529
>                 URL: https://issues.jboss.org/browse/JBIDE-12529
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: maven
>    Affects Versions: 4.0.0.Alpha1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>              Labels: maven_conversion
>             Fix For: 4.0.0.Beta1
>
>         Attachments: convert-me-to-maven.zip
>
>
> As a follow up on JBIDE-12527 and JBIDE-8973, we should be able to also delete all the jars from the project that have been converted to maven dependencies. A simple file.delete() doesn't work currently has the files are locked (on windows at least). 
> When manually deleting jars that are referenced in the classpath, eclipse (jdt) displays a refactoring dialog and the file deletion is working. We should take a look at how that approach is working

--
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