[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Nightly build broken

Fair enough.  We certainly don't need to worry about refactoring the launch plugin right now.
 
It may make sense though to put all of the UI from the org.eclipse.cdt.debug.mi.* plugins under a capability category.  That way we can easily hide that category by default in our products without having to hide each bit of UI ourselves.  It would also become more future-proof if it's defined in the plugin(s) themselves.  Any objection to adding this?  I assume it would only need to go into the UI plugin.  If no objections, what should it be called?  CDT GDB MI, or CDT GDB CDI?  I'm not sure exactly what those plugins include.
 
Thanks,
Warren
 


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ext Doug Schaefer
Sent: Friday, April 16, 2010 10:54 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Nightly build broken

The cdt.platform feature is supposed to be gnu free. The launch plug-in has a lot of gnu stuff in it which is why I think I moved it there. But it's all a mess. A topic for the CDT summit. ;)

On Fri, Apr 16, 2010 at 11:45 AM, <Warren.Paul@xxxxxxxxx> wrote:
So would anyone like to comment on the launch plugin remaining in the gnu.debug feature vs. moving it to cdt.platform alongside cdt.debug.core/ui?  I think it's the right thing to do, but may be missing some larger implications of such a change.
 
Thanks,
Warren


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ext John Cortell
Sent: Friday, April 09, 2010 4:25 PM
To: CDT General developers list.; CDT General developers list.; cdt-dev@xxxxxxxxxxx
Cc: cdt-dev-bounces@xxxxxxxxxxx
Subject: RE: [cdt-dev] Nightly build broken

I think it's getting late in the week and my brain isn't quite working as it should.

I'm going to leave you to sort out how we could disassociate the launch plugin from the gnu feature (perhaps move it to the cdt-platform feature). I'm going to create the dedicated gdb feature to sort the immediate problem.

John

At 03:51 PM 4/9/2010, John Cortell wrote:
Sounds like we should move the launch plugin into the new, proposed dedicated gdb feature. That would address your long-standing problem.

John

At 03:46 PM 4/9/2010, Warren.Paul@xxxxxxxxx wrote:
Content-Language: en-US
Content-Type: multipart/related;
         boundary="_005_5ABC9C306CCC574887C58E7EAC03A28C2A496C3CBDNOKEUMSG02mgd_";
         type="multipart/alternative"

I find fault in the fact that the launch plugin is in a gnu feature.  I've been meaning to raise this just this week actually, so good timing. :)
 
The launch plugin isn't really GNU specific, and is used in our products which have nothing GNU.  So with the current feature structure we basically have to include that feature but hide any UI from the MI plugins.  Ideally we'd move the launch plugin into the platform or core feature, and then the new GDB plugins could be added to the existing gnu.debug feature.  That kind of forces DSF based products to include the CDI plugins I guess though.  If those were added without moving the launch plugin, that's two more plugins that we don't want that we get included and presumably more UI we have to hide.
 
Ahh..  I don't know what the best solution is, but giving you some more things to think about.  :)
 
Thanks,
Warren
 


From: cdt-dev-bounces@xxxxxxxxxxx [ mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ext John Cortell
Sent: Friday, April 09, 2010 3:28 PM
To: CDT General developers list.; CDT General developers list.
Cc: cdt-dev@xxxxxxxxxxx; cdt-dev-bounces@xxxxxxxxxxx
Subject: Re: [cdt-dev] Nightly build broken
Given that existing DSF-feature --> CDI-feature dependency, your suggestion makes sense to me. If someone finds fault with it, then the dedicated feature will be the way to go.
John
At 03:23 PM 4/9/2010, Vivian Kong wrote:

Actually it looks like org.eclipse.cdt.gnu.dsf already have some dependencies on org.eclipse.cdt.gnu.debug feature (it depends on org.eclipse.cdt.launch, which is in o.e.cdt.gnu.debug)...so maybe we can move o.e.cdt.gdb* to the o.e.cdt.gnu.debug feature?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab

Inactive hide details for Vivian Kong---04/09/2010 03:56:52 PM-   Vivian Kong---04/09/2010 03:56:52 PM---Hi everyone, The nightly build is broken:

[]  
From:
Vivian Kong/Toronto/IBM@IBMCA
[]  
To:
cdt-dev@xxxxxxxxxxx
[]  
Date:
04/09/2010 03:56 PM
[]  
Subject:
[cdt-dev] Nightly build broken
[]  
Sent by:
cdt-dev-bounces@xxxxxxxxxxx



Hi everyone,
The nightly build is broken:
/opt/public/download-staging.priv/tools/cdt/releng/org.eclipse.cdt/all/org.eclipse.cdt.releng/tools/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.6.0.v20091204/scripts/genericTargets.xml:106: Bundle org.eclipse.cdt.debug.mi.core_7.0.0.201004090808 failed to resolve.:
Missing required plug-in org.eclipse.cdt.gdb_7.0.0.
The new cdt.gdb.* plugins are missing from the cdt.map file. I'll add them in.
However, both features org.eclipse.cdt.gnu.debug and org.eclipse.cdt.gnu.dsf have dependencies on the new org.eclipse.cdt.gdb plugin. Should the new plugin be part of the cdt.platform feature instead of cdt.gnu.dsf feature?

Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev