Re: [tcf-dev] TCF 1.0 and Juno M7

[Doug Schaefer <dschaefer@xxxxxxx>]

As I responded on the cdt-dev list, I believe TCF (tools.cdt.tcf) has
already been flagged to release on the Juno train, just as it was for
Indigo. The b3 files just need to be updated to point to a different repo
since it's no longer in the CDT repo.

Doug

On 12-05-01 5:31 PM, "Jeff Johnston" <jjohnstn@xxxxxxxxxx> wrote:

>Ok, I have gotten a response back from David Williams.  What I am
>attempting to do is wrong.
>
>I have no idea what project TCF 1.0 sits under.  If it is meant to be
>its own project, it cannot apply to be part of the Juno release this
>late in the game and add a new b3aggrcon file and I cannot ship it as
>part of the Linux Tools.
>
>If it is still part of the CDT, then perhaps the CDT can ship 1.0
>versions of the new features/plug-ins along-side the 0.4.0 versions of
>org.eclipse.tm.tcf they shipped in M6.
>
>If not, Lttng has to revert the changes before M7.
>
>-- Jeff J.
>
>On 05/01/2012 02:47 PM, Jeff Johnston wrote:
>> You are correct that Lttng isn't requiring Target Explorer, but if TCF
>> tries to create a b3aggrcon file, they will run into the issue below if
>> they expose that feature in any way.
>>
>> I guess when I just added the repository without specifying any
>> features, it tried them all.
>>
>> I modified my change to add just one feature under the added repository:
>> org.eclipse.tcf.feature.feature.group and that Validated ok. I did not
>> expose the feature in a simrel category. I sent a note to David Williams
>> to see if this was ok.
>>
>> -- Jeff J.
>>
>>
>> On 05/01/2012 02:37 PM, Patrick Tasse wrote:
>>> Hi Jeff,
>>>
>>> In LTTng we depend on org.eclipse.tcf.core and org.eclipse.tcf.rse, but
>>> we shouldn't have a dependency on Target Explorer.
>>>
>>> At one point I incorrectly thought we needed it, at that time I was
>>> getting gnu.io.rxtx from the repository http://rxtx.qbang.org/eclipse.
>>>
>>> Patrick
>>>
>>> On Tue, May 1, 2012 at 1:40 PM, Jeff Johnston <jjohnstn@xxxxxxxxxx
>>> <mailto:jjohnstn@xxxxxxxxxx>> wrote:
>>>
>>> Just a heads up. I started work on a back-up plan and added a
>>> repository to Linux Tools which is a copy of the TCF Juno nightly
>>> repo and got the following when trying to validate the Juno
>>>aggregation:
>>>
>>> Cannot complete the install because one or more required items could
>>> not be found.
>>> Missing requirement: Target Explorer 1.0.0.201205011302
>>> (org.eclipse.tcf.te.feature.__feature.group 1.0.0.201205011302)
>>> requires 'gnu.io.rxtx 0.0.0' but it could not be found
>>>
>>> -- Jeff J.
>>>
>>>
>>> On 05/01/2012 04:18 AM, Stieber, Uwe wrote:
>>>
>>> Hi Jeff,
>>>
>>> Yes, the plan is to have TCF 1.0 to participate at the Junoi
>>> release train.
>>>
>>> Martin O. : Can you update us on how we are in regards of
>>> integrating TCF into the Juno B3 aggregator model?
>>>
>>> Thanks, Uwe :)
>>>
>>>
>>> -----Original Message-----
>>> From: tcf-dev-bounces@xxxxxxxxxxx
>>> <mailto:tcf-dev-bounces@xxxxxxxxxxx>
>>> [mailto:tcf-dev-bounces@__eclipse.org
>>> <mailto:tcf-dev-bounces@xxxxxxxxxxx>] On Behalf Of Jeff Johnston
>>> Sent: Dienstag, 01. Mai 2012 01:19
>>> To: tcf-dev@xxxxxxxxxxx <mailto:tcf-dev@xxxxxxxxxxx>
>>> Subject: [tcf-dev] TCF 1.0 and Juno M7
>>>
>>> Can anyone confirm if TCF 1.0 will be part of the Juno M7
>>> milestone release?
>>>
>>> I ask because the Linux Tools project component Lttng has
>>> switched to using org.eclipse.tcf.core 1.0
>>> and nothing in the Juno aggregation file is providing it yet.
>>>
>>> -- Jeff J.
>>> _________________________________________________
>>> tcf-dev mailing list
>>> tcf-dev@xxxxxxxxxxx <mailto:tcf-dev@xxxxxxxxxxx>
>>> http://dev.eclipse.org/__mailman/listinfo/tcf-dev
>>> <http://dev.eclipse.org/mailman/listinfo/tcf-dev>
>>>
>>> _________________________________________________
>>> tcf-dev mailing list
>>> tcf-dev@xxxxxxxxxxx <mailto:tcf-dev@xxxxxxxxxxx>
>>> http://dev.eclipse.org/__mailman/listinfo/tcf-dev
>>> <http://dev.eclipse.org/mailman/listinfo/tcf-dev>
>>>
>>>
>>> _________________________________________________
>>> tcf-dev mailing list
>>> tcf-dev@xxxxxxxxxxx <mailto:tcf-dev@xxxxxxxxxxx>
>>> http://dev.eclipse.org/__mailman/listinfo/tcf-dev
>>> <http://dev.eclipse.org/mailman/listinfo/tcf-dev>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> tcf-dev mailing list
>>> tcf-dev@xxxxxxxxxxx
>>> http://dev.eclipse.org/mailman/listinfo/tcf-dev
>>
>> _______________________________________________
>> tcf-dev mailing list
>> tcf-dev@xxxxxxxxxxx
>> http://dev.eclipse.org/mailman/listinfo/tcf-dev
>
>_______________________________________________
>tcf-dev mailing list
>tcf-dev@xxxxxxxxxxx
>http://dev.eclipse.org/mailman/listinfo/tcf-dev