[jbosstools-issues] [JBoss JIRA] (JBIDE-8973) Provide a way to convert pure java libs into maven provided dependencies

[ https://issues.jboss.org/browse/JBIDE-8973?page=com.atlassian.jira.plugin... ] Isaac Rooskov updated JBIDE-8973: --------------------------------- Release Notes Docs Status: Documented as Feature Request Writer: irooskov Release Notes Text: A new feature has been added that assists users in converting a Java project to Maven. After selecting the project's Maven coordinate, a new wizard will display that attempts to identify all the project's classpath entries and their equivalent Maven dependencies. The user can then decide on the dependencies that will be added to the generated Maven pom.xml file. Dependencies can be edited within the wizard by double-clicking on the dependency, opening a dialog page. After all changes have been made and needed dependencies are selected, a user can select to delete all classpath entries from the project, as the Maven Dependencies Library will provide all the required classpath libraries after the conversion. was: When converting a legacy Eclipse Java project to maven (right-click on project > Configure > Convert to Maven ...), after selecting the project's maven coordinate, a new wizard will pop up, trying to identify all the project's classpath entries as their equivalent Maven dependencies. The user can (de)select all the dependencies that will be added to the generated pom.xml. Double-clicking on a Maven dependency will open a dialog page to edit the dependency's details (groupId, artifactId, version, scope ...) Checking the "Delete classpath entries from project" checkbox will remove all the project classpath entries, as we expect the Maven Dependencies Library, added after the project conversion, to provide all the required classpath libraries. -- 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