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.
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.
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).
/Linus
2008/6/6, Bob Tarling <[EMAIL PROTECTED]>:
>
> Andreas said:
> > ext/argouml-cpp/lib/ or so? I know, makes loading harder...
>
> In think again we have something to learn here from eclipse.
>
> With the single directory we have for module jars there is no way we
> can control two different modules from deciding to use the same jar
> name for themselves or conflicting with each other files.
>
> The eclipse plugins each go under their own separate directory and
> that directory name includes a dot separated URL owned by the plugin
> writers organisation.
>
> e.g. eclipse/plugins/de.mvmsoft.checkclipse_2.2.0 contains the
> checkclipse plugin.
>
> 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.
>
> That directory name could even by contain the name of the jar and
> class in which to find the module interface implementation or
> alternatively have it contain some XML description file as eclipse
> does.
>
> Bob.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
