CVS integration does not work with aliased modules

> The CVS integration in Jira 3 Preview has improved a lot and now it can be
> considered finally usable when one has more than just a couple of source
> files (tested the Professional Standalone version) !
>
> But it only works nicely if the 'CVS modules' are simple directories in the
> repository. Unfortunately we have been exploiting quite heavily a standard
> feature of CVS called 'alias modules' and this gives now the new Jira CVS
> integration a headache.
>
> To simplify it when we checkout a single module 'env_projectx' it is
> actually an alias module which collects things on the server side and comes
> out in physical files as
> root/struct_common
> root/struct_projectx
> ...
>
> and still having the correct direct CVS repository details of the server
> directories in the local configuration files of the 'CVS' subdirectories.
> Note that this 'root' directory doesn't even exist in the 'log files' of
> CVS.
>
> So the problem now is that when I try to set the Jira's CVS integration the
> following happens:
>
> "Error parsing cvs log: RCS filename
> '/opt/master/struct_common/.cvsignore,v' does not start with the provided
> root '/opt/master/env_pdm' "
>
> '/opt/master' is the end part of CVSROOT and 'env_pdm' is the alias module
>
> In other words could there be an optional extra parameter that Jira would
> use to match against the 'cvs log' command's output instead of assuming
> that it's always the end part of CVSROOT + the given module name:
> '/opt/master' + 'env_pdm' = '/opt/master/env_pdm' ??