Bartosz Oudekerk wrote:
Reinier van den Born wrote:
Apparently basedir=.../editor, which explains the superfluous "editor"
in the path.
Also localdev is apparently hardcoded, so it never looks in
example_sqlserver_project
Exactly, it's the default. Unless you specify another location, it looks
there.
So I added the following line to my build.properties:
maven.cocoon.servermanager.configuration.dir=${basedir}/src/configurations/example_sqlserver_project
which seems to do the trick (didn't run the editor yet, so I am not sure)
It's the correct way to do it if you're using anything but the default.
It took me a while, but I get that now :-)
Although the current organisation seems to lean on two concepts ("hinkt op twee gedachten"). One, to have a "dir" with
many configurations, one per "project" (hence the projects subdir in localdev, etc). The other, to have completely
separate configurations (each its own "dir"), in which case this projects subdir has no real function. This "mismatch"
actually caused me some confusion.
I like the first concept. In fact all configurations (localdev and the templates) could be kept in a single "dir" (ie.
maven.cocoon.servermanager.configuration.dir) with each configuration in a separate projects subdir. One would only have
to set maven.cocoon.servermanager.configuration to change to another (standard) configuration.
Only if a custom config is needed, maven.cocoon.servermanager.configuration.dir would be pointed to a directory outside
of the .../editor tree.
Anyway,...
I do wonder about the localdev/projects/localdev/... This projects
subdir is in all configurations (taxdev, the templates). Seems to
suggest that I could also put the projects/example_sqlserver_project
subtree under ../localdev/projects, except that the configuration.dir
is then still wrongly set.
Plus you would be making changes within the default CMS code, which is
generally not recommended. If you want to use your own servermanager
configuration, create it one level above the editor and set
maven.cocoon.servermanager.configuration.dir accordingly.
When using the default (localdev) the dir is determined differently,
so that the only config that works...
I'm not sure what you mean here.
What I meant is that the settings in editor/project.properties are not correct. It is only because these settings are
not used if you specify localdev, that the default build works.
If you look in editor/maven.xml you'll see a special treatment of localdev,
which IMHO shouldn't be necessary.
Anyway, I'd say the instructions need an update...
I think you're right, I'll put it on my TODO list.
Regards,
--
Reinier van den Born
HintTech B.V.
Rotterdamseweg 183c, 2629 HD Delft
T: +31(0)15 268 2573
F: +31(0)15 268 2567
M: +31(0)6 494 171 36
--
HintTech levert specialisten op het gebied van softwareontwikkeling (.NET en
Java),
projectmanagement, informatiebeveiliging en business consulting.
KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01
begin:vcard
fn:Reinier van den Born
n:van den Born;Reinier
org:HintTech B.V.
adr:;;Rotterdamseweg 183c;Delft;;2629HD;Netherlands
email;internet:[EMAIL PROTECTED]
tel;work:+31-15-268 2573
tel;fax:+31-15-268 2567
tel;cell:+31-6 494 171 36
note;quoted-printable:KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01=0D=0A=
=0D=0A=
HintTech levert specialisten op het gebied van softwareontwikkeling (.NET=
en Java), projectmanagement, informatiebeveiliging en business consulting=
.=0D=0A=
=0D=0A=
url:www.hinttech.com
version:2.1
end:vcard
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
