RE: [stellation-res] latest CVS does not compute^Wcompile

["Jonathan Gossage" <jgossage@xxxxxxxx>]

> >-----Original Message-----
> >From: stellation-res-admin@xxxxxxxxxxxxxxx
> >[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Mark C.
> >Chu-Carroll
> >Sent: September 4, 2002 5:45 AM
> >To: stellation-res@xxxxxxxxxxxxxxx
> >Subject: Re: [stellation-res] latest CVS does not compute^Wcompile
> >
> >
> >On Wed, 2002-09-04 at 00:37, Florin Iucha wrote:
> >> I have synched to the latest CVS and when I compile using "ant bundle"
> >> in misc I get:
> >>
> >/usr/local/src/stellation/org.eclipse.stellation/plugins/org.ecli
> >pse.stellation.core/src/org/eclipse/stellation/repos/UpdateManage
> >r.java:371:13:383:26:
> >>    Error: The method "int executeUpdateStatement(java.lang.String $1);"
> >>    can throw the checked exception
> >>    "org/eclipse/stellation/repos/database/DatabaseException", but its
> >>    invocation is neither enclosed in a try statement that can
> >catch that
> >>    exception nor in the body of a method or constructor that "throws"
> >>    that exception.
> >
> >Damn... Dave pointed this out to me as well. Something in my Eclipse
> >workspace is totally hosed. Eclipse claims that I'm totally up to date,
> >and the sync view shows no differences between my workspace and the CVS
> >repository. In my workspace, everything compiles cleanly, both in
> >Eclipse, and running ant from the command line. But when I do a clean
> >checkout, I see that error.
> >
> >Time to start with a fresh workspace, I think...
> >
> >> Adding
> >>    import org.eclipse.stellation.repos.database.DatabaseException;
> >> to
> >>    core/src/org/eclipse/stellation/repos/UpdateManager.java
> >> fixes the compilation problem. Yes, I see that there is an
> >>    import org.eclipse.stellation.repos.database.*;
> >> but jikes1.15 still chokes.
> >>
> >> Now speaking of that, I think we should remove the * imports
> >(regardless
> >> of whenever jikes likes them or not) because they make it harder to
> >> follow what a class really needs.
> >
> >In general, I rely on Eclipse to manage my imports for me. I think it's
> >set so that more than 10 imports from a single package turns into an
> >import *. (I find overly long import lists hard to process, so I tend to
> >like switching to the * import when there are a lot... But I'm willing
> >to switch to never using * imports if it avoids trouble.
> >
> >	-Mark
> >
I much prefer explicit lists even if long. If you put them in alphabetical
sequence with thrid party
imports following and Java library imports either first or last things are
easy to find.

Regards

Jonathan

Personal Email
jgossage@xxxxxxxx

Business Email
jonathan@xxxxxxxxxxxxxx