Sorry for the delay...
> Probably the biggest annoyance I have with using a sub-module is that
> the ${project.root} property within the sub-module ends up including the
> module above it instead of being the actual project root, so I have to
> define my own local ${project.root.local} property in each sub-module.
> To illustrate:
>
> from a first level module:
> ${project.root}="/home/ssayles/src/myProject"
>
> from within a sub-module:
> ${project.root}="/home/ssayles/src/myProject/myModule"
>
> Is it possible to get this value to remain the real project root?
> Perhaps I'm missing something?
Sub-modules are not supported at the moment. Currently all modules must be
direct peers. I might find a way around this in the future.
> Also, one of my thoughts is that we should raise developer awareness
> about the associated tests for a module. In other words, if they change
> something in the code which breaks the tests for that module, this
> should be readily apparent. Of course, this will happen when you
This is planned.
> 2. Force the integration of the module build with the associated
> testsuite. In other words, have build targets within the module call
> correlating targets in the testsuite sub-module. This does not seem to
> fit within the buildmagic way of doing things (to me), but it could
> work.
Perhaps... will have to see. Would probably be better to leave them
seperate but require developers to run the modele tests. I know what you
mean though... problems is that by doing so, making small changes and
recompiling would take too long.
Or I could short-circuit with unless properties.
Anyways... we'll see.
--jason
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
