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

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&gt; 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

On 10/25/2012 10:00 PM, Martin Malina wrote: > What JIRA component should we use if we log a bug for detection of > jbossas runtime? You log the bug against astools / servertools. _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

jira still has a runtime component - nothing has changed in that aspect. Thus for now, issues found in runtime-detection is to be reported in the runtime-detection component. /max On 25 Oct 2012, at 15:59, Martin Malina <mmalina(a)redhat.com&gt; wrote: > 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&gt; 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 > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On 29. 10. 2012, at 20:13, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: > oh sorry - I missed you asked for jbossas runtime detection issues specifically - then yes, first component for that would be as Rob writes elsewhere JBoss AS runtime detection. Yes, thanks. > > For anything else that doesn't fall into some other specific component related to runtime detection, use runtime-detection component. You mean SOA Runtime Detection, right? Cause there no runtime detection (no soa) anymore.

-Martin > /max > > On 29 Oct 2012, at 20:08, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: > >> jira still has a runtime component - nothing has changed in that aspect. >> >> Thus for now, issues found in runtime-detection is to be reported in the runtime-detection component. >> >> /max >> >> On 25 Oct 2012, at 15:59, Martin Malina <mmalina(a)redhat.com&gt; wrote: >> >>> 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&gt; 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 >>> >>> >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265

>>> oh sorry - I missed you asked for jbossas runtime detection issues specifically - then yes, first component for that would be as Rob writes elsewhere JBoss AS runtime detection. >> Yes, thanks. >>> >>> For anything else that doesn't fall into some other specific component related to runtime detection, use runtime-detection component. >> >> You mean SOA Runtime Detection, right? Cause there no runtime detection (no soa) anymore. > > not following what you mean ? > > There is the jbosstools-base/runtime repo and ...wtf...why do we now have a "SOA runtime detection" component? > > Did I miss something ? When was that change made ? "runtime detection" the core parts is still a separate feature/functionallity… Yes, runtime detection has been renamed to SOA runtime detection - that's why I brought this up. I thought it was Snjezana making this change since (presumably) most of the runtime detection functionality has been moved to server component. But from POV of functionality, it still is a separate feature for sure. So personally I would prefer to have it as a separate component in JIRA.

But so far it seemed that it's just a fact that from now on we should use JBossAS/server jira component to report issues for runtime detection (if it's not soa runtimes that cause the problem).

So I'm looking forward to seeing a conclusion on this topic :)

soa runtime detection component == https://github.com/jbosstools/jbosstools-runtime-soa Changed because as/seam detection migrated into AS component, which is now in Server, but the SOA Runtime Detection stuff is still on its own as a separate component (which should be one day migrated into bpel, jbpm, and esb).

N On 10/30/2012 09:23 AM, Max Rydahl Andersen wrote: > > On 30 Oct 2012, at 09:31, Martin Malina <mmalina(a)redhat.com&gt; wrote: > >> >> On 29. 10. 2012, at 20:13, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: >> >>> oh sorry - I missed you asked for jbossas runtime detection issues specifically - then yes, first component for that would be as Rob writes elsewhere JBoss AS runtime detection. >> >> Yes, thanks. >> >>> >>> For anything else that doesn't fall into some other specific component related to runtime detection, use runtime-detection component. >> >> You mean SOA Runtime Detection, right? Cause there no runtime detection (no soa) anymore. > > not following what you mean ? > > There is the jbosstools-base/runtime repo and ...wtf...why do we now have a "SOA runtime detection" component? > > Did I miss something ? When was that change made ? "runtime detection" the core parts is still a separate feature/functionallity... > > Now I get what you are asking for. > > Nick - did you change this ? with what reason ? > > /max > >> -Martin >> >>> /max >>> >>> On 29 Oct 2012, at 20:08, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: >>> >>>> jira still has a runtime component - nothing has changed in that aspect. >>>> >>>> Thus for now, issues found in runtime-detection is to be reported in the runtime-detection component. >>>> >>>> /max >>>> >>>> On 25 Oct 2012, at 15:59, Martin Malina <mmalina(a)redhat.com&gt; wrote: >>>> >>>>> 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&gt; 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 >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >> >> -- >> Martin Malina >> JBoss QA Engineer >> Red Hat Czech s.r.o. >> Purkynova 99 >> 612 45 Brno, Czech Republic >> >> Tel.: +420 532 294 265 >> >> >> >> > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com