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

[Fred Bricon (JIRA)]

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

Fred Bricon resolved JBIDE-8973.
--------------------------------

    Release Notes Text: 
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.
            Resolution: Done


Initial implementation is made available for JBT 4.0.0.Alpha1. Further improvements will be treated as separate JIRAs : 

- JBIDE-12527 Improve maven conversion of lib jars	   
- JBIDE-12528 Create standalone wizard for conversion to maven dependencies	   
- JBIDE-12529 Use refactoring API to delete converted dependencies
                
> Provide a way to convert pure java libs into maven provided dependencies
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-8973
>                 URL: https://issues.jboss.org/browse/JBIDE-8973
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: maven
>    Affects Versions: 3.3.0.M1
>            Reporter: Max Rydahl Andersen
>            Assignee: Fred Bricon
>              Labels: maven_conversion, new_and_noteworthy
>             Fix For: 4.0.0.Alpha1
>
>         Attachments: identify_dependencies.png
>
>
> Execute: right click on a non-maven project, and choose "Configure > Convert to Maven"
> Assert: UI is shown that shows which jars misses metadata and what can be automatically converted to maven dependencies. UI has options to change the dependency details and exclude some of them from the conversion.
> Execute: Press Ok
> Assert: The selected dependencies are added to the generated pom.xml.

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