--- In [email protected], "Rodney Kinney" <[EMAIL PROTECTED]> wrote:
>
> > VASSAL can now no longer read those extensions because:
> > Unable to load extension ZZZ as it was prepared for module XXX.
>
>
> If you unzip the extension file, you can edit the buildFiles and zip them
> back in. In the first line, there's an attribute that specifies the name of
> the parent module.
>
> rk
>
>
> [Non-text portions of this message have been removed]
>
Is thre any other way to do this within the VASSAL engine itself? This
solution will work, but I
would hate to have to do this everytime I update the module name.
