Re: [jbosstools-dev] [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