Hello Linus,
OK, I understand now the full thing. The configuration I was missing was
(from the cookbook section you pointed out):
<quote>
*
Set the workspace default file for ant to
tools/eclipse/eclipse-ant.properties.
Window => Preferences, Ant -> Runtime Properties and add a Global
property file
|${workspace_loc:/argouml-core-tools/eclipse/eclipse-ant.properties}|.</quote>
Now one thing is important to note: the description you provide in the
cookbook link and the build.xml files are correct if the
checkout was made by importing the eclipse team project sets. If the
checkout was made by the command line, due to the different
directory structure, the build (specifically generating the parser) in
eclipse won't work. In this case, we need to override the default
properties and at least define value of antlrall.jar.path to the ArgoUML
library, but, as "${project_loc:argouml-app}/lib/antlrall-2.7.2.jar"
BTW, if in the global property file we have
antlrall.jar.path=${project_loc:argouml-app}/lib/antlrall-2.7.2.jar
instead of
antlrall.jar.path=${workspace_loc}/argouml-app/lib/antlrall-2.7.2.jar
it works for both cases.
Do you agree if I commit the change?
Regards and thanks for your instructions,
Luís
PS: future comments/ideas from me on this issue will go to issue 4625.
Linus Tolke wrote:
Hello Luis!
This is strange. I have managed to start using the ArgoUML
configuration. I think the transformation instructions can be
forgotten about soon.
Tonight, the Cookbook builds again so you can see my terse description
on how to set up for building modules at the bottom of
http://argouml-stats.tigris.org/documentation/defaulthtml/cookbook/ch02s08.html#d0e2827.
I will have another look at the problems tonight.
/Linus
2008/2/19, Luis Sergio Oliveira <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
Linus Tolke wrote:
Hello all!
I have now managed to get the Eclipse build working. I have used
the PDE Tools and manifest editing to a large extent to handle
dependencies. Most of this work was already done so it was just a
matter of adapting to the new eclipse projects and adjust
dependencies.
Here is what you need to do to update your Eclipse environment:
* Make sure you don't have any uncommitted work. If you do,
you will loose it by the steps below.
* Remove the following Eclipse projects:
argouml
argouml-core-lib
argouml-core-tests
(missing dependencies will show up as errors).
* Download the new psf file and Import it (you can press No
to all) to save downloading time.
* Remove the argouml-core-model-mdr/build directory (I
thought I would be able to remove this. I was wrong so I
put it back).
* Update all Eclipse projects!
You also have the option to start over using the psf file in a
new workspace or after having erased all projects. That might be
simpler.
/Linus
Hi Linus,
I'm now testing your recipe above. To make a clean test I started
with a new empty eclipse workspace and imported the
argouml-core-projectset.psf
It all worked well, but, when I run the ArgoUML configuration it
failed with the error:
"org.argouml.model.mdr.MDRModelImplementation is not a working
Model implementation."
The testing of the "argouml-modules-projectset.psf" checkout in
the same clean environment results in the errors Bob talks about
in other email:
"Buildfile: .../svnco3/argouml-module-idl/build.xml
init:
prepare:
[echo] Preparing the build directories
generateparser:
[echo] Generate parsers using ${antlrall.jar.path}
[java] java.lang.NoClassDefFoundError: antlr/Tool
[java] Exception in thread "main"
BUILD FAILED
.../svnco3/argouml-module-idl/build.xml:83: Java returned: 1
Total time: 751 milliseconds"
Regards,
Luís
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> For additional
commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
