Hi Dr. Dabbous, Thanks for trying ArgoEclipse and sorry for the problems.
> 1.) (minor problem) I could NOT get eclipse to import the > team project set as provided on your site. > Since this has nothing to do with argoeclipse i just > keep this here for informal purpose. There have been other reports of checkout problems with new installations. I think one thing which *may* help, is to create a SVN Repository definition for the ArgoEclipse repository before attempting to import the projects. Due to some SVN/Subclipse issues, this seems to help. There's another problem with the current project definitions though. We switched over to using the ArgoUML trunk (from a private branch) over the weekend and I haven't updated the project definitions to reflect that yet. I'll do that immediately. > I then browsed through the code and found indeed some > obviously broken java references. > > May it be that your last update on trunk from 10.12.2006 > unintentionally broke things ? I suspect this is related to the switch from our private ArgoUML branch (work_argoeclipse_tfmorris), please switch your ArgoUML projects (5 of them) to the main trunk and see if that helps. The updates over the weekend included a fairly significant refactoring of the import source subsystem for ArgoUML and ArgoEclipse, so there may still be some issues, particularly on the ArgoEclipse side of things since I was focused on getting the ArgoUML side solid to meet their release deadline. The focus of the refactoring was making the subsystem GUI independent so that it can be used in ArgoEclipse without lots of duplication and extra work. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
