Hello Tom, I created an Issue and added the patches. http://argoeclipse.tigris.org/issues/show_bug.cgi?id=13
:) I didn't work previously with patches, so please tell me if they are Ok. Bogdan I committed already the code to ArgoEclipse, but it misses the patches from ArgoUML projects. On 4/3/07, Bogdan Ciprian Pistol <[EMAIL PROTECTED]> wrote:
Thanks for the quick reply Tom, Your comments helped me better understand the issues. I believe that Eclipse buddies will help momentarily ArgoEclipse. In the end, when the ArgoUML structure will be done, these artifacts can be removed... but there are some things that won't work even then. Log4j for example needs access to the caller plugin (suppose Log4j is in a separate plugin) The static blocks of code won't run if their classes are accessed from another plugin (these can be solved by converting them in a static method and a singleton should run that method only once) > I'm not sure that the ArgoUML "standard way" isn't wrong. Yes, you're right. It does seems a bit weird that the Model API initialize itself with the Model MDR implementation (that implements exactly the Model API) > I'm not sure I fully understand this. Is there someplace that describes > Eclipse buddies in more detail? Check out this article: http://www.eclipsezone.com/articles/eclipse-vms/ > The mailing list is good for general discussions, but patches attached to an > issue in the bug database provide a more focused discussion among those > interested. I think we need to make better use of the ArgoEclipse issue > database, so perhaps this would be a good opportunity to start with. So I should create issues in the ArgoEclipse database and attach patches there. Ok, thanks. Bogdan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
