7:05 a.m.
3rd party certification
-----------------------
Key: JBDS-1235
URL: https://jira.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Requirements
Reporter: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.0.0.GA
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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:07 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1235) 3rd party certification
[
https://jira.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin.sy...
]
Max Rydahl Andersen updated JBDS-1235:
--------------------------------------
Fix Version/s: 4.0.x
(was: 4.0.0.GA)
3rd party certification
-----------------------
Key: JBDS-1235
URL: https://jira.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Requirements
Reporter: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.0.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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:58 a.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1235) 3rd party certification
[
https://jira.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin.sy...
]
Andre Dietisheim reassigned JBDS-1235:
--------------------------------------
Assignee: Andre Dietisheim
3rd party certification
-----------------------
Key: JBDS-1235
URL: https://jira.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Requirements
Reporter: Max Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 4.0.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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1235) 3rd party certification
[
https://jira.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin.sy...
]
Andre Dietisheim updated JBDS-1235:
-----------------------------------
Assignee: (was: Andre Dietisheim)
3rd party certification
-----------------------
Key: JBDS-1235
URL: https://jira.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Requirements
Reporter: Max Andersen
Priority: Blocker
Fix For: 4.0.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.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:02 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1235) 3rd party certification
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-1235:
-----------------------------
Component/s: 3rdPartyCertification
3rdPartyDependencies
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
6:06 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1235) 3rd party certification
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1235 at 4/19/11 7:05 PM:
-----------------------------------------------------------
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}
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 -- {color:red} REMOVED PENDING LICENSE REVIEW - need to distribute
sources?{color}
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
6:06 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1235) 3rd party certification
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1235:
----------------------------------
These are the projects and components we need to certify for JBDS 4.x.
{code}
egit/0.11
findbugs/1.3.9 -- {color:red} REMOVED PENDING LICENSE REVIEW - need to distribute
sources?{color}
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
6:15 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1235) 3rd party certification
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
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
6:17 p.m.
New subject: [JBoss JIRA] Updated: (JBDS-1235) 3rd party certification for JBDS 4.x
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-1235:
-----------------------------
Summary: 3rd party certification for JBDS 4.x (was: 3rd party certification)
3rd party certification for JBDS 4.x
------------------------------------
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
8:14 a.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1235) 3rd party certification for JBDS 4.x
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Jiri Peterka reassigned JBDS-1235:
----------------------------------
Assignee: Vlado Pakan
3rd party certification for JBDS 4.x
------------------------------------
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
Assignee: Vlado Pakan
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
8:16 a.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1235) 3rd party certification for JBDS 4.x
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Jiri Peterka reassigned JBDS-1235:
----------------------------------
Assignee: Jiri Peterka (was: Vlado Pakan)
3rd party certification for JBDS 4.x
------------------------------------
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
Assignee: Jiri Peterka
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
3:14 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1235) 3rd party certification for JBDS 4.x
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Jiri Peterka updated JBDS-1235:
-------------------------------
Attachment: extras4x.png
3rd party certification for JBDS 4.x
------------------------------------
Key: JBDS-1235
URL: https://issues.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
Reporter: Max Rydahl Andersen
Assignee: Jiri Peterka
Priority: Blocker
Fix For: 4.x
Attachments: extras4x.png
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
3:18 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1235) 3rd party certification for JBDS 4.x
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Jiri Peterka updated JBDS-1235:
-------------------------------
Attachment: extras411m1.png
3rd party certification for JBDS 4.x
------------------------------------
Key: JBDS-1235
URL: https://issues.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
Reporter: Max Rydahl Andersen
Assignee: Jiri Peterka
Priority: Blocker
Fix For: 4.x
Attachments: extras411m1.png, extras4x.png
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
3:25 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1235) 3rd party certification for JBDS 4.x
[
https://issues.jboss.org/browse/JBDS-1235?page=com.atlassian.jira.plugin....
]
Jiri Peterka commented on JBDS-1235:
------------------------------------
GWT, Groovy and SoapUI was refused for 4.1, these subtasks can be closed
For others, for TCs see: https://docspace.corp.redhat.com/docs/DOC-76255
3rd party certification for JBDS 4.x
------------------------------------
Key: JBDS-1235
URL: https://issues.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
Reporter: Max Rydahl Andersen
Assignee: Jiri Peterka
Priority: Blocker
Fix For: 4.x
Attachments: extras411m1.png, extras4x.png
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
5300
days inactive
5790
days old
jbosstools-issues@lists.jboss.org
13 comments
4 participants
participants (4)
-
Andre Dietisheim (JIRA) -
Jiri Peterka (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)