2008/6/6 Linus Tolke <[EMAIL PROTECTED]>: > I don't think that having jars in separate directories will prevent them > from being confused since they, with the current solution, will have to be > on the global class path anyway. It is better then to see the conflicts > already in the jar names.
We don't have control of all modules, only the ones owned by the ArgoUML project. We have no idea what jars those modules may require and how they may conflict. In order to protect users from conflicts in external modules I don't see any other solution than to clearly separate the modules. > If we should get something from Eclipse, I again suggest that we grab the > whole solution with interfaces, control files together with the > implementation. I assume that we will then get this problem solved too. Isn't what I'm suggesting a migration towards that? We have to start somewhere. > As it is now, adding an extra directory will affect the release scripts so I > suggest that we wait until there is an actual problem to be resolved (i.e. > when two module needs two different versions of antlr or something). I thought there was a problem with ANTLR versions but then I haven't been following those talks too closely. Maybe that is resolved. Perhaps you missed this comment >> I'd hesitated to suggest this before as I didn't want to see modules >> forced to repackage themselves. However we could have our module >> discovery code deal with both the current situation and the structure >> described above. So we can allow for this but nothing has to change in the release unless we then take another decision to migrate to the proposed directories. Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
