Guys, <br><br>In the repository, and also in general (ie normal IDE/text files) we are going to allow rules to be in individual files, and then have a deployment tool collect them all up, compile etc... (of course current DRL will still apply as it does now).
<br><br>For this to work, they will all be (for now) in the one folder - and there will be some overarching "package configuration" that sets the name space, imports, globals etc (all the stuff you see at the top of a drl now).
<br><br><br>So my question: <br><br>*should this config file just be a plain test file - line based stuff just like you see now at the top of the .drl file?<br>* Or, should we have some more controlled XML or flat format that has more meta data in it (from the repository, optionally). In any case, a nice Eclipse Form based UI can "help" with the package config (importing classes etc), but at the end of the day, it has to be friendly for hand editing text.
<br>* or multiple files for different "parts" of the config (imports in one, globals in another etc).<br><br>(and it will of course be synced to the repository where applicable).<br><br><br>Thoughts anyone?<br><br>
Michael.<br>