Warning: #5162 damages 5.1-Projects!

Fixed in 5.1.1

Sascha Weinreuter wrote:

Just a heads up, do NOT open important 5.1 projects in Demetra or you might have
a lot of fun fixing them.

If it has already happened and IDEA doesn't load the project any more, open the
.iws file and add the attribute "splitterProportion='0.5'" to the "navigator"
element of the "ProjectView" component:

<component name="ProjectView">
<navigator currentView="ProjectPane" splitterProportion="0.5">
...

Sascha

java.lang.NullPointerException
at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)
at java.lang.Float.parseFloat(Unknown Source)
at
com.intellij.ide.projectView.impl.ProjectViewImpl.readExternal(ProjectViewImpl.java:118)
at
com.intellij.openapi.components.impl.ComponentManagerImpl.doInitJdomExternalizable(ComponentManagerImpl.java:98)

--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

Workaround: delete iws-file.

Tom

Tom wrote:

Workaround: delete iws-file.

this can be just as bad as having to recreate the whole project if you lose
several tuned run-configurations :(

Sascha

At least for me it helped to continue working this morning. Unfortunately
the Rearranger plug-in does not work with Demetra...

Tom

That would be a good reason to always use a copy of one's projects when fiddling with th EAP builds.

Where can I get version 5.1.1?

Thanks!

Yeah, I make periodic copies of my project files for this reason. Then I don't really care if the EAP horks my project file. It's also nice to keep a copy on the off chance that the release version corrupts it.

"Sascha Weinreuter" <sascha.weinreuter@NOSPAM-cit.de> wrote
in message news:dthhmf$sgo$1@is.intellij.net...

Just a heads up, do NOT open important 5.1 projects in

Demetra or you might have

a lot of fun fixing them.

http://joelonsoftware.com/articles/fog0000000036.html

"Now, Mr. Rogers over at Well-Tempered Software Company
(colloquially, "WellTemperSoft") is one of those nerdy
organized types who refuses to write code until he's got a
spec. He spends about 20 minutes designing the backwards
compatibility feature the same way Speedy did, and comes up
with a spec that basically says:

When opening a file created with an older version of the
product, the file is converted to the new format.

The spec is shown to the customer, who says "wait a minute!
We don't want to switch everyone at once!" So Mr. Rogers
thinks some more, and amends the spec to say:

When opening a file created with an older version of the
product, the file is converted to the new format in memory.
When saving this file, the user is given the option to
convert it back.
Another 20 minutes have elapsed.

Mr. Rogers' boss, an object nut, looks at this and thinks
something might be amiss. He suggests a different
architecture.

The code will be factored to use two interfaces: V1 and V2.
V1 contains all the version one features, and V2, which
inherits from V1, adds all the new features. Now V1::Save
can handle the backwards compatibility while V2::Save can be
used to save all the new stuff. If you've opened a V1 file
and try to use V2 functionality, the program can warn you
right away, and you will have to either convert the file or
give up the new functionality."