[jbosstools-issues] [JBoss JIRA] (JBTIS-331) Get the integration stack into Early Access in JBoss Central

Max Rydahl Andersen (JIRA) issues at jboss.org
Thu Oct 2 05:49:02 EDT 2014


    [ https://issues.jboss.org/browse/JBTIS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007994#comment-13007994 ] 

Max Rydahl Andersen commented on JBTIS-331:
-------------------------------------------

what kind of earlyaccess are we talking here ? 

on jboss tools I assume this is just being added into jbosstools development updatesite - no special thing here (sure we can mark it as earlyaccess since it wont be there when jbosstools GA's).

But for it to be visibiel in JBoss Tools Final and from developer studio the earlyaccess content needs to goto the earlyaccess p2 repository, just changing the certificate ID does not do anything on its own.

This paragraph:
"It is not necessary to refactor (or copy) your plugin to include .earlyaccess in the name, UNLESS you plan to have one plugin for "early access" and one for "released" content, as we do in JBT/JBDS. (You can also include both types of content in the same plugin.)" sounds *very* wrong to me. Why does IS not need to have separate earlyaccess content like core do ? what makes it okey their updatesites gets automatically added ?




> Get the integration stack into Early Access in JBoss Central
> ------------------------------------------------------------
>
>                 Key: JBTIS-331
>                 URL: https://issues.jboss.org/browse/JBTIS-331
>             Project: JBoss Tools Integration Stack
>          Issue Type: Feature Request
>          Components: distribution
>    Affects Versions: 8.0.0.Alpha2
>            Reporter: Paul Leacu
>            Assignee: Paul Leacu
>
> Procedure for encorporating the IS into Early Access.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jbosstools-issues mailing list