[Andromda-user] [Newbie corner] [cvs] cvs

2005-07-03 Thread tequila
im setting my project up in eclipse. should i add the generated files to .cvsignore? whats the best way of dealing with changing generates and cvs? r _ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2063#2063 Posting t

[Andromda-user] [Cartridge development] [I can't find the test failure report]

2005-07-03 Thread [EMAIL PROTECTED]
Quote: I found the problem and it made appear that the implementation of this javadoc improvement is going to be far more difficult than I thought because there are plenty of tests that are going to fail. (end of quote) well, that's the purpose, right ? for every cartridge the tests are go

[Andromda-user] [Installation & Configuration] [cvs]

2005-07-03 Thread [EMAIL PROTECTED]
if you using the andromdapp:generate tool you will see that the generated code mostly goes into a target subdirectory, so just put a .cvsignore file in the parent directory and add target to it, you should never check in those files some files go into the src subdirectory, this means they are

[Andromda-user] [Cartridge development] [I can't find the test failure report]

2005-07-03 Thread sebastien
[EMAIL PROTECTED] wrote: Quote: I found the problem and it made appear that the implementation of this javadoc improvement is going to be far more difficult than I thought because there are plenty of tests that are going to fail. (end of quote) well, that's the purpose, right ? for every

[Andromda-user] [Cartridge development] [I can't find the test failure report]

2005-07-03 Thread [EMAIL PROTECTED]
sebastien wrote: it can be interesting to generate documentation for other documentation systems like doxygen for example. So why not define a base interface named DocumentationGenerator with method like getClassifierDocumentation, getMethodDocumentation, getParameterDocumentation and so one,

[Andromda-user] [Cartridge development] [I can't find the test failure report]

2005-07-03 Thread sebastien
[EMAIL PROTECTED] wrote: yeah it's definitely worth the effort, can you write something that will work (+ junit tests) ? then we'll take a look at applying it to the codebase together with the other AndroMDA developers that are interested thanks for all the efforts so far! (end of quote)