[jbosstools-dev] [Soa-tools-list] Proposed change for JBTIS target platform - 4.2.1.Final/ 4.2.1.EA

[Rob Cernich]

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 at redhat.com>
> > To: "Paul Leacu" <pleacu at redhat.com>
> > Cc: jbds-is-pm-list at redhat.com, "soa-tools-list"
> > <soa-tools-list at redhat.com>, "jbosstools-dev jbosstools-dev"
> > <jbosstools-dev at 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 at redhat.com>
> > >> To: "Paul Leacu" <pleacu at redhat.com>
> > >> Cc: "Rob Cernich" <rcernich at redhat.com>, "soa-tools-list"
> > >> <soa-tools-list at redhat.com>, jbds-is-pm-list at redhat.com,
> > >> "jbosstools-dev jbosstools-dev" <jbosstools-dev at 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 at redhat.com>
> > >>>> To: "Paul Leacu" <pleacu at redhat.com>
> > >>>> Cc: jbds-is-pm-list at redhat.com, "soa-tools-list"
> > >>>> <soa-tools-list at redhat.com>, "jbosstools-dev jbosstools-dev"
> > >>>> <jbosstools-dev at 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.Final/
> > >>>>>
> > >>>>> 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 at redhat.com
> > >>>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
> > >>>>>
> > >>>>
> > >>
> > >>
> > >> /max
> > >> http://about.me/maxandersen
> > >>
> > 
> > 
> > /max
> > http://about.me/maxandersen
> > 
>