8:11 a.m.
Fred Bricon created JBIDE-12529:
-----------------------------------
Summary: 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
Fix For: 4.0.0.Alpha2
As a follow up on JBIDE-12527 and JBIDE-8973, we should be able to also convert any jar in
the project explorer to maven dependencies.
Use case : select multiple lib dependencies, then right click and choose "Convert to
Maven dependencies...".
The "Convert to Maven dependencies..." wizard is shown with a 2nd page
displaying a preview of the selected maven dependencies with a copy to clipoard button. If
the containing project is a maven project, an "update pom.xml" button will also
be displayed.
--
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
8:16 a.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-12529:
--------------------------------
Description:
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
was:
As a follow up on JBIDE-12527 and JBIDE-8973, we should be able to also convert any jar in
the project explorer to maven dependencies.
Use case : select multiple lib dependencies, then right click and choose "Convert to
Maven dependencies...".
The "Convert to Maven dependencies..." wizard is shown with a 2nd page
displaying a preview of the selected maven dependencies with a copy to clipoard button. If
the containing project is a maven project, an "update pom.xml" button will also
be displayed.
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.Alpha2
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
--
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
8:16 a.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-12529:
--------------------------------
Description:
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
was:
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
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.Alpha2
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
8:35 a.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-12529:
--------------------------------
Fix Version/s: 4.0.0.Beta1
(was: 4.0.0.Alpha2)
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
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
10:23 a.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
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
10:23 a.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
Fred Bricon edited comment on JBIDE-12529 at 10/3/12 11:22 AM:
---------------------------------------------------------------
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!
was (Author: fbricon):
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
3 p.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
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
3 p.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
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
3 p.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
Snjezana Peco updated JBIDE-12529:
----------------------------------
Attachment: jbide-12529.diff
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
1:09 a.m.
[
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
9:54 a.m.
[
https://issues.jboss.org/browse/JBIDE-12529?page=com.atlassian.jira.plugi...
]
Rastislav Wagner closed JBIDE-12529.
------------------------------------
verified in JBT 4.0.0.CR1a 2012-11-25_07-06-54-B97
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
4212
days inactive
4299
days old
jbosstools-issues@lists.jboss.org
10 comments
3 participants
participants (3)
-
Fred Bricon (JIRA) -
Rastislav Wagner (JIRA)
-
Snjezana Peco (JIRA)