[jbosstools-issues] [JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS, JBT default install; add new connector to Central

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-19645:
---------------------------------------------

[~akazakov] how many features do we have in this seam3 using "old" seam3 packages/syntax now ? and how many of the seam3 features do we/do we not support in new deltaspike format ?

Just to have it outlined/documented.

And this plugin purely provides the hooks/backbone for seam3 cdi extensions, right ? no wizards, no UI etc. all just nice and transparent only activated when actually used in the project, no performance impact etc. and all unit tested so if we break stuff it would show up, correct ?

I'm mostly +1 for keeping it too - seems cheaper adn simpler.

> Remove seam 3 features from JBDS, JBT default install; add new connector to Central
> -----------------------------------------------------------------------------------
>
>                 Key: JBIDE-19645
>                 URL: https://issues.jboss.org/browse/JBIDE-19645
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, seam2, updatesite
>    Affects Versions: 4.3.0.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Alexey Kazakov
>             Fix For: 4.3.0.Beta1
>
>
> Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2:
> * remove from CoreTools categories on update sites
> * remove from JBDS core.feature
> * create new connectors in JBT and JBDS Central
> [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)