And then smack the configuration file:
-mvn -DconfigId=basic install
When I went to do this I noticed that "basic" was already there (along with several of it's friends) - and the two files differ greatly in size. Can we update the docs accordingly? Or is something else going on here ...
And then smack the configuration file:
-mvn -DconfigId=basic install
When I went to do this I noticed that "basic" was already there (along with several of it's friends) - and the two files differ greatly in size. Can we update the docs accordingly? Or is something else going on here ...
The instructions are correct for 1.4.x, Simone and Alessio just put
the configurations directly in svn instead....
Now, shall we start adding ifs to the docs? (if on 1.4.x do that, on
1.5.x something else, and so on...)
And then smack the configuration file:
-mvn -DconfigId=basic install
When I went to do this I noticed that "basic" was already there (along
with several of it's friends) - and the two files differ greatly in
size. Can we update the docs accordingly? Or is something else going on
here ...
The instructions are correct for 1.4.x, Simone and Alessio just put
the configurations directly in svn instead....
Now, shall we start adding ifs to the docs? (if on 1.4.x do that, on
1.5.x something else, and so on...)
Hmm, the whole point of me taking it out was so that they werent stored
in svn... Which defeats the purpose of the entire effort since the
majority of feedback about it was negative.
And then smack the configuration file:
-mvn -DconfigId=basic install
When I went to do this I noticed that "basic" was already there (along with several of it's friends) - and the two files differ greatly in size. Can we update the docs accordingly? Or is something else going on here ...
The instructions are correct for 1.4.x, Simone and Alessio just put
the configurations directly in svn instead....
Now, shall we start adding ifs to the docs? (if on 1.4.x do that, on
1.5.x something else, and so on...)
Hmm, the whole point of me taking it out was so that they werent stored
in svn... Which defeats the purpose of the entire effort since the
majority of feedback about it was negative.
Well, too many steps to get a running geoserver going.
Yet, even having the configuration in svn is not best, we still have
svn issues (for example, the new config have a "preview" folder that
conflicts with what svn expects, probably need to add another ignore)...
I would like to have each configuration in a separate svn module,
but how could we manage dependencies and in-webapp config injection,
I don't know...
Probably a modified configuration script that picks a named module
contents, and a different way of exploding it that allows svn to
completely ignore the configuration.