That sounds good. That should make things fairly easy
to use. Or at least easier then they are now :)
+1
> Here is an idea...along what you are thinking for #2.
>
> One problem with Torque is that right now, we will be distributing a bunch
> of properties files that people will modify. If they want to upgrade Torque,
> then they will have to re-edit those property files after they upgrade in
> order to be stay current. It is a pain in the butt.
>
> So, one thing we could do is at least start a process like this:
>
> ./torque.sh generate_properties
>
> [ then go edit the properties files ]
>
> ./torque.sh generate_maps
>
> ----------------------------------------
>
> If you are upgrading your version of Torque, we could do something like
> this:
>
> ./torque.sh upgrade_properties
>
> What that would do is execute code that would re-generate the properties
> files based on your existing ones (and the values in those) and include
> anything that is new. Also, if there is property name changes, this class
> could handle that as well.
>
> -jon
>
>
--
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
