Yeah, Chainsaw sat dormant for about 3 or 4 years, thus the lack of
generics. I've put a lot of cycles into Chainsaw recently, the guts are
pretty similar but there are a ton of new features...screen video here (I
gotta say, annotation is a really handy feature):
http://people.apache.org/~sdeboy/c
On 6/30/2010 10:36 PM, Scott Deboy wrote:
> Everything compiles just fine with jdk 1.5, and it seems to run fine,
> after the change discovered earlier today.
>
> Just for fun, I had a jdk 1.4 laying around. It turns out receivers and
> chainsaw both use 1.5 features that aren't in 1.4 (not many)
I've committed the change to make Chainsaw build fine with a 1.5 JDK. I'd
still suggest upgrading to 1.6, but if you don't have a choice, it will now
build and run fine with 1.5.
Scott
On Wed, Jun 30, 2010 at 9:36 PM, Scott Deboy wrote:
> Everything compiles just fine with jdk 1.5, and it seem
Everything compiles just fine with jdk 1.5, and it seems to run fine, after
the change discovered earlier today.
Just for fun, I had a jdk 1.4 laying around. It turns out receivers and
chainsaw both use 1.5 features that aren't in 1.4 (not many) - just an fyi..
I'm not sure what percentage of fo
Just to be clear, I'm not arguing for 1.5+ support. For a desktop utility like
Chainsaw, I'd be fine if we stated 1.6+, or even some more recent build of it,
e.g., 1.6.0_10+. Either way, it should be stated and whatever is chosen should
be
used to build chainsaw to ensure that it compiles and ru
I don't think we've made a statement about compatibility w/r/t Chainsaw and
JDKs. I think it's reasonable to support 1.5 even though it's End-of-Lifed,
as long as it's 'easy' to support.
Chainsaw does use a few of the more advanced Swing features, which may be
buggy in older (and no longer suppor
What is the oldest supported JVM for Chainsaw?
I always make it a point to build a project against the the oldest supported
JVM version that I promise to support. You shouldn't be building against 1.6
at all if you state 1.5 compatibility. Same goes for Log4j. If Log4j claims
1.3 compatibil
I just checked the APIs and you found a 1.5/1.6 compatibity
issue...mouseadapter in 1.5 did not implement mousemotionadapter, but it
does in 1.6.
I'll change the code to use a mousemotionadapter..
To update your working copy to svn HEAD, yes, just update your working copy
using whatever tool you
Scott,
Hope you don't mind me answering you directly - I am a newbie in the world of
open source development, so please forgive any protocol faux paus - but to
answer your question, I am developing on XP SP2 with java 1.5.0_15. I am also
starting to learn my way around maven - how would I speci
What java VM are you using to compile? is this a gcj issue (are you building
on Linux), because java.awt.event.MouseAdapter implements
java.awt.event.MouseMotionListener (you shouldn't have this compilation
issue)..
I'd make sure to use a Sun jdk to build..also,
can you updated your working copy t
Hello,
I went through the HowToBuild.txt file and executed the mvn installs for all
the projects as directed. Now getting this (any solutions/ideas appreciated)
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\App
11 matches
Mail list logo
