Hi!

-------- Original-Nachricht --------
> Datum: Fri, 6 Jun 2008 21:14:02 +0200
> Von: "Linus Tolke" <[EMAIL PROTECTED]>
> An: [email protected]
> Betreff: Re: [argouml-dev] C++ module preprocessor

--<snip>--
 
> 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?

I did 4 and was a happy camper until it was said, that the module should
provide the jar...

To 3: maybe the jar should rather go to something like ext/lib/ , or so, so 
it's clear, that this is not a module, but a lib used by a module. Or even
to separate the libs from each other to something like 
ext/argouml-cpp/lib/ or so? I know, makes loading harder...

4 is ok, unless someone (maybe a company, or so) want's to provide a module,
we are not even aware of. If all the modules (with libs) would require a 
modified
manifest, it'll be very complex to create a complete manifest. 

BTW: the above statement is just for the design fetishists on the dev list, 
since I don't believe, that such a module exists... :-)

Ciao,
Andreas

-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to