I've given up on it, and gone back to the pukka release version for work. It was scribbling over projects, throwing up error messages non-stop, and eventually refused to display any tool windows or tool window bars at all. I could probably have deleted the project files and the caches and got it working again, but I had work to do, and it just didn't seem worth it...
Well, the EAP versions cannot be called "stable", but there should be at least each second or third, that is "quite stable". Otherwise the EAP fails, because no one tries it. EAP is only valuable, if the versions have a minimum stability.
That's why I suggested some time ago to make following:
1) release an "experimental" build 2) try to fix as much as possible/necessary bugs reported for this experimental build 3) release an "unstable" build 4) implement new features 5) start at 1)
I believe, this is the best approach, for you (JetBrains) and us (the testers). What do you think?
Well, the EAP versions cannot be called "stable", but there should be at least each second or third, that is "quite stable". Otherwise the EAP fails, because no one tries it. EAP is only valuable, if the versions have a minimum stability.
I find that the EAP versions are usually stable enough for me to use all day. Specifically, all of the Aurora versions have been stable enough for me.
Just in case, I keep the installers for a bunch of the older versions around, plus I have the latest production version installed. And I check my code in to source control before installing a new version, just to be extra-safe.
>>Well, the EAP versions cannot be called "stable", but there should be >>at least each second or third, that is "quite stable". Otherwise the >>EAP fails, because no one tries it. EAP is only valuable, if the >>versions have a minimum stability.
I find that the EAP versions are usually stable enough for me to use all day. Specifically, all of the Aurora versions have been stable enough for me.
I have not been able to use any of the Aurora EAP builds yet. 802 couldn't open any source files without a continuous internal error. I didn't try 804. 807 apparently couldn't find java.lang.String, etc. even though the JDK appeared to be properly configured and selected for that project. I had work to do so I didn't fiddle with it anymore but I'm going to try deleting the separate system directory I keep for the EAP builds that I install.
Just in case, I keep the installers for a bunch of the older versions around, plus I have the latest production version installed. And I check my code in to source control before installing a new version, just to be extra-safe.
I have IDEA 3.0.2 installed once and the current EAP unpacked in a separate directory. I keep 3 sets of separate config and system directories: 1) Main set used by 3.0.2 for doing majority of my work, 2) Duplicate of main set for starting a second instance of IDEA to test plugins, 3) EAP set. So I don't need to uninstall/reinstall anything.
Ciao, Gordon
-- Gordon Tyler (Software Developer) Quest Software <http://java.quest.com/> 260 King Street East, Toronto, Ontario M5A 4L5, Canada Voice: 416-643-4846 | Fax: 416-594-1919
The key for me to make the 80X work was to re-create my project. I had enormous problems with the migration (which I submitted and I believed are not fixed yet) that triggered an endless stream of exception. Just try another time from a clean project this time. Other than that I think this new EAP is on par with the old one: it is stable to do production development on.
> >>Well, the EAP versions cannot be called "stable", but there should be >>at least each second or third, that is "quite stable". Otherwise the >>EAP fails, because no one tries it. EAP is only valuable, if the >>versions have a minimum stability. >
I find that the EAP versions are usually stable enough for me to use all day. Specifically, all of the Aurora versions have been stable enough
for
me.
>
I have not been able to use any of the Aurora EAP builds yet. 802 couldn't open any source files without a continuous internal error. I didn't try 804. 807 apparently couldn't find java.lang.String, etc. even though the JDK appeared to be properly configured and selected for that project. I had work to do so I didn't fiddle with it anymore but I'm going to try deleting the separate system directory I keep for the EAP builds that I install.
>
Just in case, I keep the installers for a bunch of the older versions around, plus I have the latest production version installed. And I check
my
code in to source control before installing a new version, just to be extra-safe.
>
I have IDEA 3.0.2 installed once and the current EAP unpacked in a separate directory. I keep 3 sets of separate config and system directories: 1) Main set used by 3.0.2 for doing majority of my work, 2) Duplicate of main set for starting a second instance of IDEA to test plugins, 3) EAP set. So I don't need to uninstall/reinstall anything.
>
Ciao, Gordon
>
-- Gordon Tyler (Software Developer) Quest Software <http://java.quest.com/> 260 King Street East, Toronto, Ontario M5A 4L5, Canada Voice: 416-643-4846 | Fax: 416-594-1919
Pretty buggy. Only release version could be claimed as stable.
--
Best regards,
Maxim Shafirov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"
"Travis Reeder" <travis@thinkvirtual.com> wrote in message
news:18101780.1048622745658.JavaMail.jrun@is.intellij.net...
I've given up on it, and gone back to the pukka release version for work. It
was scribbling over projects, throwing up error messages non-stop, and
eventually refused to display any tool windows or tool window bars at all. I
could probably have deleted the project files and the caches and got it
working again, but I had work to do, and it just didn't seem worth it...
"Travis Reeder" <travis@thinkvirtual.com> wrote in message
news:18101780.1048622745658.JavaMail.jrun@is.intellij.net...
Hi,
Well, the EAP versions cannot be called "stable", but there should be
at least each second or third, that is "quite stable". Otherwise the
EAP fails, because no one tries it. EAP is only valuable, if the
versions have a minimum stability.
That's why I suggested some time ago to make following:
1) release an "experimental" build
2) try to fix as much as possible/necessary bugs reported for this
experimental build
3) release an "unstable" build
4) implement new features
5) start at 1)
I believe, this is the best approach, for you (JetBrains) and us (the
testers). What do you think?
Cheers,
Tom
"Thomas Singer" <idea@regnis.de> wrote in message
news:86n28vcnrc6d5u406d1ltaeliktbks9ee4@4ax.com...
I find that the EAP versions are usually stable enough for me to use all
day. Specifically, all of the Aurora versions have been stable enough for
me.
Just in case, I keep the installers for a bunch of the older versions
around, plus I have the latest production version installed. And I check my
code in to source control before installing a new version, just to be
extra-safe.
Erik Hanson
Erik Hanson wrote:
>>Well, the EAP versions cannot be called "stable", but there should be
>>at least each second or third, that is "quite stable". Otherwise the
>>EAP fails, because no one tries it. EAP is only valuable, if the
>>versions have a minimum stability.
I have not been able to use any of the Aurora EAP builds yet. 802
couldn't open any source files without a continuous internal error. I
didn't try 804. 807 apparently couldn't find java.lang.String, etc. even
though the JDK appeared to be properly configured and selected for that
project. I had work to do so I didn't fiddle with it anymore but I'm
going to try deleting the separate system directory I keep for the EAP
builds that I install.
I have IDEA 3.0.2 installed once and the current EAP unpacked in a
separate directory. I keep 3 sets of separate config and system
directories: 1) Main set used by 3.0.2 for doing majority of my work, 2)
Duplicate of main set for starting a second instance of IDEA to test
plugins, 3) EAP set. So I don't need to uninstall/reinstall anything.
Ciao,
Gordon
--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919
The key for me to make the 80X work was to re-create my project. I had
enormous problems with the migration (which I submitted and I believed are
not fixed yet) that triggered an endless stream of exception. Just try
another time from a clean project this time.
Other than that I think this new EAP is on par with the old one: it is
stable to do production development on.
Jacques
"Gordon Tyler" <gordon.tyler@sitraka.com> wrote in message
news:b5sm6j$1rf$1@is.intellij.net...
for
>
>
my
>
>
>
>