Opened 15 years ago
Closed 14 years ago
#241 closed defect (fixed)
release shouldn't include demos by default
Reported by: | david | Owned by: | jkuhnert |
---|---|---|---|
Priority: | high | Milestone: | 0.9 |
Component: | BuildTools | Version: | 0.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
We should only be building in what is necessary when someone asks for a release build. Builds often end up going straight into CVS/SVN repos so we shouldn't add clutter.
Change History (7)
comment:1 Changed 15 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 Changed 15 years ago by
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
I'm not against having an option to build with demos, but if you are in a production environment, you don't want to be pulling in the demos all the time. We can, and should, set that flag for nightly and other public releases, but don't force that upon folks who are deving for production.
comment:3 Changed 15 years ago by
You could handle this by having two types of builds, one a "full" build that includes the demos and the other a "library" build that includes only what someone would need to build their own apps. (This is what Struts does, for example.)
comment:5 Changed 15 years ago by
Owner: | changed from anonymous to jkuhnert |
---|---|
Status: | reopened → new |
comment:6 Changed 14 years ago by
Should be a simple close out... if its not fixed with the latest build modifcations from James....
Ping?
comment:7 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
I'll close this out since there are no demos currently in the 0.9 tree.
the demos dir is in lieu of the tests dir, which I think means that it should be our "best face". Most folks who stumble across a Dojo build *should* see what's in the demos/ dir if they see nothing else.