[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] empty name of projectType elements

I can confirm that this 'new behaviour' actually does affect existing plugins. I just spent about one hour debugging the mentioned issue: My formerly working template project did not list configurations anymore...

(I had to "debug" this issue because I did not read this post :-(. After having commited my updated plug-in extensions, my working colleague pointed me to that post and that's why I'm writing to the list now.)

Raphael

On 11/22/2011 11:23 PM, Liviu Ionescu wrote:
I would like the gurus on this list to decide whether the "projectType" element should be nameless, as needed by the new requirements introduced by the latest CDT version.

a more detailed story is below:

on 2011-01-25, the CDTConfigWizardPage.java file in org.eclipse.cdt.managedbuilder.ui.wizards was patched, so that the wizard used to create new projects no longer lists "projectType" elements that have a non empty name attribute.

the reason was an attempt to fix the bug 335338

https://bugs.eclipse.org/bugs/show_bug.cgi?id=335338

the comment inserted in the source code states:

// Bug 335338 don't include project type configurations if we're not creating a project-typed project
//            Project types are non-default if their nameAttribute != "" (see: ManagedBuildWizard: "old style project types")


however, this broke compatibility with existing plug-ins, for example my GNU ARM Eclipse Plug-in, as reported in bug 356111

https://bugs.eclipse.org/bugs/show_bug.cgi?id=356111

later marked as duplicate of bug 356864

https://bugs.eclipse.org/bugs/show_bug.cgi?id=356864


I'm convinced there other plug-ins out there that are no longer functional since they use named "projectType" elements.


for those not aware of these details, the "projectType" elements list the Debug/Release build configurations associated to toolchains.

the current behaviour is that "projectType" elements that have a name are ignored, and if all such elements have names, the wizard does not find any configuration and fails with:

"At least one configuration should be available. Project cannot be created".

if really needed, I could update my plug-in and remove all names from the "projectType" elements and do not care of other plug-ins, but I think this problem requires a community decision.

according to the "Managed Build System Extensibility Document", 3.2 ProjectType, "You must also provide a meaningful name that will be displayed to the user in the UI and new project wizards"

also the Schema in the 3.2.1 table lists the "name" attribute as Required.

I don't know what "old style project types" are and I'm not able to follow the reasons behind this additional requirement, but in principle I think that removing the name of an element to mark it somehow different from other elements is not a very fortunate decision.

unless very good reasons to not do so, my suggestion is to revert to previous 7220a version and increase the version of org.eclipse.cdt.managedbuilder.ui from 8.1.0 to 8.1.1 so I can check if my plug-in is running in the proper environment.


regards,

Liviu



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