A critical error in build 5368

In my module, I set classpath to an external JAR file. I try to delete it by navigating to that JAR file under the module item in Project Roots dialog, delete it. Then I can not open Project Roots dialog anymore.

Anyone has same problem?

8 comments
Comment actions Permalink

Hello,

Could you please describe your situation in more detail.

Thank you

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

In my module, I set classpath to an external JAR file. I try to delete
it by navigating to that JAR file under the module item in Project
Roots dialog, delete it. Then I can not open project anymore.



0
Comment actions Permalink

I can reproduce it everytime

+ Create a new project
+ Add an external JAR file to project's classpath
+ Choose the JAR file and click Detach
+ Click Apply then OK but Project Roots dialog cann't close and IDEA throws some exceptions. You must click Close to close the dialog.

Now you can't open Project Roots dialog for this project anymore.



Attachment(s):
RemoveJarFileBug.gif
0
Comment actions Permalink

Sounds like this: http://www.jetbrains.net/jira/browse/IDEADEV-6653 (Although I
reported it, I found it in JIRA by coincidence. There really needs to be a way
to keep track of one's own reported exceptions!)

Workaround: Look for the following block in module's .iml file and remove it:

]]>

Sascha



Attachment(s):
detach-jar-breaks-project.png
0
Comment actions Permalink

Hello,

Indeed I've never tried to detach a module library in such a way. I always
detach an order entry for it in classpath tab (as workaround it works fine)

Thank you.

-


Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

I can reproduce it everytime

+ Create a new project
+ Add an external JAR file to project's classpath
+ Choose the JAR file and click Detach
+ Click Apply then OK but Project Roots dialog cann't close and IDEA
throws some exceptions. You must click Close to close the dialog.
Now you can't open Project Roots dialog for this project anymore.



0
Comment actions Permalink

>There

really needs to be a way
to keep track of one's own reported exceptions!)


After you login to JIRA, the homepage will contain a default set of links, one of which is 'My Unresolved Reported Issues' or smth the like. Look at the bottom on the right.

Next, when you browse the project, there's a standard report link - 'Reported By Me'. This ones shows both resolved and unresolved ones.

HTH,
Andrew

0
Comment actions Permalink

Hello Andrew,

>> There
>> really needs to be a way
>> to keep track of one's own reported exceptions!)
AP> After you login to JIRA, the homepage will contain a default set of
AP> links, one of which is 'My Unresolved Reported Issues' or smth the
AP> like. Look at the bottom on the right.
AP>
AP> Next, when you browse the project, there's a standard report link -
AP> 'Reported By Me'. This ones shows both resolved and unresolved ones.

This will, however, not show the exceptions you have reported to the tracker.

Sascha: The posting of comments to ITN when a request is linked to a JIRA
issue was broken, not removed intentionally, and we hope to fix it soon.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

This also happened to me, and my .iml file looked like:

]]>

Removing it fixed the problem.

0
Comment actions Permalink

Dmitry Jemerov wrote:

Sascha: The posting of comments to ITN when a request is linked to a
JIRA issue was broken, not removed intentionally, and we hope to fix it
soon.


Unfortunately this was less than obvious because it broke like 4 months ago and
has been mentioned several times since...

While you're at it, you should make the whole error-reporting thing more
reliable and/or operate in the background because I don't feel like waiting
minutes for a report to finish. The response time is usually OK, but in like one
out of five times I try to report an error I have wait for it up to 2 minutes.
The last exception I tried to report blocked the IDE for more than 5 minutes and
failed with error 503. Please make this behave more gracefully in case of
network, etc. problems.

Sascha

0

Please sign in to leave a comment.