Community
Participate
Working Groups
The Autotools project uses ProjectCreatedActions to create a new Autotools project from the New C Project wizard. The class is public but has been marked noinstatiate which means that an API violation has occurred. The NewAutotoolsProject code which uses the class is based on the CDT NewManagedProject code. If there is no particular reason for the @noinstantiate, this is a request to remove the restriction or to provide a suitable API-compliant alternative.
I took a look at ProjectCreatedActions and I do not think it is sufficiently well defined to deserve to be an API. I think there should be a set of well defined methods to create managed build project in cdt.managedbuilder.core and it should be used by the wizards CDTCommonProjectWizard etc. and by template engine processes including NewAutotoolsProject. I took a shot to define one but CDTCommonProjectWizard much resists to any API so more time investment is necessary. So I think for now @noinstantiate should stay until the better API is developed. That is a signal that it is not a stable interface. You still can use it in your product. You can suppress the warning or disregard it. What I can do is to add as a comment a reference to this bug, so the developers would be more cautious not to change the interface.
Returning to the pool.
*** cdt cvs genie on behalf of agvozdev *** bug 318063: Note about ISVs in comment. [*] ProjectCreatedActions.java 1.6 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/all/org.eclipse.cdt.managedbuilder.core/src/org/eclipse/cdt/managedbuilder/templateengine/ProjectCreatedActions.java?root=Tools_Project&r1=1.5&r2=1.6
(In reply to comment #1) > I took a look at ProjectCreatedActions and I do not think it is sufficiently > well defined to deserve to be an API. I think there should be a set of well > defined methods to create managed build project in cdt.managedbuilder.core and > it should be used by the wizards CDTCommonProjectWizard etc. and by template > engine processes including NewAutotoolsProject. It should be probably along the lines of bug 336377.
