How Are The EAP Builds

They will only get better if you use them.

I use 813 every day, and have been using EAP through good and bad, since
it started for Aurora.

Obviously it is beta software and everyone uses different features
(witness the big fuss over CVS recently). IMHO if you can't deal with
things not working, don't use the EAP software.

charles decroes wrote:

How are the eap builds now? I tried the first aurora build and it just couldn't do the basic things. I am now using build 701. How is 813? Are you all able to do the basic editing, compiling, debugging? The first builds crashed constantly. Does it seem pretty stable now? Is it worth trying again or should I wait?

So are you able to be somewhat productive with it? You said you use it every day, how long? Are you a heads down developer or are you a student? Do you have to restart it several times a day? Are you able to do most "dumb" editor type things? Can you compile/debug?

I use it all day every day. I'm a full time developer. I have a
commercial license, but choose to use the eap. I have had no problems
that actually prevent my productive work since 813. (Unless you consider
having to restart a few times a day.)


charles decroes wrote:

So are you able to be somewhat productive with it? You said you use it every day, how long? Are you a heads down developer or are you a student? Do you have to restart it several times a day? Are you able to do most "dumb" editor type things? Can you compile/debug?

I've been using 813 every day too and it's definitely a beta so yes you need to restart it a couple of times a day but overall it's stable enough to get the job done.

Just like Barry...I use it all day every day. I'm a full time developer. I have a commercial license, but choose to use the eap. I've encountered a few problems but no show stoppers. I still keep build 688 around for occasional use and to verify a bug when I see it in 813. Go for it. I like the small tweaks to improve UI.

Although I use the EAP builds, I do find that they corrupt my project a
few times a week. Although I cannot open the project with the version I
was using when the project got corrupted, opening the project with a
different EAP 8xx version will fix it up and make it usable with the
corrupting EAP build. Strange but true.

Jon

charles decroes wrote:

So are you able to be somewhat productive with it? You said you use it every day, how long? Are you a heads down developer or are you a student? Do you have to restart it several times a day? Are you able to do most "dumb" editor type things? Can you compile/debug?

813 is quite decent I'd say. Much better than the previous versions. But it
also depends a lot on what kind of stuff you're working on, I guess.

- JSP functionality is still flaky. Stick with an Ariadna version if you do
a lot of JSP work;
- the new CVS integration works OK in 813 (it was quite unreliable in the
previous two builds, just after they changed it, I even managed to break
the build a couple of times because of incomplete updates);
- the new JUnit integration works nice;
- the other new features (code folding, search symbol, wildcard search,
etc.) come in quite handy
- didn't have any problems editing, compiling (it doesn't work with multiple
output paths, though) or debugging (mostly remote debugging against a
weblogic 6 instance);
- can't say anything about the EJB stuff, as my curent project doesn't have
any so far;
- there are a few problems with searches, apparently caused by the JSP
integration (they scarcely show up in searches, refactorings, inspections).
They're marked as fixed in 814, so I'm holding my breath for that build.

813 is the first EAP that I could really use (it has it's bugs, of course,
but no showstoppers for me) without having to rely on Ariadna for "serious"
stuff. I'll definitelly keep it around as a back-up for future builds.

HTH,
Andrei

charles decroes wrote:

How are the eap builds now? I tried the first aurora build and it just
couldn't do the basic things. I am now using build 701. How is 813? Are
you all able to do the basic editing, compiling, debugging? The first
builds crashed constantly. Does it seem pretty stable now? Is it worth
trying again or should I wait?

I skipped 809-811 because of CVS integration,
but 813 is all right.

On Mon, 05 May 2003 20:59:27 +0000, charles decroes wrote:

So are you able to be somewhat productive with it? You said you use it
every day, how long? Are you a heads down developer or are you a student?
Do you have to restart it several times a day? Are you able to do most
"dumb" editor type things? Can you compile/debug?

I'm using it all day at work, and most of the night when messing around
with stuff, EAP is doing just fine, a few rocky things but nothing
catastrophic.

--
...turn to the light - don't be frightened by the shadows it creates,
...turn to the light - turning away could be a terrible mistake
...dream theater - the great debate

On Mon, 05 May 2003 20:30:39 -0400, Jon Steelman wrote:

Although I use the EAP builds, I do find that they corrupt my project a
few times a week. Although I cannot open the project with the version I
was using when the project got corrupted, opening the project with a

Can't say I've seen any corruption of my project... mmmm.

--
...turn to the light - don't be frightened by the shadows it creates,
...turn to the light - turning away could be a terrible mistake
...dream theater - the great debate

I develop every day with it. I usually leave it running for 5 days
straight, including debugging and ant-compiles, refactoring and
editing/navigation.

charles decroes wrote:

So are you able to be somewhat productive with it? You said you use it every day, how long? Are you a heads down developer or are you a student? Do you have to restart it several times a day? Are you able to do most "dumb" editor type things? Can you compile/debug?

Cannot use the 813 build due to UI blocked in reparsing delays.
This behavior was in earlier 3.0 EAP builds but then they've put the
parsing code to the background. In 813 it foreground parsing is back.
Also, I see a long delay in autocomplete list display (typically few
seconds compared to instant display in 3.0.x).
Using several EJBs (I suspect that being the cause).
Don't have time to investigate (there was another thread about the delay
issue).

r.