Re: api support

Vitezslav Stejskal wrote:
> I am not sure about the plans of apisupport module projectization (CCing 
> Jesse as he might now more).

I don't, actually. I did convert apisupport to use the 3.5 Classpath API 
some time ago, so if that is actually implemented compatibly in Projects 
then a lot of stuff may work. It still uses Datasystems of course, and 
doesn't use any Projects APIs. Probably it could be built on the 
projects branch (just added to the module config), even without being 
fully "projectized", but that's all I know. Certainly something like 
<nbinstaller> does not intrinsically need to know anything about 
Projects at all.

Note - the trunk version of apisupport does need the trunk version of 
the ant module, and last I checked no one had merged in the trunk 
changes to the ant module into the prj_40_prototype branch - it is 
probably a simple merge since the Projects-specific stuff is in a 
separate submodule anyway, should only be necessary to tweak the 
manifest dependencies.

> I definitely want to create the verion of API support module which would 
> support projects developement (creating natures, registering looks, 
> environment providers, creating build tragets skeletons and all this 
> projects stuff), but at this time I have a lot of other tasks, so I 
> can't start working on it, sorry.

Ditto, not on my horizon at the moment. Potentially a lot of work; the 
current apisupport (other than the New Module Wizard) has no provisions 
for creating templates that add layer entries, unfortunately, and that 
limits its usefulness for things involving nontrivial declarative 
registration.

-Jesse

-- 
Jesse Glick <mailto:[email protected]> x22801
NetBeans, Open APIs  <http://www.netbeans.org/>