[
https://issues.jboss.org/browse/JBIDE-12528?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-12528:
--------------------------------
Description:
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 : multiple select lib dependencies, then right click and choose "Convert to
Maven dependencies..."
Assert: UI is shown that shows which jars misses metadata and what can be automatically
detected based on maven metadata in the jar. UI has option to delete jars from project.
Execute: Press Ok
was:
As a follow up on JBIDE-8973, we should be able to also convert project dependencies that
are not classpath entries.
Use case : convert an EAR project to maven. All the jars in <earproject>/lib/ and
all jars referenced as virtual components in .settings/org.eclipse.wst.common.component
should be identified and converted
Create standalone wizard for conversion to maven dependencies
-------------------------------------------------------------
Key: JBIDE-12528
URL:
https://issues.jboss.org/browse/JBIDE-12528
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 : multiple select lib dependencies, then right click and choose "Convert to
Maven dependencies..."
Assert: UI is shown that shows which jars misses metadata and what can be automatically
detected based on maven metadata in the jar. UI has option to delete jars from project.
Execute: Press Ok
--
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