Thomas N. schrieb:
Hi Alexander!
I integrated Antlr3 in the Java module, so I think you do not need all those 4
jar files. You need antlrworks-1.1.7.jar for development and building, and you
need antlr-runtime-3.0.1.jar only for the deployment and runtime. Please look
how I do it in the Java module, I'm creating a manifest file for the
argo-java.jar from that in argouml-java\src\org.
antlrworks is not needed for development. of course it's nice and shiny
and makes antlr the coolest tool in it's genre(my 0.02€), but it's not
needed. i won't put it in lib/ of the python project since there's no
dependence.
i'm using antlr v3 for the argouml-python project. i did not check in the jars
for antlr, because i thought they would appear somewhere in core-lib.
Please let's not have it in the core. It's just for the modules and should be
NOT included in the core!
you're right, antlr has nothing to do with argouml itself, so it does
not belong there. but it's the only available place(see below).
when two modules provide their own jars, they might clash with their
versions.
No, because the Antlr files (at runtime only antlr-runtime-3.0.1.jar) has the
version number in it's name and is explicitely referenced in the module's jar
file, as mentioned above!
i don't think that a vm that runs argo would load different versions of
the jars, since the modules won't run in different vm's with different
classpaths. i think there's only one org.antlr.* namespace in the
running vm, from the first or the last loaded jar that contains it, but
that's pure speculation.
from my point of view it would be more nice to keep them central.
No, I disagree!!! If two modules use the same lib jars, then this is not a
reason for putting them in the core. It may happen and has nothing to do with
the core ArgoUML.
no, it would be the reason to put them into a common library path, which
don't exists.
regards,
alexander
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
