lots of errors when updating library jars

Hello,

One thing the Aurora build handles very badly in comparison to the previous
Ariadna version, is the reaction on external updates of a jar file.

Sometimes I update such a .jar file (in my project classpath) with e.g. an
ant build script launched from the command prompt. In my projects I always
get a lot of NPE, AssertionFailedExceptions, ... Also if I have a source
file opened in the editor which uses this classes, suddenly all these
declarations are highlighted in red because IDEA can't find the classes
anymore, and import intentions start popping up to find these classes.

The only solution is to close all projects and restart IDEA to fix the cache
corruption.

When will this be fixed? And have you noticed simular behavior?

Willem


3 comments
Comment actions Permalink

--redacted-- wrote in message
news:blu20k$cj3$1@is.intellij.net...

Hello,

>

One thing the Aurora build handles very badly in comparison to the

previous

Ariadna version, is the reaction on external updates of a jar file.

>

Sometimes I update such a .jar file (in my project classpath) with e.g. an
ant build script launched from the command prompt. In my projects I always
get a lot of NPE, AssertionFailedExceptions, ... Also if I have a source
file opened in the editor which uses this classes, suddenly all these
declarations are highlighted in red because IDEA can't find the classes
anymore, and import intentions start popping up to find these classes.

>

The only solution is to close all projects and restart IDEA to fix the

cache

corruption.

>

When will this be fixed? And have you noticed simular behavior?


I have the same problem. It's really nasty. This certainly does not happen
in the Ariadna version. One solution I found was that when using ANT to
build the JAR file the problem happened less often. Not sure what is
different from building the jar via ant and on the command line but I
noticed that it works a bit better and you don't get the error that much
(Just close and reopen the class file and it works!). Still I hope someone
fixes this.

Regards,
Steve.


>

Willem

>
>


0
Comment actions Permalink

One solution I found was that when using ANT to
build the JAR file the problem happened less often. Not sure what is
different from building the jar via ant and on the command line but I
noticed that it works a bit better and you don't get the error that much


All my .jar files are created with ant, and I have the errors most of the
time.
I don't think this makes a lot of difference.

Willem


0
Comment actions Permalink

When will this be fixed? And have you noticed simular behavior?


My idea had some of this symptoms, and 944 fixed it for me.


0

Please sign in to leave a comment.