Hi, I was overriding some of the modules-core/administration ac.usecases java source files to generate dynamically named user groups - e.g creating a group "grp-myname" when the user "myname" is created. As well as letting users do some of the addition to groups and so on ...
My own module overrides the AddUser.java etc. Well, I noticed that the administration module did not export the ac.usescases package, so my module would fail when compiling unless I included all/most of the package files from the administration module ac.usecases package into my custom module's source directory. Since I was only interested in overriding a few files in the administration ac.usecases package, I included the <export package="org.apache.lenya.cms.ac.usecases"/> to the administration config/module.xml definition. Is there any reason not to export the package from administration, or is there a better way to accomplish the same thing - overriding the default AddUser.java , changing the usecase logic etc ... ? I would imagine it would be easier to override some of the core modules behaviours if many of the obvious packages were exported, so compiling custom modules would be more effortless for newbies. Also, this could open for easier publication of custom modules to override or add functionality to Lenya - which would be great ... getting a "forge of user contributed modules" is sorely needed, I think. It would be easier for newcomers to get the hang of Lenya and start customizing by having more examples on how to do so ... ;-) -Gringinho
