[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
Fred Bricon resolved JBIDE-12529.
---------------------------------
Resolution: Done
Fixed in trunk. Jar dependencies are now deleted if you want to, see this [screencast|
https://bitly.com/QUCyRj]
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