On Thu, 06 Jan 2011 14:09:02 -0200, Joel Halbert <j...@su3analytics.com>
wrote:
So if I understand correctly:
- the only way to disable modules that are specified in the manifest is
to remove the jar from the classpath
Wrong. See
http://tapestry.1045711.n5.nabble.com/T5-disable-loading-specified-module-td2431110.html
- if you have lots of modules, which a client may want to selectively
enable, do not declare them in the manifest, but instead let the client
use the tapestry.modules sys property to selectively enable them
This looks like a huge JAR. Why not break it in smaller, more manageable
ones?
You can also use @SubModule in a module class to include other modules
automatically without using system properties or context parameters.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
