11 comments
Comment actions Permalink

Works for me.

I am sure you ruled out plugins.

I am annoyed by the API break that caused several plug-ins to fail on 922.
Currently I am back to 915 until I have time to assess which ones don't work
and if I want to live without them until they get an update.

I would like to think that there's a smoother way to change APIs without
breaking compatibility. May be mark them internally as deprecated and issue
a warning on screen when a deprecated API was accessed (once)? Then we will
have the info but the transition to the new API will be smoother.

Just a thought,
Amnon

"Jordan Zimmerman" <jordanz@altura.com> wrote in message
news:bjl4tj$sko$1@is.intellij.net...

Am I the only one? I haven't been able to use any of the 9xx builds. I get
an assert on every mouse move (even with plugins removed).

>

http://www.intellij.net/tracker/idea/viewSCR?publicId=15914

>

--
Jordan Zimmerman
http://www.jordanzimmerman.com

>
>


0
Comment actions Permalink

922 keeps throwing exceptions when i try and open files, but 915 is working fine for me.

0
Comment actions Permalink

I believe this is because of the API change and some plug-ins.

"Andre Mermegas" <no_mail@jetbrains.com> wrote in message
news:30093318.1063139745011.JavaMail.itn@is.intellij.net...

922 keeps throwing exceptions when i try and open files, but 915 is

working fine for me.


0
Comment actions Permalink

I've removed all my plugins.

--
Jordan Zimmerman
http://www.jordanzimmerman.com

"Amnon I. Govrin" <agovrin@freshwater.com> wrote in message
news:bjlhdu$oej$1@is.intellij.net...

I believe this is because of the API change and some plug-ins.

>

"Andre Mermegas" <no_mail@jetbrains.com> wrote in message
news:30093318.1063139745011.JavaMail.itn@is.intellij.net...

922 keeps throwing exceptions when i try and open files, but 915 is

working fine for me.

>
>


0
Comment actions Permalink

After trashing every conceivable cache and rebuilding my project, 922 is now
working. What a pain...

--
Jordan Zimmerman
http://www.jordanzimmerman.com


0
Comment actions Permalink

Come on! This is how it works. They must be allowed to change vital parts of the system between EAP builds.

So this should be the natural procedure for the installation of a new EAP build:
1. Rename the directory of the old build from "Aurora" to "Aurora-]]>"
2. Create a new directory "Aurora"
3. Unpack the current build to the new directory
4. If there is a new jre for this build, download it and unpack it into the same directory. If there is no new jre, copy the jre from the previous build into the current build.
5. Backup and delete the configurations.
6. Start IDEA, configure it, close it.
7. Copy your codestyles and live templates from the backup into the config folder.

I do this with every build and it takes me less than 30 minutes and spares me posting bugs that are no real bugs. It's also less frustrating this way.

0
Comment actions Permalink

Jordan Zimmerman wrote:

Am I the only one? I haven't been able to use any of the 9xx builds.
I get an assert on every mouse move (even with plugins removed).

>

http://www.intellij.net/tracker/idea/viewSCR?publicId=15914


The 915 && 922 builds sucks. I cannot create a project (neither opening the
old one). Also, error sending does not work(why they don't gave a more
detailed error message???). I attach the idea.log...maybe someone will use
it.

Regards, Dudu





Attachment(s):
idea.log
0
Comment actions Permalink

Try to rebuild your local vcs (clear "vcs" directory in the IDEA system
folder)

--
Best regards,
Olesya Smirnova
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"


"dudu" <ionut.pascaniuc@viper-systems.com> wrote in message
news:bjmipg$tk5$1@is.intellij.net...

Jordan Zimmerman wrote:

Am I the only one? I haven't been able to use any of the 9xx builds.
I get an assert on every mouse move (even with plugins removed).

>

http://www.intellij.net/tracker/idea/viewSCR?publicId=15914

>

The 915 && 922 builds sucks. I cannot create a project (neither opening

the

old one). Also, error sending does not work(why they don't gave a more
detailed error message???). I attach the idea.log...maybe someone will use
it.

>

Regards, Dudu

>
>
>


0
Comment actions Permalink

I have to agree completely. I used to have tons of problems because I would
try to install in the existing directory or import settings. Forget that.

I install fresh every time. I have only had one problem since then and
that was caused by opening a project with 3.0.x. What a pain. I hate to
delete EVERYTHING to get it to perform correctly.


"Robert F. Beeger" <no_mail@jetbrains.com> wrote in message
news:21912.1063177022053.JavaMail.itn@is.intellij.net...

Come on! This is how it works. They must be allowed to change vital parts

of the system between EAP builds.
>

So this should be the natural procedure for the installation of a new EAP

build:

1. Rename the directory of the old build from "Aurora" to

"Aurora-]]>"

2. Create a new directory "Aurora"
3. Unpack the current build to the new directory
4. If there is a new jre for this build, download it and unpack it into

the same directory. If there is no new jre, copy the jre from the previous
build into the current build.

5. Backup and delete the configurations.
6. Start IDEA, configure it, close it.
7. Copy your codestyles and live templates from the backup into the config

folder.
>

I do this with every build and it takes me less than 30 minutes and spares

me posting bugs that are no real bugs. It's also less frustrating this way.


0
Comment actions Permalink

I just use the full install every time and import settings. From what I read
it seems a safer thing to do. When I am OK with the new build I simply
delete the old build directory.

This is EAP, living on the edge :)

"Robert F. Beeger" <no_mail@jetbrains.com> wrote in message
news:21912.1063177022053.JavaMail.itn@is.intellij.net...

Come on! This is how it works. They must be allowed to change vital parts

of the system between EAP builds.
>

So this should be the natural procedure for the installation of a new EAP

build:

1. Rename the directory of the old build from "Aurora" to

"Aurora-]]>"

2. Create a new directory "Aurora"
3. Unpack the current build to the new directory
4. If there is a new jre for this build, download it and unpack it into

the same directory. If there is no new jre, copy the jre from the previous
build into the current build.

5. Backup and delete the configurations.
6. Start IDEA, configure it, close it.
7. Copy your codestyles and live templates from the backup into the config

folder.
>

I do this with every build and it takes me less than 30 minutes and spares

me posting bugs that are no real bugs. It's also less frustrating this way.


0
Comment actions Permalink

EAP - Edge of Application Production :)


0

Please sign in to leave a comment.