Hi, Tom
Thanks for your response.
I tried out your advices a indeed i could remove all but one error.
I found it due to an incompatible gef version requirement in
argoeclipse-core/build.properties
I included the patch although it most probably is irrelevant. But who knows at
the end ;-)
Anyways i could compile and launch an argoeclipse enabled eclipse app, but then
trouble started.
I got all sorts of exceptions and to tell in the short, i was not able to do
any significant operation
with argoeclipse.
I'd like to do some helping, but i'm afraid i will not be able to help in
coding, but definitely
i'd like to help in testing. So maybe you could give a short note when it makes
sense to grab
a newer version of the sources. i'll then go and proceed .
BTW it would be very helpfull if you'd give some infos about how the final
plugin zip file can be
generated from the sources so that i can hand over a pacakged version of
argoeclpise to some analysts
who like to contribute in testing.
thanks again for your help
regards, hussayn
Tom Morris schrieb:
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]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
tel.: +49 221 560 11 0
fax.: +49 221 560 11 20
mailto:[EMAIL PROTECTED]
http://www.saxess.de
http://www.saxess.com
http://www.saxess.org
Index: build.properties
===================================================================
--- build.properties (revision 428)
+++ build.properties (working copy)
@@ -3,4 +3,4 @@
plugin.xml,\
plugin.properties,\
.
-jars.extra.classpath = platform:/plugin/org.argouml.core.lib/gef-0.12.1.jar
+jars.extra.classpath = platform:/plugin/org.argouml.core.lib/gef-0.12.2a.jar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
