[jbosstools-issues] [JBoss JIRA] (JBIDE-12529) Use refactoring API to delete converted dependencies
Snjezana Peco (JIRA)
jira-events at lists.jboss.org
Wed Oct 3 16:00:04 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723803#comment-12723803 ]
Snjezana Peco commented on JBIDE-12529:
---------------------------------------
The MavenPropertiesIdentifier.identify method opens a zip file, but doesn't close it.
Attached is a patch.
> 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, jbide-12529.diff
>
>
> 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
More information about the jbosstools-issues
mailing list