jEdit

I am trying it now, thanks. Since i couldn't find any options under the
plugin options, I wasn't sure where to set it, thanks for the
clarification.

By the way, I noticed whenever it does an auto-reimport, it collapses all
the nodes in the tree. Is there a way to avoid that?

I don't really know when I'll get to the point of release; it's not always
that I have time to make good progress on the code like this past weekend.

That being said, if you don't mind some oddities happening now and then,
and don't mind other plugins not necessarily working with PV, you could
probably survive using the trunk version. It would also help having more
people testing it. :-) Just be aware that if you switch, going back
requires some manual steps, since the new version changes the location of
configuration files.

When do you expect these changes to be released then, as they would really
ease my work flow from day to do

Philip, if you managed to compile the plugin, you can just place the
ProjectViewer.jar (it should be located in the parent directory of the
plugin's source tree) in your ~/.jedit/jars directory.

I don't recommend using PV trunk for day-to-day work, though. I use it
because I'm interested in figuring out the things that are currently broken
so I can fix them. But if you're just interested in using the plugin, it
can become quite a hassle to use the trunk version.

How do I go about using plugins from SVN, I have checked out PV, but where
do I place it in order to have it recognised by jedit

Alan, since I know you're running PV trunk (or at least update on a
regular basis to trunk), you can answer all those questions by looking at
the project's properties dialog, in the "Auto Reimport" section.

Is that an option one can switch on or off?

I use auto-import and i like that it has always detected files I create
from jEdit and automatically adds them to PV. So in my mind, that was what
'auto-import' meant before.
Now it means something else - it monitors the file system for new files
added by other processes.

Further, auto-detection of new files and adding to the project is
desireable only for non-binary files. I don't want to auto-import .class
files, .so files, or .pyc files. Does the auto-import also observe file
filter for importing if there was one? What if the file filter is CVS/SVN
entries?

PV trunk @ 13503 should have this working.

I concur, an option to allow ProjectViewer to monitor changes in the file
tree below the project root, or within any filesystem included in the
project, would make it much more useful, especially during project buildup,
e.g. when adding new modules to a Ruby on Rails project.

I am also looking for this functionality, and currently there is no option
that does this.

Nope. The behavior I'm looking for is this:

1) I'm working on a project in jedit
2) Outside of jedit I copy some files into a subdirectory of the project
3) I go back to jedit and magically the new files are already in the list
under the ProjectViewer "folder" view

I'd basically like projectviewer to monitor the directories of the project
for new files and import them automatically if they fit the "global import
options".

See: "Plugins ... Plugin Options ... Project Viewer ... Importing New
Files"

Is that what you want?