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.
> >> 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! > 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! > 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. > > Unless the files are huge, I think it would be better to have each > > individual module distribute their own so that they can manage version > > dependencies independently. I believe that even if the file ARE huge, they shouldn't be put into the core lib just for that reason. Then two modules ARE big, I see no problem with that. Regards, Thomas -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
