Thanks for the explanation. But there is no jboss-base component in JIRA. I understand
that it is in the jboss-base repo in git. But those repos don't necessarily align 1-1
to JIRA components. So the question is: What JIRA component should we use if we log a bug
for detection of jbossas runtime? In the past we used the runtime detection component in
JIRA, but that is now non-existant.
-Martin
On 25. 10. 2012, at 15:53, Snjezana Peco <snjezana.peco(a)redhat.com> wrote:
Hi Martin,
The runtime-soa component includes the esb, drools and jbpm detectors.
The runtime.core/runtime.ui plugins are placed within the jbosstools-base component.
The seam detector is included in the javaee component, but the as detector in the server
component.
Snjeza
On 10/25/2012 3:39 PM, Martin Malina wrote:
> Hi Snjeza,
>
> Recently we noticed that the runtime detection component of JBIDE has been renamed to
SOA Runtime Detection [1].
>
> This is a little confusing because old JIRAs that had this component might not have
anything to do with soa. But ok, I assume you considered different solutions and found
this to be best.
>
> But anyway, I'd like make sure we understand this correctly. Is this because most
of the runtime detection code was moved under Rob's as component and this renamed
component should now be used only for what remained in the old place which is only soa
runtimes?
>
> So from now on bugs in runtime detection that are related to JbossAS or Seam runtimes
should be logged under JBossAS/Servers component?
>
> Thanks,
> Martin
>
> [1]
https://issues.jboss.org/browse/JBIDE/component/12313665
>
> --
> Martin Malina
> JBoss QA Engineer
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno, Czech Republic
>
> Tel.: +420 532 294 265
>
>
>
>
--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic
Tel.: +420 532 294 265