|
| Re: [Acceleo] Naming conflicts in modules [message #506428 is a reply to message #505824] |
Thu, 07 January 2010 09:16  |
|
This is a multi-part message in MIME format.
--------------010405060603040305060309
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Sebastien,
You cannot name the modules A.common or B.common, yet you can name them
A::common and B::common and then import them both with the same
convention. That is the only workaround when dealing with like-named
modules.
Laurent Goubet
Obeo
Sebastien Roy wrote:
> Hello,
>
> I would like to know if there is a way to avoid conflicts in mtl modules
> / queries / templates naming.
>
> In java, naming conflicts are resolved using packages names, but I
> didn't found this concept in Acceleo.
>
> If I have a project A that defines a module "common" and a project B
> that defines another module "common", how can I use both modules in a
> project C ?
> I can even not rename them into "A.common" and "B.common" because the
> module name must be equal to the filename.
>
> Is there a workaround for that kind of conflict ? Something planned for
> the future ? A naming convention to prevent conflicts ?
>
> Regards
>
> Sebastien
--------------010405060603040305060309
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"
YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------010405060603040305060309--
|
|
|
Powered by
FUDForum. Page generated in 0.02654 seconds
] 
Search
Help
Register
Login
Home
