cc'ing this to the devel list since it's of interest to all developers

On Fri, Jan 29, 2010 at 7:35 AM, Damien Radtke <> wrote:
The way I see a dependency pane being structured involves pretty basic

- A list of required files
Why a separate list of files and not just a list of directories as below? Is this also necessary?

 - A list of required directories (or source trees)
    - A build directory
    - A source directory

The first two are basically what's in the current dependencies pane,
but simplified. A project requiring a java classpath could simply add
necessary .jar files to the first list.

Any classpath and jar-specific stuff should go into the javasidekick's classpath option pane, no?

The last two are influenced by
 javasidekick's classpath settings pane,

And should go there, probably. Who would need to use classpath, etc, and NOT be using javasidekick also?
but I can think of some
potential situations where plugins would be interested in knowing
where the current project's main source is stored and where its final
product will be generated. An option to specify a lib directory could
also be considered, so that some necessary files could just be
transferred to there rather than added manually to the first list.

Lib directory? What kind of lib? I am not sure I understand what you mean by that.


On 1/29/10, Marcelo Vanzin <> wrote:
> On Thu, Jan 28, 2010 at 11:35 PM, Shlomy Reinstein <>
> wrote:
>> I have un-assigned myself because I have no time for this now. When I
>> have some free time I will reassign it to myself if it's still
>> relevant.
>> Marcelo, why doesn't this (project dependencies pane) belong in the PV
>> plugin itself?
> Having just plain dependencies in Project Viewer might make sense. I
> just don't know how useful that feature by itself would be. You still
> need some interesting data in the projects you depend on (such as a
> classpath, let's say), and that sort of information doesn't belong in
> PV itself.
> --
> Marcelo Vanzin
> "Life's too short to drink cheap beer."