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) - just an fyi.. >
You must not have been using generics or other 1.5+ features in Chainsaw yet I take it? Might as well start using those. No point in bothering with 1.4 compatibility, especially if there are certain features that depend on 1.5+ already. > I'm not sure what percentage of folks are stuck on 1.5, but we're > compatible now, so no big deal. > Yep, if there's no compelling reason not to support it, then might as well support it. > The next question is: where do we advertise which jdk to use to build > chainsaw? I would guess on the main Chainsaw page and/or maybe in the Maven2 pom? I don't know of any other official location? The important thing is that if people ask, the answer exists somewhere on the site in a relatively easy to find location. > And..when do we get the companions finally out the door so I > can put up a vote on a release?? > I haven't been very much involved with that stuff. What's holding up a release? Are there changes in the works? I suppose we might want to wait for a new Log4j release so that Chainsaw can declare the dependency. Maybe all this stuff can be released at about the same time? Jake > Scott > > > > On Wed, Jun 30, 2010 at 9:54 PM, Jacob Kjome <h...@visi.com > <mailto:h...@visi.com>> wrote: > > 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 runs with that > version at a > minimum. > > I would consider 1.5+ support more strongly if chainsaw were a > server-side > application where the appserver might dictate the JVM used. As a > client-side app, > users have more control over the JVM to use. I would only bother > with 1.5 if > users insist on it or you really think there are no compelling > reasons not to > support it, at least for the first release. > > Jake > > On 6/30/2010 3:33 PM, Scott Deboy wrote: > > 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 supported) VMs, but I'm happy to test > > the upcoming release w/1.5. > > > > If we ever get there.. > > > > Scott > > > > > > > > On Wed, Jun 30, 2010 at 1:58 PM, Jacob Kjome <h...@visi.com > <mailto:h...@visi.com> > > <mailto:h...@visi.com <mailto:h...@visi.com>>> wrote: > > > > 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 compatibility, then it should > > be built against 1.3, not 1.4, 1.5, nor 1.6... at least for > testing > > and releases. > > > > If you don't do this, you inevitably end up with these weird > > compatibility issues. > > > > Jake > > > > > > > > On Wed, 30 Jun 2010 11:04:04 -0700 > > Scott Deboy <scott.de...@gmail.com > <mailto:scott.de...@gmail.com> <mailto:scott.de...@gmail.com > <mailto:scott.de...@gmail.com>>> > > wrote: > > > > 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 used to get Chainsaw from the > Apache svn > > repository. > > > > I'll make the change, but if you don't need 1.5, I'd suggest > > installing the > > 1.6 JDK - you won't have problems building with that.. > > > > Thanks for the find. > > > > Scott > > > > On Wed, Jun 30, 2010 at 10:51 AM, Kent, Douglas H. > > <doug.k...@hp.com <mailto:doug.k...@hp.com> > <mailto:doug.k...@hp.com <mailto:doug.k...@hp.com>>> wrote: > > > > 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 > > specify "updated > > your working copy to the svn HEAD revision of Chainsaw and > > companions?" > > Getting the HEAD version would pull in the bug fixes, > would > > it not? > > > > Thanks, > > Doug > > > > -----Original Message----- > > From: Scott Deboy [mailto:scott.de...@gmail.com > <mailto:scott.de...@gmail.com> > > <mailto:scott.de...@gmail.com > <mailto:scott.de...@gmail.com>>] > > Sent: Wednesday, June 30, 2010 12:31 PM > > To: Log4J Developers List > > Subject: Re: Chainsaw build error > > > > 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 to the svn HEAD revision of Chainsaw and companions? > > Line 3250 of > > LogPanel.java for svn HEAD is the declaration line of > a method: > > public Component getTableCellEditorComponent(JTable > > table, Object > > value, boolean isSelected, int row, int column) > > > > There have been a number of bug fixes recently that you > > probably want to > > pull in. > > > > Scott > > > > > > On Wed, Jun 30, 2010 at 5:59 AM, Kent, Douglas H. > > <doug.k...@hp.com <mailto:doug.k...@hp.com> > <mailto:doug.k...@hp.com <mailto:doug.k...@hp.com>>> > > wrote: > > > > > > 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:\Applications\apache-chainsaw\src\main\java\org\apache\log4j\chainsaw\LogPanel > > .java:[3250,12] > > > addMouseMotionListener(java.awt.event.MouseMotionListener) in ja > > va.awt.Component cannot be applied to (<anonymous > > java.awt.event.MouseAdapter>) > > > > > > > > > > > > C:\Applications\apache-chainsaw\src\main\java\org\apache\log4j\chainsaw\LogPanel > > .java:[3250,12] > > > addMouseMotionListener(java.awt.event.MouseMotionListener) in ja > > va.awt.Component cannot be applied to (<anonymous > > java.awt.event.MouseAdapter>) > > > > > > [INFO] > > > ------------------------------------------------------------------------ > > [INFO] Trace > > org.apache.maven.BuildFailureException: Compilation > > failure > > > > > > C:\Applications\apache-chainsaw\src\main\java\org\apache\log4j\chainsaw\LogPanel > > .java:[3250,12] > > > addMouseMotionListener(java.awt.event.MouseMotionListener) in ja > > va.awt.Component cannot be applied to (<anonymous > > java.awt.event.MouseAdapter>) > > > > > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > > ultLifecycleExecutor.java:580) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > > fecycle(DefaultLifecycleExecutor.java:500) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > > ltLifecycleExecutor.java:479) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > > dleFailures(DefaultLifecycleExecutor.java:331) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > > ts(DefaultLifecycleExecutor.java:292) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > > fecycleExecutor.java:142) > > at > > > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:345) > > at > > > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:132) > > at > > org.apache.maven.cli.MavenCli.main(MavenCli.java:290) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > Method) > > at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > > java:39) > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > > sorImpl.java:25) > > at > java.lang.reflect.Method.invoke(Method.java:585) > > at > > > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > > at > > > org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > > at > > > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > > > > at > > org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > Caused by: > > org.apache.maven.plugin.CompilationFailureException: > > Compilation fail > > ure > > > > > > C:\Applications\apache-chainsaw\src\main\java\org\apache\log4j\chainsaw\LogPanel > > .java:[3250,12] > > > addMouseMotionListener(java.awt.event.MouseMotionListener) in ja > > va.awt.Component cannot be applied to (<anonymous > > java.awt.event.MouseAdapter>) > > > > > > at > > > org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompiler > > Mojo.java:516) > > at > > > org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) > > at > > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > > nManager.java:454) > > at > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > > ultLifecycleExecutor.java:559) > > ... 16 more > > [INFO] > > > ------------------------------------------------------------------------ > > [INFO] Total time: 8 seconds > > [INFO] Finished at: Wed Jun 30 08:26:39 EDT 2010 > > [INFO] Final Memory: 17M/33M > > [INFO] > > > ------------------------------------------------------------------------ > > C:\Applications\apache-chainsaw> > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > log4j-dev-unsubscr...@logging.apache.org > <mailto:log4j-dev-unsubscr...@logging.apache.org> > > <mailto:log4j-dev-unsubscr...@logging.apache.org > <mailto:log4j-dev-unsubscr...@logging.apache.org>> > > For additional commands, e-mail: > > log4j-dev-h...@logging.apache.org > <mailto:log4j-dev-h...@logging.apache.org> > > <mailto:log4j-dev-h...@logging.apache.org > <mailto:log4j-dev-h...@logging.apache.org>> > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > log4j-dev-unsubscr...@logging.apache.org > <mailto:log4j-dev-unsubscr...@logging.apache.org> > > <mailto:log4j-dev-unsubscr...@logging.apache.org > <mailto:log4j-dev-unsubscr...@logging.apache.org>> > > For additional commands, e-mail: > > log4j-dev-h...@logging.apache.org > <mailto:log4j-dev-h...@logging.apache.org> > > <mailto:log4j-dev-h...@logging.apache.org > <mailto:log4j-dev-h...@logging.apache.org>> > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > log4j-dev-unsubscr...@logging.apache.org > <mailto:log4j-dev-unsubscr...@logging.apache.org> > > <mailto:log4j-dev-unsubscr...@logging.apache.org > <mailto:log4j-dev-unsubscr...@logging.apache.org>> > > For additional commands, e-mail: > log4j-dev-h...@logging.apache.org > <mailto:log4j-dev-h...@logging.apache.org> > > <mailto:log4j-dev-h...@logging.apache.org > <mailto:log4j-dev-h...@logging.apache.org>> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > <mailto:log4j-dev-unsubscr...@logging.apache.org> > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > <mailto:log4j-dev-h...@logging.apache.org> > > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
