The problem here is the old one of trying to build things on top of other things.
If you have no buy-in to the process from your providers you are left trying to hit a moving a target. Solutions: 1) Make it easy for people to maintain it 2) Write tests so you know when it breaks 3) Make it a more first class construct such that developers can "automagically" maintain it or at least know early when it is affected. 4) "Lock down" the provider's config and complain when they change it without notifying you. On Mon, 2006-01-30 at 07:48, Dimitris Andreadis wrote: > Somehow we need to do a better job keeping the installer xml > descriptor templates in-synch with the module xml descriptors, so > whenever a descriptor changes the template needs updating. > > I just fixed a trivial one, probably my bad: > http://jira.jboss.com/jira/browse/JBAS-2742 > > The other thing we need to clarify is whether the installer > distribution is the "recommended" one, since more cases (forums / > support) will start appearing where we are not sure about the used > (user/customer) config. -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
