Re: [ jEdit-devel ] plugin dependencies, was [Fwd: [ jedit-Plugin Central Submission-1765867 ] JavaSideKick 2.3.5 ready for release]

[Alan E. <ala...@gm...>]

[forwarding to list, I accidentally forgot reply-all]


The transitive closure problem should by handled by jEdit Plugin
Manager, and any script that is used for plugin packaging.

Jeff, Are these PHP scripts in SVN?  If not, perhaps they should be,
and then we can open op development to the team on it.

As long as the dependencies are set that PluginManager can understand
the relationships between all the dependencies, I  agree with
Marcello, Dale: the redundancy is not needed or desireable, so I take
back my statement about the CommonComontrols being an optional
dependency of JavaSideKick..


On 8/5/07, Dale Anson <da...@gr...> wrote:
> :) Forwarding to the developer list, it seems to me that's a better
> forum to discuss the general situation of plugin dependencies rather
> than in a tracker for a plugin release...
>
> I'm tending to agree with Marcelo on this.  It kind of like java
> classes, if class A depends on class B and class B depends on class C, I
> don't need to import class C in class A since B will handle that for me.
>
> Who wrote the python scripts that do the build?  Who's the expert that
> could fix them and check on the dependencies?  Has anyone looked at
> Ivy?  The build guys at my last company loved it as it easily managed
> dependencies.  Maybe it's time to scrap the python scripts (assuming
> there is no one to maintain them) and go with something java based that
> might be better supported by the jEdit developers?
>
> Oh, and I'm still not clear, do I need to include CommonControls in
> JavaSideKick or not?!
>
> Thanks,
>
> Dale
>