[jbosstools-issues] [JBoss JIRA] (JBIDE-12702) All groovy jars unidentified during project conversion
Fred Bricon (JIRA)
jira-events at lists.jboss.org
Tue Sep 25 05:56:34 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-12702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Bricon resolved JBIDE-12702.
---------------------------------
Resolution: Won't Fix
Not fixable given the current SHA1 checksum based search strategies.
The groovy team needs to change their release process.
> All groovy jars unidentified during project conversion
> ------------------------------------------------------
>
> Key: JBIDE-12702
> URL: https://issues.jboss.org/browse/JBIDE-12702
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.0.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: upstream
> Fix For: 4.0.x
>
>
> - Create a dynamic web project
> - Copy all jars from a groovy distro lib directory into <project>/WebContent/WEB-INF/lib
> - Right click on project > Configure > Convert to Maven...
> - Set GAV and packaging = war
> - The identification wizard tries to identify all the jars
> ASSERT : all jars are identified <- FAILS : all groovy jars are unidentified
--
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