859 a dud?

Alright, I really hope it's just me...but is compiling from within IDEA broken for anyone else? jikes and javac both die with compiler internal error, exit code -13 and 115 respectively.

8 comments
Comment actions Permalink

works for me (using javac only).

Hani Suleiman wrote:

Alright, I really hope it's just me...but is compiling from within IDEA broken for anyone else? jikes and javac both die with compiler internal error, exit code -13 and 115 respectively.


0
Comment actions Permalink

Ok, cleared up if after I deleted the .dependency-info dir.

0
Comment actions Permalink

You got as far as compiling?

Glad to hear it. I can't even create a project with this thing.

I know that the EAP is supposed to be buggy, but this is getting beyond a joke.

It spent about ten minutes trying to load the project, even though it had an error message up on screen saying that it could not save it (I think a 'cancel' button is needed while the project is loading up for cases like this)

I wasn't to keen on this 'regular releases' lark to begin with, but from where I'm sitting, loads of new features are being stuffed into the core, and stability is getting worse with each new build. And that's before all the important stuff that has been removed, with no clue as to when it will (if ever) re-appear

I imagine this isn't the same for everyone, since I've seen a lot of praise being heaped on the EAP so far ... I'm just not seeing it anymore, which is a great shame.




0
Comment actions Permalink

Gosh. Just DON'T USE THE EAP builds.
Or else stop whining and start to help Intellij by checking the log file, checking the tracker database and create new tracker entries for things that don't work for you.
Often deleting Idea's cache, dependency info or even the complete settings and recreating the project will do the job. That's why it is EAP, see? Also be sure to completley overwrite the previous installation (overwriting e.g. the start script also) or even better make a fresh install.
If errors like this occur in the final release you could complain all right, but it's still pretty early in the EAP phase so there are most probably some serious bugs.

This said I noticed some minor issues in 859 but it loads and saves projects just fine, the new CVS interface alone is worth using Aurora over Ariadna and it runs so much faster than previous builds.

0
Comment actions Permalink

+1 Stephen CVS is starting to really rock in here.

Rayz, EAP is Early Access PREVIEW... Meaning Alpha, maybe Beta, code. Is your alpha code better than this?

Chill.

R

0
Comment actions Permalink

Rayz, EAP is Early Access PREVIEW... Meaning Alpha, maybe Beta, code. Is your alpha code better than this?

Well, it's usually in a better state before I let folk see it, yes. But then I'm not in a position where I can write stuff that breaks; even for alpha/beta testing .... I don't write code for developers.



0
Comment actions Permalink

Gosh. Just DON'T USE THE EAP builds.

Well my oh my. Since I can't actually create a project, I don't have much of a choice do I?

If you'd actually bothered to read the post properly, you'd have noticed that it wasn't just the bug that I was having a problem with. And if you'd read a bit further before jumping at the opportunity to be a clever chap on the keyboard, you'd have also noticed that I have worked out that the build is stable for the vast majority of folk who use it. It just ain't really working out for me. Could be just the combination of work that I do with it, just shows up more of the holes.

+Or else stop whining +

.. or you can start reading

and start to help Intellij by checking the log file, checking the tracker database and create new tracker entries for things that don't work for you.

Er ... did you actually check the tracker?

My policy is 'fill in the bug report ... then whinge.' No point doing it any other way.

Often deleting Idea's cache, dependency info or even the complete settings and recreating the project will do the job. That's why it is EAP, see? Also be sure to completley overwrite the previous installation (overwriting e.g. the start script also) or even better make a fresh install.

Yep.. Having seen this problem a couple of builds I always clear the caches (have to do this fairly regularly anyway), do a fresh install and rebuild all the projects from scratch. It is an EAP after all .. :-/

Done all that this morning. Still refused to save a project. Checked to make sure that there was no weird setting on the directory it was writing to. Nope, nought wrong there either. So you see, I actually do a little bit of work, before coming here to vent my spleen.

And sorry to disagree with you again (but I am entitled to complain if I believe that they JetBrains need to prioritise more on clearing up the bugs.

This said I noticed some minor issues in 859

Who cares? There'll be minor issues in the final release. That's not a problem.

+the new CVS interface alone is worth using Aurora over Ariadna and it runs so much faster than previous builds. +

Well, I work with a rather unusual CVS setup; the built in IDEA implementation isn't flexible enough to work with it, so in my case Aurora doesn't win out over Ariadna for this. But then I don't think any IDE would win out over a dedicated tool for this kind of job anyway.

Hhhhmmmpppp.

Right. Spleen vented. That's much better. I think the project fiasco was just the straw that broke the camel's back, as it were ....

Really must give up coffee .....

0
Comment actions Permalink

I can't even create a project with this thing.


The workaround (that worked for me). I created a new project with #856 and then switched back to #859.

0

Please sign in to leave a comment.