I think we should have separate deploy directories.
/deploy/system with all core stuff /deploy/applications with all non-jboss configs.
A number of clients do this I found this much easier to manage myself in other projects I've worked on.
You are right though scott. Putting stuff into a new subfolder to make the deploy dir look clean really is just sweeping the dirt under the rug.
Discuss.
Bill
Scott M Stark wrote:
There should be better categorization, but this is a bit separate from the interface presented to the admin which can categorize and filter the management view. Just throwing everything in a new subfolder to make the deploy dir look clean is just sweeping the dirt under the rug.
Sacha Labourey wrote:
Maybe everything in deploy should be in a /deploy/system folder and the pure
/deploy folder should only contain some sample config file:
- sample-queues.xml
- sample-datasource.xml
- sample-timer.xml
Etc.
The current /deploy folders contains way to many files. At least we should
better categorize them as we have done with JMS and Management today.
_______________________________________________ the.core mailing list [EMAIL PROTECTED] http://mail.jboss.org/mailman/listinfo/the.core
-- ================ Bill Burke Chief Architect JBoss Group LLC. ================
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
