Deleting a directory removes it from the project: nice!

Keeps the project nice and tidy -- no more red path entries :)

6 comments
Comment actions Permalink

I haven't tested it, but what if you delete the directory and add it again
(e.g. in the case of refreshing a directory that contains required classes
from a central repository?)

It might be too automatic for its own good.

May be (if it's there I appologize) ask the user to remove it from the path
(i.e. if the user is in the middle of such an update he/she will click on
"No").

Amnon

"Barry Kaplan" <bkaplan@integratedtrading.com> wrote in message
news:bsq5a1$j6s$1@is.intellij.net...

Keeps the project nice and tidy -- no more red path entries :)

>


0
Comment actions Permalink

I don't this behavior.

Some of the projects I work on are over remotely mounted filesystems which are not always mounted.

What if I accidentilly open my project without having mounted the correct fileysystem? It sounds like IntelliJ will remove all my project configuration!

I would much rather this be optional behavior.

I had already filed a bug that the state of the Ant Build window is wiped out if the build.xml file is not accessible at startup. This seems like a related issue.

0
Comment actions Permalink

Hmm... I thought this one was because of the move to 1050.

I had a bunch of strange things when I closed my IntelliJ window (not killed
the process forcively) when it was loading. It closed and when I opened the
project with 1050 all the breakpoints and ANT files and open files were
forgotten. My ant files are local, not on the network.

Amnon

"Alex" <no_mail@jetbrains.com> wrote in message
news:10102577.1072741212000.JavaMail.itn@is.intellij.net...

I don't this behavior.

>

Some of the projects I work on are over remotely mounted filesystems which

are not always mounted.
>

What if I accidentilly open my project without having mounted the correct

fileysystem? It sounds like IntelliJ will remove all my project
configuration!
>

I would much rather this be optional behavior.

>

I had already filed a bug that the state of the Ant Build window is wiped

out if the build.xml file is not accessible at startup. This seems like a
related issue.


0
Comment actions Permalink

When I upgraded to 1050 from 1029, my Ant build window settings were preserved.

I can reproduce 100% of the time the problem over remote filesystems. If you start IntelliJ without mounting the filesystem, the Ant build window settings are lost.

0
Comment actions Permalink

Interesting. I guess that it wasn't the upgrade but instead the fact I
closed IJ in a very critical moment.

I'll revise my bug report.

Amnon

"Alex" <no_mail@jetbrains.com> wrote in message
news:30143277.1072746074436.JavaMail.itn@is.intellij.net...

When I upgraded to 1050 from 1029, my Ant build window settings were

preserved.
>

I can reproduce 100% of the time the problem over remote filesystems. If

you start IntelliJ without mounting the filesystem, the Ant build window
settings are lost.


0
Comment actions Permalink

Barry,

could you explain what exactly you mean by this?
(that is, exactly what functinality you praise? :))

Cheers,
Dmitry
Barry Kaplan wrote:

Keeps the project nice and tidy -- no more red path entries :)


--
Dmitry Lomov
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.