New Modules Mechanism
(MAGNOLIA-768)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.0 Final |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Magnolia International |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
the samples are a separate module (makes it easy to avoid installation or to uninstall) |
| Comments |
| Comment by Philipp Bracher [ 17/May/06 ] |
|
part of RC1 |
| Comment by Sameer Charles [ 29/May/06 ] |
|
We should not put sample templates and docroot in to a JAR, it wont make sence for a "templater" who simply wants to change the look and feel of the templates. |
| Comment by Philipp Bracher [ 29/May/06 ] |
|
the jsps are the extracted to the file system and therfore changeable as ever, but they are delivered as an extra module so that you can avoid installation of not needed sameples. How ever we may wait with this. |
| Comment by Magnolia International [ 15/Nov/06 ] |
|
duplicated by |