Community
Participate
Working Groups
The "base package" concept should be moved from being a project-level setting (that applies - or could apply - to each template) to a setting of the "web client with services" template, since this is really the only template that *needs* it. The "base package" field should appear above the widget libraries table presented on the 3rd page of the wizard (when the 'web client with services' template is selected). See my note from 9/2 for more detail.
I think we need to have this correct for 0.7 ..
This issue came out of the IDE scrubbing work that Theresa and I recently started.
Created attachment 204858 [details] Fix
Move base package to "web client with services" template
I downloaded the build from 201110100900 and we do not appear to be creating a 'client' package when a user chooses to create a 'Web client' only project. I believe we should still be creating a 'client' package for this type of project.
The problem seems not caused by this work item. Moreover, Brenda has opened this issue as a defect in bug 360598. So close this work item.
I think we need to look again at this. For the 'Web 2.0 client application' template, we either need to not create any packages (because packages are not technically required since everything is JavaScript targeted) OR need to ask the user for a base package if we are going to create a 'client' and a 'common' package. Currently the user is not able to specify a base package, but yet the wizard still creates a 'client' and a 'common' package. This doesn't make sense to me ...
I summarized the behavior of base package below. Please confirm if this is what you are thingking. Basic project no base package input no package created Client project provide base package input create client & common package if base package input is not empty, no need to configure generator, all inherit JSGenerator from project. Client with Service project provide base package input create client, common & server package if base package input is not empty, configure generator accordingly.
Tony - here is a slight update to what you proposed: Basic project no base package input no package created Client project provide base package input create client package (using whatever base package was specified), no need to configure generator, all inherit JSGenerator from project. Client with Service project provide base package input create client, common & server packages (using whatever base package was specified), configure generator accordingly. ==== Some examples ... Example 1: Template: Web 2.0 client Base package: "" (empty string) Packages created: client Example 2: Template: Web 2.0 client Base package: com.mycompany Packages created: com.mycompany.client Example 3: Template: Web 2.0 client with services Base package: "" (empty string) Packages created: client common server Example 4: Template: Web 2.0 client with services Base package: com.mycompany Packages created: com.mycompany.client com.mycompany.common com.mycompany.server
Set to Major because they are things newer developers may run into fairly quickly
It was fixed .
Looks good.
