9:25 a.m.
Greetings -
A proposal to change the JBTIS target platform is described here:
https://issues.jboss.org/browse/JBTIS-382
PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/280
Synopsis:
1. Split the JBTIS target platform along release/final and non-release/early access
lines
so as to not expose non .Final features to the stable capture that appears when
performing
an 'uncategorized' install. No dependent component version change from
4.2.0.Final.
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
Please respond by COB on Thursday, Jan 29 to the specified Jira if there are any
issues.
Thanks,
--paull
9:32 a.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
I think the better solution is to remove product bits from the TP and have them included
directly through the site/p2 repo. Splitting up the TP is likely to cause issues down,
especially as versions change. Also, I assume this is for product bits and not community
bits (i.e. JBDS-IS vs JBTIS).
----- Original Message -----
Greetings -
A proposal to change the JBTIS target platform is described here:
https://issues.jboss.org/browse/JBTIS-382
PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/280
Synopsis:
1. Split the JBTIS target platform along release/final and
non-release/early access lines
so as to not expose non .Final features to the stable capture that
appears when performing
an 'uncategorized' install. No dependent component version change from
4.2.0.Final.
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
Please respond by COB on Thursday, Jan 29 to the specified Jira if there
are any issues.
Thanks,
--paull
_______________________________________________
Soa-tools-list mailing list
Soa-tools-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/soa-tools-list
9:51 a.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
Hey Rob,
I'd love to remove product bits from the TP but that hasn't happened. Having
a release based JBTIS TP that is guaranteed to have only .Final components and
then having an early-access TP seems to give component developers the option of
adding non fully released dependencies that are not our own product bits while
their component is still in Beta.
The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers could use either
with 4.2.1.EA being the full set of dependencies.
We can revisit removing the JBoss product bits from the TP but for the JDV release
this change removes uncategorized non .Final bits that's needed now.
--paull
----- Original Message -----
From: "Rob Cernich" <rcernich(a)redhat.com>
To: "Paul Leacu" <pleacu(a)redhat.com>
Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
<soa-tools-list(a)redhat.com>, "jbosstools-dev jbosstools-dev"
<jbosstools-dev(a)lists.jboss.org>
Sent: Wednesday, January 28, 2015 9:32:26 AM
Subject: Re: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/
4.2.1.EA
I think the better solution is to remove product bits from the TP and have
them included directly through the site/p2 repo. Splitting up the TP is
likely to cause issues down, especially as versions change. Also, I assume
this is for product bits and not community bits (i.e. JBDS-IS vs JBTIS).
----- Original Message -----
>
> Greetings -
> A proposal to change the JBTIS target platform is described here:
>
> https://issues.jboss.org/browse/JBTIS-382
>
> PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/280
>
> Synopsis:
>
> 1. Split the JBTIS target platform along release/final and
> non-release/early access lines
> so as to not expose non .Final features to the stable capture that
> appears when performing
> an 'uncategorized' install. No dependent component version change
> from
> 4.2.0.Final.
>
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
>
> Please respond by COB on Thursday, Jan 29 to the specified Jira if there
> are any issues.
>
> Thanks,
> --paull
>
> _______________________________________________
> Soa-tools-list mailing list
> Soa-tools-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/soa-tools-list
>
10:25 a.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
i'm a bit confused what is it you consider product bits in the TP here ?
I'm not seeing any in here - am I missing something ?
I believe this change is done to ensure we don't leak in bad
dependencies between
the earlyaccess site that exists in both community and product shipment.
/max
Hey Rob,
I'd love to remove product bits from the TP but that hasn't happened.
Having
a release based JBTIS TP that is guaranteed to have only .Final
components and
then having an early-access TP seems to give component developers the
option of
adding non fully released dependencies that are not our own product
bits while
their component is still in Beta.
The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers
could use either
with 4.2.1.EA being the full set of dependencies.
We can revisit removing the JBoss product bits from the TP but for the
JDV release
this change removes uncategorized non .Final bits that's needed now.
--paull
----- Original Message -----
> From: "Rob Cernich" <rcernich(a)redhat.com>
> To: "Paul Leacu" <pleacu(a)redhat.com>
> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
> <soa-tools-list(a)redhat.com>, "jbosstools-dev jbosstools-dev"
> <jbosstools-dev(a)lists.jboss.org>
> Sent: Wednesday, January 28, 2015 9:32:26 AM
> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
> platform - 4.2.1.Final/ 4.2.1.EA
>
> I think the better solution is to remove product bits from the TP and
> have
> them included directly through the site/p2 repo. Splitting up the TP
> is
> likely to cause issues down, especially as versions change. Also, I
> assume
> this is for product bits and not community bits (i.e. JBDS-IS vs
> JBTIS).
>
> ----- Original Message -----
>>
>> Greetings -
>> A proposal to change the JBTIS target platform is described here:
>>
>> https://issues.jboss.org/browse/JBTIS-382
>>
>> PR:
>> https://github.com/jbosstools/jbosstools-integration-stack/pull/280
>>
>> Synopsis:
>>
>> 1. Split the JBTIS target platform along release/final and
>> non-release/early access lines
>> so as to not expose non .Final features to the stable capture
>> that
>> appears when performing
>> an 'uncategorized' install. No dependent component version
>> change
>> from
>> 4.2.0.Final.
>>
>>
>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
>>
>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
>>
>> Please respond by COB on Thursday, Jan 29 to the specified Jira if
>> there
>> are any issues.
>>
>> Thanks,
>> --paull
>>
>> _______________________________________________
>> Soa-tools-list mailing list
>> Soa-tools-list(a)redhat.com
>> https://www.redhat.com/mailman/listinfo/soa-tools-list
>>
>
/max
http://about.me/maxandersen
11:04 a.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
Hey Max -
The BPMN2 Modeler and BPEL appear in both the JBTIS TP and as p2 update site
components.
Your statement below is really the principle issue:
I believe this change is done to ensure we don't leak in bad
dependencies between
the earlyaccess site that exists in both community and product shipment.
--paull
----- Original Message -----
From: "Max Rydahl Andersen" <manderse(a)redhat.com>
To: "Paul Leacu" <pleacu(a)redhat.com>
Cc: "Rob Cernich" <rcernich(a)redhat.com>, "soa-tools-list"
<soa-tools-list(a)redhat.com>, jbds-is-pm-list(a)redhat.com,
"jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Wednesday, January 28, 2015 10:25:18 AM
Subject: Re: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/
4.2.1.EA
i'm a bit confused what is it you consider product bits in the TP here ?
I'm not seeing any in here - am I missing something ?
I believe this change is done to ensure we don't leak in bad
dependencies between
the earlyaccess site that exists in both community and product shipment.
/max
> Hey Rob,
>
> I'd love to remove product bits from the TP but that hasn't happened.
> Having
> a release based JBTIS TP that is guaranteed to have only .Final
> components and
> then having an early-access TP seems to give component developers the
> option of
> adding non fully released dependencies that are not our own product
> bits while
> their component is still in Beta.
>
> The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers
> could use either
> with 4.2.1.EA being the full set of dependencies.
>
> We can revisit removing the JBoss product bits from the TP but for the
> JDV release
> this change removes uncategorized non .Final bits that's needed now.
>
> --paull
>
> ----- Original Message -----
>> From: "Rob Cernich" <rcernich(a)redhat.com>
>> To: "Paul Leacu" <pleacu(a)redhat.com>
>> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
>> <soa-tools-list(a)redhat.com>, "jbosstools-dev jbosstools-dev"
>> <jbosstools-dev(a)lists.jboss.org>
>> Sent: Wednesday, January 28, 2015 9:32:26 AM
>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
>> platform - 4.2.1.Final/ 4.2.1.EA
>>
>> I think the better solution is to remove product bits from the TP and
>> have
>> them included directly through the site/p2 repo. Splitting up the TP
>> is
>> likely to cause issues down, especially as versions change. Also, I
>> assume
>> this is for product bits and not community bits (i.e. JBDS-IS vs
>> JBTIS).
>>
>> ----- Original Message -----
>>>
>>> Greetings -
>>> A proposal to change the JBTIS target platform is described here:
>>>
>>> https://issues.jboss.org/browse/JBTIS-382
>>>
>>> PR:
>>> https://github.com/jbosstools/jbosstools-integration-stack/pull/280
>>>
>>> Synopsis:
>>>
>>> 1. Split the JBTIS target platform along release/final and
>>> non-release/early access lines
>>> so as to not expose non .Final features to the stable capture
>>> that
>>> appears when performing
>>> an 'uncategorized' install. No dependent component version
>>> change
>>> from
>>> 4.2.0.Final.
>>>
>>>
>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
>>>
>>> http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
>>>
>>> Please respond by COB on Thursday, Jan 29 to the specified Jira if
>>> there
>>> are any issues.
>>>
>>> Thanks,
>>> --paull
>>>
>>> _______________________________________________
>>> Soa-tools-list mailing list
>>> Soa-tools-list(a)redhat.com
>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
>>>
>>
/max
http://about.me/maxandersen
11:08 a.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
My preference would be to remove those from the TP and include them through the site/p2
repo directly, i.e. treat them the same way we treat our early access components. The
benefit of this approach is that if those components need to be updated, we can simply
respin JBTIS/JBDS-IS instead of respinning the TP. This would allow us to provide a more
stable TP (i.e. we don't have to update it every time a bug is fixed upstream in bpmn2
or bpel).
----- Original Message -----
Hey Max -
The BPMN2 Modeler and BPEL appear in both the JBTIS TP and as p2
update site components.
Your statement below is really the principle issue:
> I believe this change is done to ensure we don't leak in bad dependencies
> between
> the earlyaccess site that exists in both community and product shipment.
--paull
----- Original Message -----
> From: "Max Rydahl Andersen" <manderse(a)redhat.com>
> To: "Paul Leacu" <pleacu(a)redhat.com>
> Cc: "Rob Cernich" <rcernich(a)redhat.com>, "soa-tools-list"
> <soa-tools-list(a)redhat.com>, jbds-is-pm-list(a)redhat.com,
> "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
> Sent: Wednesday, January 28, 2015 10:25:18 AM
> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target platform -
> 4.2.1.Final/ 4.2.1.EA
>
> i'm a bit confused what is it you consider product bits in the TP here ?
>
> I'm not seeing any in here - am I missing something ?
>
> I believe this change is done to ensure we don't leak in bad
> dependencies between
> the earlyaccess site that exists in both community and product shipment.
>
> /max
> > Hey Rob,
> >
> > I'd love to remove product bits from the TP but that hasn't happened.
> > Having
> > a release based JBTIS TP that is guaranteed to have only .Final
> > components and
> > then having an early-access TP seems to give component developers the
> > option of
> > adding non fully released dependencies that are not our own product
> > bits while
> > their component is still in Beta.
> >
> > The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers
> > could use either
> > with 4.2.1.EA being the full set of dependencies.
> >
> > We can revisit removing the JBoss product bits from the TP but for the
> > JDV release
> > this change removes uncategorized non .Final bits that's needed now.
> >
> > --paull
> >
> > ----- Original Message -----
> >> From: "Rob Cernich" <rcernich(a)redhat.com>
> >> To: "Paul Leacu" <pleacu(a)redhat.com>
> >> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
> >> <soa-tools-list(a)redhat.com>, "jbosstools-dev
jbosstools-dev"
> >> <jbosstools-dev(a)lists.jboss.org>
> >> Sent: Wednesday, January 28, 2015 9:32:26 AM
> >> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
> >> platform - 4.2.1.Final/ 4.2.1.EA
> >>
> >> I think the better solution is to remove product bits from the TP and
> >> have
> >> them included directly through the site/p2 repo. Splitting up the TP
> >> is
> >> likely to cause issues down, especially as versions change. Also, I
> >> assume
> >> this is for product bits and not community bits (i.e. JBDS-IS vs
> >> JBTIS).
> >>
> >> ----- Original Message -----
> >>>
> >>> Greetings -
> >>> A proposal to change the JBTIS target platform is described here:
> >>>
> >>> https://issues.jboss.org/browse/JBTIS-382
> >>>
> >>> PR:
> >>> https://github.com/jbosstools/jbosstools-integration-stack/pull/280
> >>>
> >>> Synopsis:
> >>>
> >>> 1. Split the JBTIS target platform along release/final and
> >>> non-release/early access lines
> >>> so as to not expose non .Final features to the stable capture
> >>> that
> >>> appears when performing
> >>> an 'uncategorized' install. No dependent component version
> >>> change
> >>> from
> >>> 4.2.0.Final.
> >>>
> >>>
> >>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
> >>>
> >>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
> >>>
> >>> Please respond by COB on Thursday, Jan 29 to the specified Jira if
> >>> there
> >>> are any issues.
> >>>
> >>> Thanks,
> >>> --paull
> >>>
> >>> _______________________________________________
> >>> Soa-tools-list mailing list
> >>> Soa-tools-list(a)redhat.com
> >>> https://www.redhat.com/mailman/listinfo/soa-tools-list
> >>>
> >>
>
>
> /max
> http://about.me/maxandersen
>
11:21 a.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
On 28 Jan 2015, at 17:04, Paul Leacu wrote:
Hey Max -
The BPMN2 Modeler and BPEL appear in both the JBTIS TP and as p2
update site components.
okey - but both BPMN2 and BPEL is part of community release too so i'm
confused why called product only ;)
Your statement below is really the principle issue:
> I believe this change is done to ensure we don't leak in bad
> dependencies between
> the earlyaccess site that exists in both community and product
> shipment.
--paull
----- Original Message -----
> From: "Max Rydahl Andersen" <manderse(a)redhat.com>
> To: "Paul Leacu" <pleacu(a)redhat.com>
> Cc: "Rob Cernich" <rcernich(a)redhat.com>, "soa-tools-list"
> <soa-tools-list(a)redhat.com>, jbds-is-pm-list(a)redhat.com,
> "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
> Sent: Wednesday, January 28, 2015 10:25:18 AM
> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
> platform - 4.2.1.Final/ 4.2.1.EA
>
> i'm a bit confused what is it you consider product bits in the TP
> here ?
>
> I'm not seeing any in here - am I missing something ?
>
> I believe this change is done to ensure we don't leak in bad
> dependencies between
> the earlyaccess site that exists in both community and product
> shipment.
>
> /max
>> Hey Rob,
>>
>> I'd love to remove product bits from the TP but that hasn't
>> happened.
>> Having
>> a release based JBTIS TP that is guaranteed to have only .Final
>> components and
>> then having an early-access TP seems to give component developers
>> the
>> option of
>> adding non fully released dependencies that are not our own product
>> bits while
>> their component is still in Beta.
>>
>> The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers
>> could use either
>> with 4.2.1.EA being the full set of dependencies.
>>
>> We can revisit removing the JBoss product bits from the TP but for
>> the
>> JDV release
>> this change removes uncategorized non .Final bits that's needed now.
>>
>> --paull
>>
>> ----- Original Message -----
>>> From: "Rob Cernich" <rcernich(a)redhat.com>
>>> To: "Paul Leacu" <pleacu(a)redhat.com>
>>> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
>>> <soa-tools-list(a)redhat.com>, "jbosstools-dev jbosstools-dev"
>>> <jbosstools-dev(a)lists.jboss.org>
>>> Sent: Wednesday, January 28, 2015 9:32:26 AM
>>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
>>> platform - 4.2.1.Final/ 4.2.1.EA
>>>
>>> I think the better solution is to remove product bits from the TP
>>> and
>>> have
>>> them included directly through the site/p2 repo. Splitting up the
>>> TP
>>> is
>>> likely to cause issues down, especially as versions change. Also,
>>> I
>>> assume
>>> this is for product bits and not community bits (i.e. JBDS-IS vs
>>> JBTIS).
>>>
>>> ----- Original Message -----
>>>>
>>>> Greetings -
>>>> A proposal to change the JBTIS target platform is described here:
>>>>
>>>> https://issues.jboss.org/browse/JBTIS-382
>>>>
>>>> PR:
>>>> https://github.com/jbosstools/jbosstools-integration-stack/pull/280
>>>>
>>>> Synopsis:
>>>>
>>>> 1. Split the JBTIS target platform along release/final and
>>>> non-release/early access lines
>>>> so as to not expose non .Final features to the stable capture
>>>> that
>>>> appears when performing
>>>> an 'uncategorized' install. No dependent component version
>>>> change
>>>> from
>>>> 4.2.0.Final.
>>>>
>>>>
>>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
>>>>
>>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
>>>>
>>>> Please respond by COB on Thursday, Jan 29 to the specified Jira if
>>>> there
>>>> are any issues.
>>>>
>>>> Thanks,
>>>> --paull
>>>>
>>>> _______________________________________________
>>>> Soa-tools-list mailing list
>>>> Soa-tools-list(a)redhat.com
>>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
>>>>
>>>
>
>
> /max
> http://about.me/maxandersen
>
/max
http://about.me/maxandersen
12:49 p.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
Okay - I'm in complete agreement that bpel/ bpmn2 modeler should migrate out of the
JBTIS
TP but it will take time for the existing tools which rely on it (SwitchYard + ??) to
change.
So - since this is for a CR2 IS release (soon to be .Final/.GA) and a .Final/EA TP
release -
let me propose the following:
1. I create a Jira for the removal of bpel/ bpmn2 modeler from the JBTIS TP.
2. We go ahead with the JBTIS TP split as specified in JBTIS-382 so we can get CR2 to
QE for JDV.
If we find other dependent features that are pre-release we can continue with the split
TP
theme.
Agreed?
Thanks for the feedback,
--paull
----- Original Message -----
From: "Max Rydahl Andersen" <manderse(a)redhat.com>
To: "Paul Leacu" <pleacu(a)redhat.com>
Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
<soa-tools-list(a)redhat.com>, "jbosstools-dev jbosstools-dev"
<jbosstools-dev(a)lists.jboss.org>
Sent: Wednesday, January 28, 2015 11:21:28 AM
Subject: Re: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/
4.2.1.EA
On 28 Jan 2015, at 17:04, Paul Leacu wrote:
> Hey Max -
> The BPMN2 Modeler and BPEL appear in both the JBTIS TP and as p2
> update site components.
okey - but both BPMN2 and BPEL is part of community release too so i'm
confused why called product only ;)
> Your statement below is really the principle issue:
>
>> I believe this change is done to ensure we don't leak in bad
>> dependencies between
>> the earlyaccess site that exists in both community and product
>> shipment.
>
> --paull
>
>
>
> ----- Original Message -----
>> From: "Max Rydahl Andersen" <manderse(a)redhat.com>
>> To: "Paul Leacu" <pleacu(a)redhat.com>
>> Cc: "Rob Cernich" <rcernich(a)redhat.com>,
"soa-tools-list"
>> <soa-tools-list(a)redhat.com>, jbds-is-pm-list(a)redhat.com,
>> "jbosstools-dev jbosstools-dev"
<jbosstools-dev(a)lists.jboss.org>
>> Sent: Wednesday, January 28, 2015 10:25:18 AM
>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
>> platform - 4.2.1.Final/ 4.2.1.EA
>>
>> i'm a bit confused what is it you consider product bits in the TP
>> here ?
>>
>> I'm not seeing any in here - am I missing something ?
>>
>> I believe this change is done to ensure we don't leak in bad
>> dependencies between
>> the earlyaccess site that exists in both community and product
>> shipment.
>>
>> /max
>>> Hey Rob,
>>>
>>> I'd love to remove product bits from the TP but that hasn't
>>> happened.
>>> Having
>>> a release based JBTIS TP that is guaranteed to have only .Final
>>> components and
>>> then having an early-access TP seems to give component developers
>>> the
>>> option of
>>> adding non fully released dependencies that are not our own product
>>> bits while
>>> their component is still in Beta.
>>>
>>> The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers
>>> could use either
>>> with 4.2.1.EA being the full set of dependencies.
>>>
>>> We can revisit removing the JBoss product bits from the TP but for
>>> the
>>> JDV release
>>> this change removes uncategorized non .Final bits that's needed now.
>>>
>>> --paull
>>>
>>> ----- Original Message -----
>>>> From: "Rob Cernich" <rcernich(a)redhat.com>
>>>> To: "Paul Leacu" <pleacu(a)redhat.com>
>>>> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
>>>> <soa-tools-list(a)redhat.com>, "jbosstools-dev
jbosstools-dev"
>>>> <jbosstools-dev(a)lists.jboss.org>
>>>> Sent: Wednesday, January 28, 2015 9:32:26 AM
>>>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
>>>> platform - 4.2.1.Final/ 4.2.1.EA
>>>>
>>>> I think the better solution is to remove product bits from the TP
>>>> and
>>>> have
>>>> them included directly through the site/p2 repo. Splitting up the
>>>> TP
>>>> is
>>>> likely to cause issues down, especially as versions change. Also,
>>>> I
>>>> assume
>>>> this is for product bits and not community bits (i.e. JBDS-IS vs
>>>> JBTIS).
>>>>
>>>> ----- Original Message -----
>>>>>
>>>>> Greetings -
>>>>> A proposal to change the JBTIS target platform is described here:
>>>>>
>>>>> https://issues.jboss.org/browse/JBTIS-382
>>>>>
>>>>> PR:
>>>>> https://github.com/jbosstools/jbosstools-integration-stack/pull/280
>>>>>
>>>>> Synopsis:
>>>>>
>>>>> 1. Split the JBTIS target platform along release/final and
>>>>> non-release/early access lines
>>>>> so as to not expose non .Final features to the stable capture
>>>>> that
>>>>> appears when performing
>>>>> an 'uncategorized' install. No dependent component version
>>>>> change
>>>>> from
>>>>> 4.2.0.Final.
>>>>>
>>>>>
>>>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
>>>>>
>>>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
>>>>>
>>>>> Please respond by COB on Thursday, Jan 29 to the specified Jira if
>>>>> there
>>>>> are any issues.
>>>>>
>>>>> Thanks,
>>>>> --paull
>>>>>
>>>>> _______________________________________________
>>>>> Soa-tools-list mailing list
>>>>> Soa-tools-list(a)redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
>>>>>
>>>>
>>
>>
>> /max
>> http://about.me/maxandersen
>>
/max
http://about.me/maxandersen
1:24 p.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
Switchyard does not pull bpmn2 modeller from the TP, so it's removal will not affect
SwitchYard builds, FYI.
----- Original Message -----
Okay - I'm in complete agreement that bpel/ bpmn2 modeler should migrate
out of the JBTIS
TP but it will take time for the existing tools which rely on it
(SwitchYard + ??) to change.
So - since this is for a CR2 IS release (soon to be .Final/.GA) and a
.Final/EA TP release -
let me propose the following:
1. I create a Jira for the removal of bpel/ bpmn2 modeler from the JBTIS
TP.
2. We go ahead with the JBTIS TP split as specified in JBTIS-382 so we
can get CR2 to QE for JDV.
If we find other dependent features that are pre-release we can continue
with the split TP
theme.
Agreed?
Thanks for the feedback,
--paull
----- Original Message -----
> From: "Max Rydahl Andersen" <manderse(a)redhat.com>
> To: "Paul Leacu" <pleacu(a)redhat.com>
> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
> <soa-tools-list(a)redhat.com>, "jbosstools-dev jbosstools-dev"
> <jbosstools-dev(a)lists.jboss.org>
> Sent: Wednesday, January 28, 2015 11:21:28 AM
> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target platform -
> 4.2.1.Final/ 4.2.1.EA
>
> On 28 Jan 2015, at 17:04, Paul Leacu wrote:
>
> > Hey Max -
> > The BPMN2 Modeler and BPEL appear in both the JBTIS TP and as p2
> > update site components.
>
> okey - but both BPMN2 and BPEL is part of community release too so i'm
> confused why called product only ;)
>
> > Your statement below is really the principle issue:
>
> >
> >> I believe this change is done to ensure we don't leak in bad
> >> dependencies between
> >> the earlyaccess site that exists in both community and product
> >> shipment.
> >
> > --paull
> >
> >
> >
> > ----- Original Message -----
> >> From: "Max Rydahl Andersen" <manderse(a)redhat.com>
> >> To: "Paul Leacu" <pleacu(a)redhat.com>
> >> Cc: "Rob Cernich" <rcernich(a)redhat.com>,
"soa-tools-list"
> >> <soa-tools-list(a)redhat.com>, jbds-is-pm-list(a)redhat.com,
> >> "jbosstools-dev jbosstools-dev"
<jbosstools-dev(a)lists.jboss.org>
> >> Sent: Wednesday, January 28, 2015 10:25:18 AM
> >> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
> >> platform - 4.2.1.Final/ 4.2.1.EA
> >>
> >> i'm a bit confused what is it you consider product bits in the TP
> >> here ?
> >>
> >> I'm not seeing any in here - am I missing something ?
> >>
> >> I believe this change is done to ensure we don't leak in bad
> >> dependencies between
> >> the earlyaccess site that exists in both community and product
> >> shipment.
> >>
> >> /max
> >>> Hey Rob,
> >>>
> >>> I'd love to remove product bits from the TP but that hasn't
> >>> happened.
> >>> Having
> >>> a release based JBTIS TP that is guaranteed to have only .Final
> >>> components and
> >>> then having an early-access TP seems to give component developers
> >>> the
> >>> option of
> >>> adding non fully released dependencies that are not our own product
> >>> bits while
> >>> their component is still in Beta.
> >>>
> >>> The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers
> >>> could use either
> >>> with 4.2.1.EA being the full set of dependencies.
> >>>
> >>> We can revisit removing the JBoss product bits from the TP but for
> >>> the
> >>> JDV release
> >>> this change removes uncategorized non .Final bits that's needed
now.
> >>>
> >>> --paull
> >>>
> >>> ----- Original Message -----
> >>>> From: "Rob Cernich" <rcernich(a)redhat.com>
> >>>> To: "Paul Leacu" <pleacu(a)redhat.com>
> >>>> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
> >>>> <soa-tools-list(a)redhat.com>, "jbosstools-dev
jbosstools-dev"
> >>>> <jbosstools-dev(a)lists.jboss.org>
> >>>> Sent: Wednesday, January 28, 2015 9:32:26 AM
> >>>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
> >>>> platform - 4.2.1.Final/ 4.2.1.EA
> >>>>
> >>>> I think the better solution is to remove product bits from the TP
> >>>> and
> >>>> have
> >>>> them included directly through the site/p2 repo. Splitting up the
> >>>> TP
> >>>> is
> >>>> likely to cause issues down, especially as versions change. Also,
> >>>> I
> >>>> assume
> >>>> this is for product bits and not community bits (i.e. JBDS-IS vs
> >>>> JBTIS).
> >>>>
> >>>> ----- Original Message -----
> >>>>>
> >>>>> Greetings -
> >>>>> A proposal to change the JBTIS target platform is described
here:
> >>>>>
> >>>>> https://issues.jboss.org/browse/JBTIS-382
> >>>>>
> >>>>> PR:
> >>>>>
https://github.com/jbosstools/jbosstools-integration-stack/pull/280
> >>>>>
> >>>>> Synopsis:
> >>>>>
> >>>>> 1. Split the JBTIS target platform along release/final and
> >>>>> non-release/early access lines
> >>>>> so as to not expose non .Final features to the stable capture
> >>>>> that
> >>>>> appears when performing
> >>>>> an 'uncategorized' install. No dependent component
version
> >>>>> change
> >>>>> from
> >>>>> 4.2.0.Final.
> >>>>>
> >>>>>
> >>>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
> >>>>>
> >>>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
> >>>>>
> >>>>> Please respond by COB on Thursday, Jan 29 to the specified Jira
if
> >>>>> there
> >>>>> are any issues.
> >>>>>
> >>>>> Thanks,
> >>>>> --paull
> >>>>>
> >>>>> _______________________________________________
> >>>>> Soa-tools-list mailing list
> >>>>> Soa-tools-list(a)redhat.com
> >>>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
> >>>>>
> >>>>
> >>
> >>
> >> /max
> >> http://about.me/maxandersen
> >>
>
>
> /max
> http://about.me/maxandersen
>
6:44 a.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
On 28 Jan 2015, at 15:25, Paul Leacu wrote:
Greetings -
A proposal to change the JBTIS target platform is described here:
https://issues.jboss.org/browse/JBTIS-382
PR:
https://github.com/jbosstools/jbosstools-integration-stack/pull/280
Synopsis:
1. Split the JBTIS target platform along release/final and
non-release/early access lines
so as to not expose non .Final features to the stable capture that
appears when performing
an 'uncategorized' install. No dependent component version change
from 4.2.0.Final.
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
Please respond by COB on Thursday, Jan 29 to the specified Jira if
there are any issues.
I only have limited time today but I put main comments on the PR.
main "bug" is that you are using the version to differentiate where IMO
it is a *new* artifact that is being introduced, not a new new version.
Also even that was the case, 4.2.1.EA is *not* an allowed/valid version
- so I suggest using it as a separate artifact instead with shared
version since that is actually what is done here. split in Two TP's (or
updatesites) for one version.
I also believe that would remove the need for all the profiling
switching ? (but can't say that for sure since I haven't had
time to run the build to completeness)
/max
Thanks,
--paull
_______________________________________________
Soa-tools-list mailing list
Soa-tools-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/soa-tools-list
/max
http://about.me/maxandersen
3:26 a.m.
New subject: [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA
On 28 Jan 2015, at 18:49, Paul Leacu wrote:
Okay - I'm in complete agreement that bpel/ bpmn2 modeler should
migrate out of the JBTIS
TP but it will take time for the existing tools which rely on it
(SwitchYard + ??) to change.
So - since this is for a CR2 IS release (soon to be .Final/.GA) and a
.Final/EA TP release -
let me propose the following:
1. I create a Jira for the removal of bpel/ bpmn2 modeler from the
JBTIS TP.
since it seem to continue being a "problem" with bpel/bpmn2 to update
then this sounds like current best way forward.
2. We go ahead with the JBTIS TP split as specified in JBTIS-382 so
we can get CR2 to QE for JDV.
split need to happen so yes - just lets not mix up the version naming.
/max
If we find other dependent features that are pre-release we can
continue with the split TP
theme.
Agreed?
Thanks for the feedback,
--paull
----- Original Message -----
> From: "Max Rydahl Andersen" <manderse(a)redhat.com>
> To: "Paul Leacu" <pleacu(a)redhat.com>
> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
> <soa-tools-list(a)redhat.com>, "jbosstools-dev jbosstools-dev"
> <jbosstools-dev(a)lists.jboss.org>
> Sent: Wednesday, January 28, 2015 11:21:28 AM
> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
> platform - 4.2.1.Final/ 4.2.1.EA
>
> On 28 Jan 2015, at 17:04, Paul Leacu wrote:
>
>> Hey Max -
>> The BPMN2 Modeler and BPEL appear in both the JBTIS TP and as p2
>> update site components.
>
> okey - but both BPMN2 and BPEL is part of community release too so
> i'm
> confused why called product only ;)
>
>> Your statement below is really the principle issue:
>
>>
>>> I believe this change is done to ensure we don't leak in bad
>>> dependencies between
>>> the earlyaccess site that exists in both community and product
>>> shipment.
>>
>> --paull
>>
>>
>>
>> ----- Original Message -----
>>> From: "Max Rydahl Andersen" <manderse(a)redhat.com>
>>> To: "Paul Leacu" <pleacu(a)redhat.com>
>>> Cc: "Rob Cernich" <rcernich(a)redhat.com>,
"soa-tools-list"
>>> <soa-tools-list(a)redhat.com>, jbds-is-pm-list(a)redhat.com,
>>> "jbosstools-dev jbosstools-dev"
<jbosstools-dev(a)lists.jboss.org>
>>> Sent: Wednesday, January 28, 2015 10:25:18 AM
>>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
>>> platform - 4.2.1.Final/ 4.2.1.EA
>>>
>>> i'm a bit confused what is it you consider product bits in the TP
>>> here ?
>>>
>>> I'm not seeing any in here - am I missing something ?
>>>
>>> I believe this change is done to ensure we don't leak in bad
>>> dependencies between
>>> the earlyaccess site that exists in both community and product
>>> shipment.
>>>
>>> /max
>>>> Hey Rob,
>>>>
>>>> I'd love to remove product bits from the TP but that hasn't
>>>> happened.
>>>> Having
>>>> a release based JBTIS TP that is guaranteed to have only .Final
>>>> components and
>>>> then having an early-access TP seems to give component developers
>>>> the
>>>> option of
>>>> adding non fully released dependencies that are not our own
>>>> product
>>>> bits while
>>>> their component is still in Beta.
>>>>
>>>> The TPs are identical (JBTIS TP/ JBDSIS TP) - component developers
>>>> could use either
>>>> with 4.2.1.EA being the full set of dependencies.
>>>>
>>>> We can revisit removing the JBoss product bits from the TP but for
>>>> the
>>>> JDV release
>>>> this change removes uncategorized non .Final bits that's needed
>>>> now.
>>>>
>>>> --paull
>>>>
>>>> ----- Original Message -----
>>>>> From: "Rob Cernich" <rcernich(a)redhat.com>
>>>>> To: "Paul Leacu" <pleacu(a)redhat.com>
>>>>> Cc: jbds-is-pm-list(a)redhat.com, "soa-tools-list"
>>>>> <soa-tools-list(a)redhat.com>, "jbosstools-dev
jbosstools-dev"
>>>>> <jbosstools-dev(a)lists.jboss.org>
>>>>> Sent: Wednesday, January 28, 2015 9:32:26 AM
>>>>> Subject: Re: [Soa-tools-list] Proposed change for JBTIS target
>>>>> platform - 4.2.1.Final/ 4.2.1.EA
>>>>>
>>>>> I think the better solution is to remove product bits from the TP
>>>>> and
>>>>> have
>>>>> them included directly through the site/p2 repo. Splitting up
>>>>> the
>>>>> TP
>>>>> is
>>>>> likely to cause issues down, especially as versions change.
>>>>> Also,
>>>>> I
>>>>> assume
>>>>> this is for product bits and not community bits (i.e. JBDS-IS vs
>>>>> JBTIS).
>>>>>
>>>>> ----- Original Message -----
>>>>>>
>>>>>> Greetings -
>>>>>> A proposal to change the JBTIS target platform is described
>>>>>> here:
>>>>>>
>>>>>> https://issues.jboss.org/browse/JBTIS-382
>>>>>>
>>>>>> PR:
>>>>>>
https://github.com/jbosstools/jbosstools-integration-stack/pull/280
>>>>>>
>>>>>> Synopsis:
>>>>>>
>>>>>> 1. Split the JBTIS target platform along release/final and
>>>>>> non-release/early access lines
>>>>>> so as to not expose non .Final features to the stable capture
>>>>>> that
>>>>>> appears when performing
>>>>>> an 'uncategorized' install. No dependent component
version
>>>>>> change
>>>>>> from
>>>>>> 4.2.0.Final.
>>>>>>
>>>>>>
>>>>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.Fi...
>>>>>>
>>>>>>
http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.1.EA/
>>>>>>
>>>>>> Please respond by COB on Thursday, Jan 29 to the specified Jira
>>>>>> if
>>>>>> there
>>>>>> are any issues.
>>>>>>
>>>>>> Thanks,
>>>>>> --paull
>>>>>>
>>>>>> _______________________________________________
>>>>>> Soa-tools-list mailing list
>>>>>> Soa-tools-list(a)redhat.com
>>>>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
>>>>>>
>>>>>
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>
>
> /max
> http://about.me/maxandersen
>
_______________________________________________
Soa-tools-list mailing list
Soa-tools-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/soa-tools-list
/max
http://about.me/maxandersen
3369
days inactive
3374
days old
jbosstools-dev@lists.jboss.org
10 comments
3 participants
participants (3)
-
Max Rydahl Andersen -
Paul Leacu -
Rob Cernich