[jbosstools-issues] [JBoss JIRA] (JBIDE-18847) Extract discovery code out of project examples
Nick Boldt (JIRA)
issues at jboss.org
Thu Jan 15 10:52:49 EST 2015
[ https://issues.jboss.org/browse/JBIDE-18847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032826#comment-13032826 ]
Nick Boldt edited comment on JBIDE-18847 at 1/15/15 10:52 AM:
--------------------------------------------------------------
New plugin(s) need to be added to JBT and JBDS aggregates. Reopening.
1. add plugin to JBT/JBDS agg sites
2. remove new features (discovery + discovery.test)
(this includes both discovery.core and org.jboss.tools.project.examples.seam, plus any other new plugins)
was (Author: nickboldt):
New plugin(s) need to be added to JBT and JBDS aggregates. Reopening.
> Extract discovery code out of project examples
> ----------------------------------------------
>
> Key: JBIDE-18847
> URL: https://issues.jboss.org/browse/JBIDE-18847
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples
> Affects Versions: 4.2.0.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.3.0.Alpha1
>
>
> Discovery code used by central (to install software) and project-examples (to discover proxy-wizards) lives in project examples. Because of that dependency, project examples also contain API that configures central content. That forces com.jboss.devstudio.core.central to depend on project examples, just to configure central contents.
> This sucks big time and that common discovery code should be extracted to another component, consumed by both central and examples. The central configuration API should move back to central.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jbosstools-issues
mailing list