understanding how configs are "mavenized"

I have been trying to get an existing project to play in the new
mavenized environment, but I am running into some problems, I think due
to my lack of understanding of how all the pieces now fit together.

I am having trouble getting the following configurations to get picked
up in the war file:

conf/client/struts/struts-config.xml - this file has my struts forwards,
which should get folded in to the consolidated struts-config.xml. For
me, only associated projects like app-crud have the forwards in the
final war file, but my project entries in this file are not getting
picked up.

conf/server/logkit.xconf, system.xconf - these files are not getting
carried over into the war file. The merged.config in the war file does
not have any of my "stuff" from these files, but the dependency apps
like app-crud are working properly.

xdoclet persistent stuff: I had a bunch of xdoclet stuff in my java
persistent classes, which ant used to pull out and automatically
generate persist-name.xconf files, which would then get folded into the
merged file. Now with my "maven war" process, these files are not
getting created, and when I look at the persistent menu in app-crud, I
do not see my app's schema.

Any guidance on how to get these configuration items to flow through to
the war would be greatly appreciated. I have read the documentation, but
I have not found the relevant section which describes the structure of
configuration.  The odd thing is, I have (I think) faithfully copied the
structure and layout of other apps in CVS, such as app-crud, and
app-poll, but what is apparently working there is not working for me.

Regards,

Adam


http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com