Hi again,
Well, looking at the “TCF CDT Extender” feature, the case is a different one here than for the TE. As this feature does pull in CDT UI as well, it is more appropriate
to keep things as they are. It needs to be possible to have an TCF feature available that does not depend on CDT … for integrators using TCF but not CDT. Exactly the reason why we have separated the features.
So, things are good as they are, probably the feature names could be better, but we can change that later too.
@Martin: All you need is a new build from the tcf-nightly Hudson build job. But as the RXTX repository went missing ….
Best regards, Uwe
J
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Stieber, Uwe
Sent: Samstag, 05. Mai 2012 09:42
To: TCF Development
Subject: Re: [tcf-dev] TCF 1.0 and Juno M7
Hi Martin,
The “TE CDT Extender” feature is a supposed to allow the separation of TE from CDT, and to allow the installation of TE without CDT. It has been based on the
hope that there is a way, some when, to have the CDT ELF parser, which is the only one I know is available in Java, separated from CDT. After all, it appears that feature is not necessary in that way. I’ve tried to install the TE TCF feature only from the
staging area, which works fine. Checking the installed plug-in’s revealed that P2 resolved the dependency to “o.e.cdt.core” without pulling in whole CDT and without manually installing the “TE CDT Extender” feature. Until there is an ELF parser, written in
Java, available from somewhere else, this is the exact minimum set of plug-in’s we require.
Here are the changes I did so far:
-
Merged the TE CDT feature with the TE feature and removed the TE CDT feature from the git tree
-
Updated the feature description in the TE TCF feature
Given the P2 is resolving the dependencies nicely without pulling in all of CDT, I suggest to do the CDT feature merge for TCF too. This solves too the “strange”
feature name (Target Communication Framework, CDT Extender) issue from the users POV. And probably we should replace “RSE Extender” with “RSE Support”, which makes it easier to understand for the user for that feature two.
If we do the change, we end up with only 3 features than
Target Communication Framework
Target Communication Framework, RSE Support
Target Explorer, TCF
Which appears much better/clearer than the four features from now.
@Martin: Note that the Hudson builds currently fail because the RXTX repository seems to be gone !!
Best regards, Uwe
J
Hi all,
TCF features are now exposed in the Juno repo – see attached screenshot
http://download.eclipse.org/releases/staging
I’d suggest updating the feature descriptions a bit to clarify what each of the 4
Contributed features provides from a user’s point of view. For example
TCF CDT integration: “A full-featured C/C++ debugger for local or remote systems running a TCF agent”
TCF RSE integration: “Remote file system and process browsing in RSE for systems running a TCF agent”
TE CDT Extender: “C/C++ debugger launching from Target Explorer”
TE TCF: “TCF connectivity plug-in for the Target Explorer to browse remote file systems, processes or open a terminal”
Is this possible for M7 (until Monday noon) ?
BTW does the TE CDT Extender make any sense at all without TE TCF ?
Is TE TCF interesting at all without the TE CDT Extender ?
Martin
Hi all,
We now have 2 update sites at Eclipse.org for TCF Juno builds:
http://download.eclipse.org/tcf/builds/juno/milestones
http://download.eclipse.org/tcf/builds/juno/nightly
I’m working with Doug Schaefer and David Williams on getting these contributed to Juno M7 ASAP, but if you need to build against TCF now you should be able
to direct your builder against the milestone site.
The simplest way (least disruption) would be just mentioning the TCF repo in the cdt.b3aggrcon file – which should be OK since TCF is still a subproject of
CDT and has always been contributed to Juno via its CDT parent project (also the artifacts had always been there, I checked the M7 repo). Only the builds were taken apart.
We’ll be looking for a clean solution though.
Martin
From:
tcf-dev-bounces@xxxxxxxxxxx
[mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Francois Chouinard
Sent: Wednesday, May 02, 2012 1:47 AM
To: TCF Development
Subject: Re: [tcf-dev] TCF 1.0 and Juno M7
Yo,
TCF is required for one feature of the legacy part of LTTng. If anything should be removed from the Linux Tools delivery it is either that single feature or (worst case) the legacy LTTng (pre-2.0)
For the newer version, also delivered in Juno, we rely solely on RSE. However, the jury is still out if we will eventually be using TCF at all with the new version (but certainly not in the Juno time frame).
On Tue, May 1, 2012 at 7:04 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote:
I'm pretty sure I +1'd Juno in the project metadata for TCF. But I don't
have access to that anymore.
And, no, it would not be alright to have a separate update site. You'd
have to rip Lttng off the train then as well.
Doug.
On 12-05-01 6:30 PM, "Tarassov, Eugene" <eugene.tarassov@xxxxxxxxxxxxx>
wrote:
>We need to resolve this.
>Let's see what Martin O. says - he is TCF project lead.
>If it is too late for Juno, is it OK to have separate update site for TCF
>until next release?
>
>Thanks,
>Eugene
>
>-----Original Message-----
>From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On
>Behalf Of Jeff Johnston
>Sent: Tuesday, May 01, 2012 3:15 PM
>To: tcf-dev@xxxxxxxxxxx
>Subject: Re: [tcf-dev] TCF 1.0 and Juno M7
>
> From what I understand, TCF is now its own project, but TCF does not
>have a b3aggrcon file in org.eclipse.juno.build and is not listed on the
>following page:
>
>http://www.eclipse.org/projects/releases/releases.php?release=juno
>
>There is a process to go through (e.g. there is a Juno flag to turn on
>under the Eclipse portal). I also couldn't find any recent CQs with TCF
>in the subject. A CQ is needed to officially move or create a project
>as the IP must be cleared.
>
>David Williams does not seem to know about the project and he is in
>charge of aggregation.
>
>-- Jeff J.
>
>On 05/01/2012 05:51 PM, Tarassov, Eugene wrote:
>> Hi Jeff,
>>
>> TCF 1.0 is top level project now.
>> We do want it to be part of train releases.
>> It is supposed to be in Juno - unless something went wrong.
>>
>> Regards,
>> Eugene
>>
>> -----Original Message-----
>> From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
>>On Behalf Of Jeff Johnston
>> Sent: Tuesday, May 01, 2012 2:32 PM
>> To: tcf-dev@xxxxxxxxxxx
>> Subject: Re: [tcf-dev] TCF 1.0 and Juno M7
>>
>> 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
>> _______________________________________________
>> 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
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/tcf-dev
--
Francois
|
