MMBase

Maven example webapp's config directory is to empty

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.9.0
  • Component/s: Build
  • Description:
    Hide
    The from the Maven build resulting example webapp has a very empty config directory. In order to for example alter the database or logging configuration one has to unzip the mmbase.jar in order to find the configuration files needed.

    At least some of the most needed configuration files and directories should be present so that one does not need to hunt for them.
    Show
    The from the Maven build resulting example webapp has a very empty config directory. In order to for example alter the database or logging configuration one has to unzip the mmbase.jar in order to find the configuration files needed. At least some of the most needed configuration files and directories should be present so that one does not need to hunt for them.

Issue Links

Activity

Hide
André van Toly added a comment - 2008-08-01 09:44
I would rather have all configuration present in the WEB-INF directory, like it was in the ant build, then none at all like the case is now with maven.
Show
André van Toly added a comment - 2008-08-01 09:44 I would rather have all configuration present in the WEB-INF directory, like it was in the ant build, then none at all like the case is now with maven.
Hide
Michiel Meeuwissen added a comment - 2008-09-12 08:16
But whatis to be considered configuration?

log4.xml clearly is, dtds clearly are not.

Currently we find:
michiel@sepio:~/mmbase/head/example-webapp/target/example/WEB-INF/config$ ls
datatypes.xml functions security

Which is IMHO generally not so bad. datatypes.xml and functions are only templates, which is good. security is context security which you probably want to change to (if only to change admin2k).

Most sadly the README is missing.

In 1.8 we also find:
builders/applications - stupid
applications - not really necesasry, as but could as a matter of example be shipped in an _example_ webapp..
modules - this can in production environment be omitted, but to get started at least a jdbc.xml can be handy to find.
taglib - contains template configuration, so should be included
utils - contains several actual settings, so should be included
xslt - xslt is code, so this IMHO could just as wel be just in the jar (we don't ship .java's either).


Show
Michiel Meeuwissen added a comment - 2008-09-12 08:16 But whatis to be considered configuration? log4.xml clearly is, dtds clearly are not. Currently we find: michiel@sepio:~/mmbase/head/example-webapp/target/example/WEB-INF/config$ ls datatypes.xml functions security Which is IMHO generally not so bad. datatypes.xml and functions are only templates, which is good. security is context security which you probably want to change to (if only to change admin2k). Most sadly the README is missing. In 1.8 we also find: builders/applications - stupid applications - not really necesasry, as but could as a matter of example be shipped in an _example_ webapp.. modules - this can in production environment be omitted, but to get started at least a jdbc.xml can be handy to find. taglib - contains template configuration, so should be included utils - contains several actual settings, so should be included xslt - xslt is code, so this IMHO could just as wel be just in the jar (we don't ship .java's either).
Hide
Nico Klasens added a comment - 2008-10-03 00:02
<mmbase.config.bundle>true</mmbase.config.bundle>
Show
Nico Klasens added a comment - 2008-10-03 00:02 <mmbase.config.bundle>true</mmbase.config.bundle>

People

Dates

  • Created:
    2008-07-31 17:43
    Updated:
    2008-10-03 00:02
    Resolved:
    2008-10-03 00:02