Hello Andreas!
The module loader doesn't add jars listed in the manifest file to the
classpath. That is an issue. It can probably be fixed in the module loader
unless we would like to spend that effort on replacing the module loader
with the plugin-handling from Eclipse that already solves all these
problems.
Until fixed this is how I see it handled. There is essentially four
different problems:
1. When running ArgoUML with the C++ module from within Eclipse.
2. When running ArgoUML from the build.xml in the argouml-cpp project.
3. When running ArgoUML with the C++ module from the argouml project.
4. When running the release of ArgoUML.
The solutions are the following:
1. Add the jar to the "ArgoUML with C++"-configuration that you have
created. This shouldn't really be needed since the jar is already provided
by the project.
2. Add the jar to the classpath used by the "run" or "debug" targets.
3. (This is the tough one:) You need to explicitly list the jar on the
class-path. If you run from the "run" target in build.xml, then this isn't
possible. Should we add build/ext/*.jar to that?
4. The manifest of the argouml.jar needs to be changed to include the jar
file.
Is it one of these you have a problem with or something else entirely?
/Linus
2008/6/4, "Andreas Rückert" <[EMAIL PROTECTED]>:
>
> > Concerning jcpp integration into ArgoUML I think it should be possible
> > for modules to declare additional jars that must be loaded or, if it
> > isn't we should create an issue for the ArgoUML module loader to support
> > it.
>
> That's what I tried. Declared the jcpp jar in the module's manifest, but
> since
> there isn't even a ext/lib directory, or so, and all the other jars are in
> the lib
> dir, it's very likely, that this feature is simply not implemented in Argo.
> [...]
>
