Closed GoogleCodeExporter closed 9 years ago
Yes, IvySvn has required Java 6 from the start. The previous site that hosted
this
project made this clear, I will update the documentation on the Google Code
site to
mention this too so thanks for pointing that out.
I'm afraid Java 5 compatability isn't something we are going to work on but
feel free
to check out the source version and make the necessary changes yourself, I'm
guessing
there's not much that would need to change.
Original comment by massdosage
on 3 Sep 2008 at 9:00
Yep, there isn't much to change at all. I updated the code to not use the new
IOException handling and removed the @Override annotation, since @Override
annotation
not suppose to be use on implementing interface.
http://java.sun.com/docs/books/tutorial/java/javaOO/QandE/annotations-answers.ht
ml.
It is all working now.
Original comment by reach...@gmail.com
on 3 Sep 2008 at 11:21
Aah yes, thanks for noticing the @Override issue. I think some previous version
of
Eclipse put those in there but you are right, they shouldn't be set on methods
which
implement an interface, only methods which override something in a parent
class. I
have removed all of those which were incorrect.
As for the IOExceptions, the constructor which takes a nested exception is
really
useful (dunno why they only added that in Java 6!) so I'm probably going to
leave
that as it is for now.
Glad you got it working!
Original comment by massdosage
on 4 Sep 2008 at 9:16
OK, re-opened as enough people have requested this and the changes necessary are
minimal. Have already committed changes, will go into next (2.0b2) release for
testing.
Original comment by massdosage
on 4 Sep 2008 at 5:55
I create a SVNIOException subclass to handle the error constructor issue.
Original comment by staz6...@gmail.com
on 10 Sep 2008 at 4:43
IvySvn 2.0.0 Beta 2 will be Java 5 compatible (or you can check out the current
source from svn).
I followed Sun's recommendations for making exceptions backward-compatible while
retaining the stack of the original exception by doing this wherever I was
previously
nesting the exception within an IOException:
} catch (SVNException e) {
throw (IOException) new IOException().initCause(e);
}
Original comment by massdosage
on 10 Sep 2008 at 4:48
Fixed in 2.0.0-beta2 which has just been released.
Original comment by massdosage
on 12 Sep 2008 at 11:12
Original issue reported on code.google.com by
reach...@gmail.com
on 2 Sep 2008 at 9:19