This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
From email on dev@apisupport: Tim: >> 1. The plan was (and I truly hope still is) to have a wizard for >> creating new sample projects, packaging them up, etc. Should I be >> hoping that will be ready, and just create a proper suite-ified >> feedreader & write up the steps, or should I plan to manually write a >> wizard iterator for it (now there's an API I hoped I'd never ever >> touch again!)? Jesse: > It's not ready yet, but this is the responsibility of other developers - > probably Martin, Milos, or Radek. Please file a P2 DEFECT for it to make > sure it gets handled. So, we have some deliverables for 4.2 that depend on this feature - status?
Provisionally assigning to Radek, but reassign if you want.
I believe that Milos is the right person, since he has commited "New Project Template" wizard few hours ago. Probably not the same, since it handles only templates for J2SE projects, but presuambly very similar. Not sure however :)
Actually, Martin, you can zip any project type, not just j2se projects AFAIK. the current status is: 1. in cvs trunk, zips up the project, generates and registers a wizardIterator that will unzip the project. Has some basic panel. it's compilable and works out of the box, of course one can tweak the generated code later. I suppose you will have to do that for your feedreader project. (well actually if there's a top level directory with a project deinition with siblings under it, it might actually zipp all of them. not sure if it's a bug or defect. 2. there's still work to be done there. especially on the ui side of things. currently the template category cannot be chosen and is hardwired to "Others". Naturally you can rewrite that in the generated code.
So if I have suite S - module A - module B - module C and tell it to zip up S, it should work, and the only thing I need to worry about is ensuring that the UI opens A/B/C as well, correct? What about templatizing the project name, etc.?
correctly showing template categories now. to Tim: Yes, I think the suite scenario should work. it should zip everything. By default will just upen the suite project. Currently no change of the zipped project is done. I don't think it's planned. That would assume that we know the semantics of *all* project types that are out there now or possibly emerge later. What you definitely can do is to rewrite the generated unzipping code to perform some operations on it. I consider the issue closed (fixed) now.
> Yes, I think the suite scenario should work. No, it seems that it doesn't work for suite case at all, that the code is not ready for such a case - see issue 63247.
v