[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBDS-1235) 3rd party certification
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Tue Apr 19 19:15:33 EDT 2011
[ https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596641#comment-12596641 ]
Nick Boldt edited comment on JBDS-1235 at 4/19/11 7:15 PM:
-----------------------------------------------------------
These are the 8 projects' versions we need to certify for JBDS 4.x.
{code}
egit/0.11
findbugs/1.3.9 -- REMOVED PENDING LICENSE REVIEW - need to distribute sources?
m2eclipse/0.12
mylyn/3.6
pmd/3.2.6
subclipse/1.6
springide/2.5.1.201011101000
testng/5.14.6.20110119_1050
{code}
was (Author: nickboldt):
These are the projects and components we need to certify for JBDS 4.x.
{code}
egit/0.11
findbugs/1.3.9 -- REMOVED PENDING LICENSE REVIEW - need to distribute sources?
m2eclipse/0.12
mylyn/3.6
pmd/3.2.6
subclipse/1.6
springide/2.5.1.201011101000
testng/5.14.6.20110119_1050
{code}
> 3rd party certification
> -----------------------
>
> Key: JBDS-1235
> URL: https://issues.jboss.org/browse/JBDS-1235
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.x
>
>
> We should define what kind of certifications we want and then certify 3rd party plugins with JBDS
> Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees.
> For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list