[jbosstools-issues] [JBoss JIRA] (JBIDE-12707) Maven workspace project dependencies are not identified during maven conversion
Fred Bricon (JIRA)
jira-events at lists.jboss.org
Tue Sep 25 05:52:34 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-12707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Bricon resolved JBIDE-12707.
---------------------------------
Resolution: Done
Fixed in trunk
> Maven workspace project dependencies are not identified during maven conversion
> -------------------------------------------------------------------------------
>
> Key: JBIDE-12707
> URL: https://issues.jboss.org/browse/JBIDE-12707
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.0.0.Beta1
>
>
> When converting a project to maven, if one of the dependencies is already a maven project opened in the workspace, it should be identified as such.
> Ex :
> - create a java project
> - create a dynamic web project
> - add the java project to the web project build path
> - convert the java project to maven
> - convert the web project to maven
> ASSERT : the java project dependency should be identified with its maven GAV
--
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
More information about the jbosstools-issues
mailing list