[jbosstools-issues] [JBoss JIRA] (JBIDE-12583) Unify two download-runtime models in o.j.t.runtime.as.handler plugin
[
https://issues.jboss.org/browse/JBIDE-12583?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12583:
----------------------------------------
ESB stuff is no more part of JBoss Tools "core" site, it's part
"soa-tooling" site.
You can resolve dependencies to SOA-Tooling latest builds by addding the following profile
when invoking Maven: jbosstools-nightly-staging-composite-soa-tooling
So, here is an example command-line: *mvn verify -P
unified.target,jbosstools-staging-aggregate,jbosstools-nightly-staging-composite-soa-tooling*
. For further question about availability of SOA components, [~dpalmer] is the guy to
ask.
Unify two download-runtime models in o.j.t.runtime.as.handler plugin
--------------------------------------------------------------------
Key: JBIDE-12583
URL: https://issues.jboss.org/browse/JBIDE-12583
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers, runtime detection
Affects Versions: 4.0.0.Alpha2
Reporter: Rob Stryker
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
Attachments: JBIDE-12583.astools.png, JBIDE-12583.runtime.png
ASTools has an integration plugin for astools vs runtime. With runtime now living at the
bottom of the stack, this plugin may no longer be useful.
The runtime wizard dialog cannot load any runtime.ui dialogs because there is no
dependency between as.ui and runtime.ui. To add a dependency here would basically make
o.j.t.runtime.as.handler to be useless. All the code there could easily be pushed into
astools' other plugins.
This isn't a huge priority, but it is a little silly to have two models doing exactly
the same thing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira