Jacob Kjome | 1 Jul 06:54 2010

Re: Chainsaw build error

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 <hoju <at> visi.com
(Continue reading)

Scott Deboy | 1 Jul 06:36 2010
Picon

Re: Chainsaw build error

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 folks are stuck on 1.5, but we're compatible now, so no big deal.

The next question is: where do we advertise which jdk to use to build chainsaw?  And..when do we get the companions finally out the door so I can put up a vote on a release??

Scott



On Wed, Jun 30, 2010 at 9:54 PM, Jacob Kjome <hoju <at> 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 <hoju <at> visi.com
> <mailto:hoju <at> 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.deboy <at> gmail.com <mailto:scott.deboy <at> 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.kent <at> hp.com <mailto:doug.kent <at> 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.deboy <at> gmail.com
>             <mailto:scott.deboy <at> 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.kent <at> hp.com <mailto:doug.kent <at> 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-unsubscribe <at> logging.apache.org
>             <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>                   For additional commands, e-mail:
>             log4j-dev-help <at> logging.apache.org
>             <mailto:log4j-dev-help <at> logging.apache.org>
>
>
>
>
>
>             ---------------------------------------------------------------------
>             To unsubscribe, e-mail:
>             log4j-dev-unsubscribe <at> logging.apache.org
>             <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>             For additional commands, e-mail:
>             log4j-dev-help <at> logging.apache.org
>             <mailto:log4j-dev-help <at> logging.apache.org>
>
>
>
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
For additional commands, e-mail: log4j-dev-help <at> logging.apache.org


Scott Deboy | 1 Jul 06:39 2010
Picon

Re: Chainsaw build error

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 <scott.deboy <at> gmail.com> 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..

I'm not sure what percentage of folks are stuck on 1.5, but we're compatible now, so no big deal.

The next question is: where do we advertise which jdk to use to build chainsaw?  And..when do we get the companions finally out the door so I can put up a vote on a release??

Scott




On Wed, Jun 30, 2010 at 9:54 PM, Jacob Kjome <hoju <at> 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 <hoju <at> visi.com
> <mailto:hoju <at> 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.deboy <at> gmail.com <mailto:scott.deboy <at> 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.kent <at> hp.com <mailto:doug.kent <at> 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.deboy <at> gmail.com
>             <mailto:scott.deboy <at> 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.kent <at> hp.com <mailto:doug.kent <at> 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-unsubscribe <at> logging.apache.org
>             <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>                   For additional commands, e-mail:
>             log4j-dev-help <at> logging.apache.org
>             <mailto:log4j-dev-help <at> logging.apache.org>
>
>
>
>
>
>             ---------------------------------------------------------------------
>             To unsubscribe, e-mail:
>             log4j-dev-unsubscribe <at> logging.apache.org
>             <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>             For additional commands, e-mail:
>             log4j-dev-help <at> logging.apache.org
>             <mailto:log4j-dev-help <at> logging.apache.org>
>
>
>
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
For additional commands, e-mail: log4j-dev-help <at> logging.apache.org



Jacob Kjome | 1 Jul 07:58 2010

Re: Chainsaw build error

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 <hoju <at> visi.com
> <mailto:hoju <at> 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 <hoju <at> visi.com
>     <mailto:hoju <at> visi.com>
>     > <mailto:hoju <at> visi.com <mailto:hoju <at> 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.deboy <at> gmail.com
>     <mailto:scott.deboy <at> gmail.com> <mailto:scott.deboy <at> gmail.com
>     <mailto:scott.deboy <at> 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.kent <at> hp.com <mailto:doug.kent <at> hp.com>
>     <mailto:doug.kent <at> hp.com <mailto:doug.kent <at> 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.deboy <at> gmail.com
>     <mailto:scott.deboy <at> gmail.com>
>     >             <mailto:scott.deboy <at> gmail.com
>     <mailto:scott.deboy <at> 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.kent <at> hp.com <mailto:doug.kent <at> hp.com>
>     <mailto:doug.kent <at> hp.com <mailto:doug.kent <at> 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-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     >             <mailto:log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>>
>     >                   For additional commands, e-mail:
>     >             log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>     >             <mailto:log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>>
>     >
>     >
>     >
>     >
>     >
>     >            
>     ---------------------------------------------------------------------
>     >             To unsubscribe, e-mail:
>     >             log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     >             <mailto:log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>>
>     >             For additional commands, e-mail:
>     >             log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>     >             <mailto:log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>>
>     >
>     >
>     >
>     >
>     >    
>     ---------------------------------------------------------------------
>     >     To unsubscribe, e-mail:
>     log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     >     <mailto:log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>>
>     >     For additional commands, e-mail:
>     log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>     >     <mailto:log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>>
>     >
>     >
> 
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
> 
> 
Scott Deboy | 1 Jul 07:11 2010
Picon

Re: Chainsaw build error

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/chainsawdemo.avi

Chainsaw does depend on a recent 'core log4j' release (1.2.16), and receivers and extras have changes that Chainsaw depends upon.  Everything is clean rat-wise, so I think we're pretty much ready to cut release candidates.

My preference would be to get Chainsaw + companions out the door asap, voting on everything at the same time would work for me.

One thing I would like to do is add some updated screen shots, maybe even the screen video on the Chainsaw page (not sure where things like that should go..they seem too big to add to svn for the dev checkout).

We have to decide what to do about the ZeroConf companion.  Now that the latest release of log4j includes network-based appenders which have zeroconf built-in, via reflection, the zeroconf companion is redundant.  Not critical, but something we need to take care of.

I actually don't have a pgp signature on file here, so I don't think I can cut release candidates myself without going through some hoops, so I've been relying on Curt's free time, but I should probably just figure out what I need to do to cut the release candidates myself...

Scott

On Wed, Jun 30, 2010 at 10:58 PM, Jacob Kjome <hoju <at> visi.com> wrote:
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 <hoju <at> visi.com
> <mailto:hoju <at> 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 <hoju <at> visi.com
>     <mailto:hoju <at> visi.com>
>     > <mailto:hoju <at> visi.com <mailto:hoju <at> 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.deboy <at> gmail.com
>     <mailto:scott.deboy <at> gmail.com> <mailto:scott.deboy <at> gmail.com
>     <mailto:scott.deboy <at> 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.kent <at> hp.com <mailto:doug.kent <at> hp.com>
>     <mailto:doug.kent <at> hp.com <mailto:doug.kent <at> 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.deboy <at> gmail.com
>     <mailto:scott.deboy <at> gmail.com>
>     >             <mailto:scott.deboy <at> gmail.com
>     <mailto:scott.deboy <at> 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.kent <at> hp.com <mailto:doug.kent <at> hp.com>
>     <mailto:doug.kent <at> hp.com <mailto:doug.kent <at> 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-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     >             <mailto:log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>>
>     >                   For additional commands, e-mail:
>     >             log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>     >             <mailto:log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>>
>     >
>     >
>     >
>     >
>     >
>     >
>     ---------------------------------------------------------------------
>     >             To unsubscribe, e-mail:
>     >             log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     >             <mailto:log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>>
>     >             For additional commands, e-mail:
>     >             log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>     >             <mailto:log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>>
>     >
>     >
>     >
>     >
>     >
>     ---------------------------------------------------------------------
>     >     To unsubscribe, e-mail:
>     log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     >     <mailto:log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>>
>     >     For additional commands, e-mail:
>     log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>     >     <mailto:log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>>
>     >
>     >
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
>     <mailto:log4j-dev-unsubscribe <at> logging.apache.org>
>     For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
>     <mailto:log4j-dev-help <at> logging.apache.org>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
For additional commands, e-mail: log4j-dev-help <at> logging.apache.org


Curt Arnold | 3 Jul 04:06 2010
Picon

Re: Chainsaw build error


On Jul 1, 2010, at 12:11 AM, Scott Deboy wrote:
> 
> I actually don't have a pgp signature on file here, so I don't think I can cut release candidates myself
without going through some hoops, so I've been relying on Curt's free time, but I should probably just
figure out what I need to do to cut the release candidates myself...
> 
> Scott

"Free time", I'm not sure I know what that means.  Sorry, been buried recently.  As far as I can tell,
everything is ready on log4j and the companions for a release candidate cut.

Can you describe the JDK 1.5 dependency in receivers?  Does it require JDK 1.5+ to build, but some aspects
might function on earlier VM's or it is cross the board failure on earlier JDK's.

The last couple of builds have been on Ubuntu, less to collect than trying to build on Windows.  I was
intending to build the last log4j release on bootable CD or Amazon Web Services to make it easy for someone
else (or me if I had a crash) to create a near duplicate release.  I had to update my signing key during the
1.2.16 and it took a couple of tries to get the signature in everyplace that it needed to be.  Even if you don't
actually put the bits on the distribution server, it would be good to have someone else walk through the process.
Scott Deboy | 3 Jul 04:21 2010
Picon

Re: Chainsaw build error

My laptop died yesterday so I can't do much until it comes back from  
being repaired.

I remember seeing charbuffer refs in tests (nio) and one or two other  
issues but you'd have to try it yourself.

I'm not able to help with a release until it gets back, so if you have  
time that'd be great...fine either way.

Scott

On Jul 2, 2010, at 7:06 PM, Curt Arnold <carnold <at> apache.org> wrote:

>
> On Jul 1, 2010, at 12:11 AM, Scott Deboy wrote:
>>
>> I actually don't have a pgp signature on file here, so I don't  
>> think I can cut release candidates myself without going through  
>> some hoops, so I've been relying on Curt's free time, but I should  
>> probably just figure out what I need to do to cut the release  
>> candidates myself...
>>
>> Scott
>
> "Free time", I'm not sure I know what that means.  Sorry, been  
> buried recently.  As far as I can tell, everything is ready on log4j  
> and the companions for a release candidate cut.
>
> Can you describe the JDK 1.5 dependency in receivers?  Does it  
> require JDK 1.5+ to build, but some aspects might function on  
> earlier VM's or it is cross the board failure on earlier JDK's.
>
> The last couple of builds have been on Ubuntu, less to collect than  
> trying to build on Windows.  I was intending to build the last log4j  
> release on bootable CD or Amazon Web Services to make it easy for  
> someone else (or me if I had a crash) to create a near duplicate  
> release.  I had to update my signing key during the 1.2.16 and it  
> took a couple of tries to get the signature in everyplace that it  
> needed to be.  Even if you don't actually put the bits on the  
> distribution server, it would be good to have someone else walk  
> through the process.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
> For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
>
bugzilla | 4 Jul 13:23 2010
Picon

Bug report for Log4j [2010/07/04]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
|     |   |           MIN=Minor   NOR=Normal    ENH=Enhancement TRV=Trivial |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|23329|New|Enh|2003-09-22|<logger> element in XML config should support reso|
|26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|Inf|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|Inf|Enh|2004-03-02|NetSendAppender                                   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n|
|30407|Inf|Maj|2004-07-30|Externally rolled file problem                    |
|30888|Inf|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30892|New|Min|2004-08-27|Log files cannot be closed                        |
|31089|New|Nor|2004-09-07|Does not accept ISO8601 dates in focus field      |
|31178|Inf|Cri|2004-09-11|Exception using Chainsaw for simple debugging     |
|31179|Ass|Enh|2004-09-11|Implement Chainsaw as Eclipse stand-alone applicat|
|33278|New|Min|2005-01-27|NPE thrown durring daily log file rollover        |
|33493|Inf|Enh|2005-02-10|contribution to log4j: servlet diagnostic context |
|34440|New|Nor|2005-04-13|sandbox:IMAppender - comma-seperated recipient lis|
|34491|Ver|Nor|2005-04-18|Missing include in build.jms target results in mis|
|34651|New|Enh|2005-04-27|allow for a header on top of every rolled file    |
|34738|Inf|Nor|2005-05-04|Chainsaw does not remember what Columns are select|
|34945|Inf|Nor|2005-05-17|ThrowableInformation has dubious Stack Trace extra|
|34974|Inf|Cri|2005-05-19|Exception when running a Pluglet                  |
|35239|Inf|Nor|2005-06-06|NullPointerException when saving displayed events |
|35563|Inf|Enh|2005-06-30|Syslog appender parametrability                   |
|35996|Inf|Enh|2005-08-03|Add support for ant-like <property> in log4j.xml  |
|36435|New|Enh|2005-08-31|Log4J RollingFileAppender under OpenVMS does not f|
|36654|Inf|Min|2005-09-14|Provide better error messages for "Please initiali|
|36789|Inf|Nor|2005-09-23|Empty control flow statement in org.apache.log4j.l|
|37349|Ass|Nor|2005-11-03|DBAppender not working with jTDS driver           |
|37638|New|Nor|2005-11-25|logging doesn't fall back with FallbackErrorHandle|
|37734|New|Nor|2005-12-01|Customize Event ID and Event Category with NTEVent|
|38363|Ass|Nor|2006-01-24|SecurityException during log output               |
|38394|Ver|Enh|2006-01-26|PropertySetter fails to print stacktrace if error |
|38395|Ver|Reg|2006-01-26|Unable to set threshold on appender via config fil|
|38406|Ver|Nor|2006-01-26|jdk1.4 dependencies in log4j 1.3 alpha            |
|38513|New|Nor|2006-02-05|[PATCH] Suggested unit test for JMSAppender       |
|38582|Ass|Nor|2006-02-08|Chainsaw does not include Receiver JavaDoc in dist|
|38590|Inf|Nor|2006-02-09|no space on device fails another instance         |
|38883|Opn|Nor|2006-03-07|LogFilePatternReceiver fails to process multi-line|
|39690|Inf|Cri|2006-05-31|Initialization fail in J2EE Environment           |
|39691|Ass|Nor|2006-05-31|DBAppender doesn't log long events                |
|40068|New|Nor|2006-07-18|Add support for attach-on-demand API to chainsaw  |
|40251|Opn|Min|2006-08-14|Hard coded JMX domain name for MBean instances    |
|40382|Inf|Maj|2006-09-01|Sysappender hangs during boot time on HP          |
|40385|Inf|Maj|2006-09-01|SocketServer cannot find config file when passed a|
|40472|New|Nor|2006-09-11|SettingsManager calls loadSettings with global set|
|40533|New|Nor|2006-09-18|Chainsaw not showing all logging statements       |
|40570|Inf|Blk|2006-09-21|RollingFileAppender does not rollover when the fil|
|40611|New|Trv|2006-09-27|Bad subclass example; NullPointerException in Logg|
|40736|Inf|Nor|2006-10-11|log4j delete permission denied                    |
|40889|Inf|Nor|2006-11-03|repeated entries in log after failure             |
|40990|Inf|Nor|2006-11-17|Cannot bind port or ip address for outgoing UDP so|
|41006|Inf|Enh|2006-11-20|Contributing XMLSocketHubReceiver                 |
|41214|Ass|Maj|2006-12-19|Deadlock with RollingFileAppender                 |
|41311|Inf|Min|2007-01-06|Please make TimeBasedRollingPolicy non-final?     |
|41547|Inf|Nor|2007-02-05|PropertyConfigurator and layout.contentType       |
|41799|New|Enh|2007-03-09|SyslogAppender should enable to customize Log4j.Le|
|41882|Inf|Nor|2007-03-18|IE7 problems with Log4J web site                  |
|41937|New|Nor|2007-03-23|Logs from some panels missing in custom expression|
|41980|Inf|Maj|2007-03-29|Log4j stop updating log file- version log4j-1.2.8 |
|42189|Ass|Nor|2007-04-22|Add simple bridge for java.util.logging, with basi|
|42213|Opn|Blk|2007-04-24|log4j causing threads to stuck in weblogic        |
|42516|Inf|Nor|2007-05-24|Log4j failed to log file when packaged in Eclipse |
|42664|New|Enh|2007-06-14|JUL Appender                                      |
|42883|Opn|Nor|2007-07-12|'Welcome' and 'Drag & Drop' panels can't be hidden|
|42933|Inf|Maj|2007-07-18|IllegalStateException thrown from FileAppender.clo|
|43148|Ass|Nor|2007-08-16|LogFilePatternReceiver depends on jakarta-oro, cou|
|43282|Opn|Nor|2007-08-31|Add OSGi packaging info to log4j and companions   |
|43313|Ass|Nor|2007-09-05|log4j 1.2.16 release considerations and discussion|
|43403|Inf|Nor|2007-09-16|PatternLayout: new format modifer: prefix if non-e|
|43619|New|Enh|2007-10-13|Simple proposal for pluggable sys-props resolvers |
|43637|Inf|Nor|2007-10-16|SocketAppender.append(LoggingEvent) calls the Erro|
|43728|Inf|Cri|2007-10-29|Log file loss when specified file is locked by ano|
|43736|Ass|Nor|2007-10-30|Chainsaw does not honor encoding when loading XML |
|43820|New|Enh|2007-11-08|[PATCH] Layered Configurator Patch                |
|43879|Inf|Nor|2007-11-16|FileAppender writes Header multiple times         |
|43911|Inf|Nor|2007-11-20|logfiles not getting rolled over with RollingFileA|
|43923|Inf|Min|2007-11-21|JBOSS specific information in javadocs            |
|44219|Inf|Nor|2008-01-13|'WARNING' for a log level is silently ignored/chan|
|44308|New|Enh|2008-01-28|[Patch] JMX component for managing Logger configur|
|44370|Inf|Reg|2008-02-06|MANIFEST.MF broken in log4j-1.2.15.jar            |
|44386|Opn|Nor|2008-02-10|NTEventLogAppender.dll for windows 64             |
|44526|Inf|Nor|2008-03-04|segmentation fault occuring when PropertyConfigura|
|44557|Inf|Nor|2008-03-07|no close call to Appender after replacing the root|
|44649|Inf|Nor|2008-03-20|JMS Hangs when a Root Appender                    |
|44700|Inf|Nor|2008-03-28|Log4J locks rolled log files                      |
|44727|Inf|Nor|2008-04-01|Add missing Logger#isErrorEnabled and isWarningEna|
|44834|Inf|Nor|2008-04-17|SimpleSocketServer looses buffered logs, produces |
|44839|Inf|Nor|2008-04-17|SyslogAppender logging to a UNIX domain socket    |
|44932|New|Cri|2008-05-05|improve DailyRollingFileAppender handling of rotat|
|44934|Inf|Enh|2008-05-05|add helper method to DailyRollingFileAppender to g|
|45042|New|Nor|2008-05-19|Need a reliable way to detect misconfiguration    |
|45109|Inf|Nor|2008-05-31|SMTPAppender uses wrong property for mail server  |
|45165|Ass|Enh|2008-06-09|Multifile Appender                                |
|45231|Ass|Nor|2008-06-18|Clear appenders call on logger calls a helper whic|
|45236|Inf|Cri|2008-06-19|Wriring output to an out-dated file.              |
|45304|Inf|Nor|2008-06-29|using log4j with OAS for some reasone all the logg|
|45482|Inf|Min|2008-07-25|Source contains unused variables                  |
|45629|New|Nor|2008-08-13|TopicConnection is not closed                     |
|45753|New|Nor|2008-09-06|Code contribution: BurstFilter for extras         |
|45781|New|Nor|2008-09-11|RollingFileAppender under Windows does not rotate |
|45855|New|Enh|2008-09-21|Add site/apt documentation for JULBridgeLogManager|
|45932|New|Nor|2008-10-01|Log4j JMX MBeans not cleaned up                   |
|45934|New|Enh|2008-10-02|FileAppender should use virtual-machine shutdown h|
|45939|New|Nor|2008-10-02|Cannot drop HierarchyDynamicMBean from LoggerRepos|
|46100|New|Enh|2008-10-27|NagiosAppender available for contribution         |
|46260|Inf|Nor|2008-11-21|RollingFileAppender and Tomcat has a strange behav|
|46426|Ass|Nor|2008-12-20|Implement commons-logging interfaces natively in l|
|46514|New|Nor|2009-01-12|provide API to re-init log4j                      |
|46533|New|Enh|2009-01-14|Deamon Thread                                     |
|46570|New|Nor|2009-01-20|DailyRollingFileAppender rolls logs into files dat|
|46573|Inf|Maj|2009-01-21|MDC attributes cant't be displayed on Chainsaw    |
|46592|Opn|Trv|2009-01-23|trim() on property file entries                   |
|46626|New|Enh|2009-01-29|Log4J 1.2.15 SyslogAppender doesn't not handle TAG|
|46691|New|Nor|2009-02-10|log4j file rolling over on restart of the server  |
|46804|New|Enh|2009-03-05|create the method PropertyConfigurator.configureAn|
|46868|New|Nor|2009-03-17|SocketHUBAppender: Allow restriction of binding to|
|46878|New|Cri|2009-03-19|Deadlock in 1.2.15 caused by AsyncAppender and Thr|
|46941|New|Enh|2009-03-31|Sub Level Logging Technique                       |
|46983|New|Enh|2009-04-07|More Debug output for log4j auto-configure request|
|47004|Inf|Nor|2009-04-08|log messages occasionally sharing a line          |
|47123|New|Blk|2009-04-29|TimeBasedRollingPolicy appends logs into a old log|
|47141|Inf|Enh|2009-05-02|add getCyclicBuffer() method to log4j SMTPAppender|
|47164|New|Enh|2009-05-07|HTMLLayout replace newline with <BR>              |
|47208|New|Enh|2009-05-17|Better Default colours for Log Panel Color Filter |
|47357|New|Min|2009-06-11|Declaring logger and category with same name cause|
|47575|Inf|Nor|2009-07-24|GZipping large files stops logging                |
|47595|Opn|Nor|2009-07-28|[companion] POMs of companions have problems      |
|47703|New|Nor|2009-08-18|Object rendering ought to be done outside synchron|
|47713|Inf|Nor|2009-08-20|SMTPAppender system properties propagation issue  |
|47740|Inf|Nor|2009-08-26|log4j 1.2.15 deadlock RootAppender NDC            |
|47883|New|Nor|2009-09-21|Lines dropped with UseNewHashFunction             |
|47898|Inf|Maj|2009-09-24|DailyRollingFileAppender unable to create backup l|
|47960|New|Min|2009-10-08|CompositeAppender contribution                    |
|48027|Inf|Cri|2009-10-20|Logger statements in a particular class file is no|
|48141|Inf|Cri|2009-11-05|Log file rotation issue in Linux VM               |
|48209|New|Nor|2009-11-17|Websphere 6.0: logging statements appear in the SY|
|48220|New|Min|2009-11-18|LoggingEvent.mdcCopy serialization with non-serial|
|48244|New|Min|2009-11-19|Socket Server configuration does not handle not re|
|48356|New|Nor|2009-12-08|Download page does not have link to KEYS file     |
|48365|New|Maj|2009-12-10|Log4J DailyRollingFileAppender sometimes does not |
|48430|New|Nor|2009-12-22|log4j:ERROR Write failure. java.io.IOException: St|
|48502|New|Cri|2010-01-07|Issue: Rotation file is not getting created - Roll|
|48527|New|Maj|2010-01-11|maven metadata is out of date                     |
|48583|New|Enh|2010-01-20|allow format of timestamp (first column of log fil|
|48607|New|Cri|2010-01-25|Log levels are not displayed corectly             |
|48679|New|Nor|2010-02-04|performance of getEffectiveLevel can be significan|
|48704|New|Nor|2010-02-08|Multiple Java Process in Cluster Logging to the sa|
|48802|New|Nor|2010-02-23|Log4j not writting.                               |
|48820|New|Nor|2010-02-26|JDBCAppender inserts the current MDC values for th|
|48986|New|Nor|2010-03-25|RollingFileAppender.rollOver() calls this.setFile |
|49003|New|Nor|2010-03-27|SocketServerTestCase.test8 fails on Apache Harmony|
|49071|New|Nor|2010-04-08|1.2.16 isn't available for download               |
|49077|New|Nor|2010-04-09|Prepare smaller jar omitting LF5 and Chainsaw 1   |
|49177|New|Enh|2010-04-23|SyslogAppender: Make the maximum package size conf|
|49229|New|Trv|2010-04-29|build.xml reference wrong javax mail version, shou|
|49243|New|Min|2010-05-04|Fix one BZ number in Changelog of 1.2.16          |
|49247|New|Enh|2010-05-04|Add option for persistent/non-persistent delivery |
|49248|New|Min|2010-05-04|javadoc for org.apache.log4j.rolling.FixedWindowRo|
|49265|New|Nor|2010-05-07|log4j - java.io.OptionalDataException             |
|49307|New|Nor|2010-05-18|unusable error message when log4j.xml has a duplic|
|49329|New|Nor|2010-05-23|Smart and compact formatting of package/class name|
|49349|New|Nor|2010-05-27|LoggingEvent stoped coming with AsyncAppender     |
|49353|New|Nor|2010-05-28|[patch] change logfactor userdir name to hidden di|
|49354|New|Nor|2010-05-28|XMLLayout writes illegal characters to XML file   |
|49359|New|Nor|2010-05-29|Log4j site should have some mention of git mirrori|
|49390|New|Nor|2010-06-05|1.0 releases of log4j companions component and rec|
|49421|New|Maj|2010-06-10|Chainsaw don't show Logger for SocketReceiver and |
|49470|New|Nor|2010-06-19|log4j 1.2.17 release                              |
|49471|New|Enh|2010-06-19|Add CDATA parameter to XmlLayout                  |
|49481|New|Maj|2010-06-21|Log4j stops writting to file, and then causes serv|
|49489|New|Enh|2010-06-22|Ability to filter on several loggers              |
+-----+---+---+----------+--------------------------------------------------+
| Total  174 bugs                                                           |
+---------------------------------------------------------------------------+
noreply | 6 Jul 14:46 2010
Picon

[GUMP <at> vmgump]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project logging-log4j-chainsaw has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - logging-log4j-chainsaw :  Chainsaw log viewer

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason build failed
 -INFO- Failed to extract fallback artifacts from Gump Repository

The following work was performed:
http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/gump_work/build_logging-chainsaw_logging-log4j-chainsaw.html
Work Name: build_logging-chainsaw_logging-log4j-chainsaw (Type: Build)
Work ended in a state of : Failed
Elapsed: 5 secs
Command Line: /usr/lib/jvm/java-6-sun/bin/java -Djava.awt.headless=true
-Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only -Dversion=06072010 -Dgump=true chainsaw.jar 
[Working Directory: /srv/gump/public/workspace/logging-chainsaw]
CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/logging-chainsaw/classes:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/jakarta-oro/jakarta-oro-06072010.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-060720
 10.jar:/srv/gump/public/workspace/logging-log4j-zeroconf/target/apache-log4j-zeroconf-1.0-SNAPSHOT.jar:/srv/gump/public/workspace/logging-log4j-extras/target/apache-log4j-extras-06072010.jar
 :/srv/gump/public/workspace/logging-log4j-receivers/target/apache-log4j-receivers-06072010.jar:/srv/gump/public/workspace/logging-log4j-component/target/apache-log4j-component-06072010.jar:/srv/gump/public/workspace/apache-commons/vfs/core/target/commons-vfs-2.0-SNAPSHOT.jar:/srv/gump/public/workspace/xstream/xstream/target/xstream-1.4-SNAPSHOT.jar:/srv/gump/public/workspace/jmdns/lib/jmdns.jar:/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/srv/gump/packages/jms1.1/lib/jms.jar:/srv/gump/packages/jmx-1_2_1-bin/lib/jmxri.jar:/srv/gump/packages/jmx-1_2_1-bin/lib/jmxtools.jar:/srv/gump/public/workspace/junit/dist/junit-06072010.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar
---------------------------------------------
    [javac] symbol  : class UIKeyboardInteractive
    [javac] location: class org.apache.log4j.chainsaw.vfs.VFSLogFilePatternReceiver
    [javac]   public static class MyUserInfo implements UserInfo, UIKeyboardInteractive {
    [javac]                                                       ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/color/RuleColorizer.java:235:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
    [javac]         File f = new File(SettingsManager.getInstance().getSettingsDirectory(),
URLEncoder.encode(name + COLORS_EXTENSION));
    [javac]                                                                                           ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/color/RuleColorizer.java:267:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
    [javac]     File f = new File(SettingsManager.getInstance().getSettingsDirectory(),
URLEncoder.encode(name) + COLORS_EXTENSION);
    [javac]                                                                                       ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:156:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
    [javac]         		URLEncoder.encode(p.getNamespace() + ".properties"));
    [javac]         		          ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:248:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
    [javac]                                 		 URLEncoder.encode(profileable.getNamespace()) + ".properties")));
    [javac]                                 		           ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/LogPanel.java:1399:
warning: [deprecation] Date(java.lang.String) in java.util.Date has been deprecated
    [javac]             	value = timestampExpressionFormat.format(new Date(table.getValueAt(row, column).toString()));
    [javac]             	                                         ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/LogPanel.java:1592:
warning: [deprecation] Date(java.lang.String) in java.util.Date has been deprecated
    [javac]             	value = timestampExpressionFormat.format(new Date(table.getValueAt(row, column).toString()));
    [javac]             	                                         ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/LogPanel.java:1845:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
    [javac]                 .getSettingsDirectory(), URLEncoder.encode(identifier) + ".xml");
    [javac]                                                    ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/LogPanel.java:1954:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
    [javac]               .getSettingsDirectory(), URLEncoder.encode(identifier) + ".xml");
    [javac]                                                  ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/NoReceiversWarningPanel.java:625:
warning: [deprecation] toURL() in java.io.File has been deprecated
    [javac]                     return file.toURL();
    [javac]                                ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/vfs/VFSLogFilePatternReceiver.java:344:
cannot access com.jcraft.jsch.UserInfo
    [javac] class file for com.jcraft.jsch.UserInfo not found
    [javac]                     	SftpFileSystemConfigBuilder.getInstance().setUserInfo(opts, new MyUserInfo(password));
    [javac]                     	                                         ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/vfs/VFSLogFilePatternReceiver.java:391:
setUserInfo(org.apache.commons.vfs.FileSystemOptions,com.jcraft.jsch.UserInfo) in
org.apache.commons.vfs.provider.sftp.SftpFileSystemConfigBuilder cannot be applied to (org.apache.commons.vfs.FileSystemOptions,org.apache.log4j.chainsaw.vfs.VFSLogFilePatternReceiver.MyUserInfo)
    [javac]                             SftpFileSystemConfigBuilder.getInstance().setUserInfo(opts, new MyUserInfo(password));
    [javac]                                                                      ^
    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/zeroconf/ZeroConfDeviceModel.java:60:
warning: [deprecation] getAddress() in javax.jmdns.ServiceInfo has been deprecated
    [javac]                 return info.getAddress().getHostName() + ":" + info.getPort();
    [javac]                            ^
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] 6 errors
    [javac] 10 warnings

BUILD FAILED
/srv/gump/public/workspace/logging-chainsaw/build.xml:81: Compile failed; see the compiler error
output for details.

Total time: 4 seconds
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/rss.xml
- Atom: http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 05000006072010, vmgump:vmgump-public:05000006072010
Gump E-mail Identifier (unique within run) #28.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]
Curt Arnold | 6 Jul 15:31 2010
Picon

Re: [GUMP <at> vmgump]: Project logging-log4j-chainsaw (in module logging-chainsaw) failed

I've quickly looked at this and am not quite sure what is going on.  The Gump report says it has been in this
state since 2010-07-05T00:00, so typically you'd look for some change in either Chainsaw (none know of)
or a dependency (in this case likely VFS) in a 24 hour window before that,  However, the Gump report says the
last success was 2007-06-03 which might mean that Chainsaw had been removed from the Gump profile since then.

I'm not sure if Chainsaw's use of VFS's SFTP facility may require an encryption export notice.  But that
should be checked.

The warnings on the use of URLEncoder are interesting as they are being used for file paths and would result
in characters being escaped they do not need to be escaped (spaces, ampersands, etc).;

On Jul 6, 2010, at 7:46 AM, <noreply <at> qos.ch> <noreply <at> qos.ch> wrote:

> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general <at> gump.apache.org.
> 
> Project logging-log4j-chainsaw has an issue affecting its community integration.
> This issue affects 1 projects.
> The current state of this project is 'Failed', with reason 'Build Failed'.
> For reference only, the following projects are affected by this:
>    - logging-log4j-chainsaw :  Chainsaw log viewer
> 
> 
> Full details are available at:
>    http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/index.html
> 
> That said, some information snippets are provided here.
> 
> The following annotations (debug/informational/warning/error messages) were provided:
> -INFO- Failed with reason build failed
> -INFO- Failed to extract fallback artifacts from Gump Repository
> 
> 
> 
> The following work was performed:
> http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/gump_work/build_logging-chainsaw_logging-log4j-chainsaw.html
> Work Name: build_logging-chainsaw_logging-log4j-chainsaw (Type: Build)
> Work ended in a state of : Failed
> Elapsed: 5 secs
> Command Line: /usr/lib/jvm/java-6-sun/bin/java -Djava.awt.headless=true
-Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only -Dversion=06072010 -Dgump=true chainsaw.jar 
> [Working Directory: /srv/gump/public/workspace/logging-chainsaw]
> CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.jar:/srv/gump/public/workspace/logging-chainsaw/classes:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/jakarta-oro/jakarta-oro-06072010.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-06072010.jar:/srv/gump/public/workspace/logging-log4j-zeroconf/target/apache-log4j-zeroconf-1.0-SNAPSHOT.jar:/srv/gump/public/workspace/logging-log4j-extras/target/apache-log4j-extras-06072010.jar
> :/srv/gump/public/workspace/logging-log4j-receivers/target/apache-log4j-receivers-06072010.jar:/srv/gump/public/workspace/logging-log4j-component/target/apache-log4j-component-06072010.jar:/srv/gump/public/workspace/apache-commons/vfs/core/target/commons-vfs-2.0-SNAPSHOT.jar:/srv/gump/public/workspace/xstream/xstream/target/xstream-1.4-SNAPSHOT.jar:/srv/gump/public/workspace/jmdns/lib/jmdns.jar:/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/srv/gump/packages/jms1.1/lib/jms.jar:/srv/gump/packages/jmx-1_2_1-bin/lib/jmxri.jar:/srv/gump/packages/jmx-1_2_1-bin/lib/jmxtools.jar:/srv/gump/public/workspace/junit/dist/junit-06072010.jar:/srv/gump/packages/javamail-1.4/mail.jar:/srv/gump/packages/javamail-1.4/lib/mailapi.jar
> ---------------------------------------------
>    [javac] symbol  : class UIKeyboardInteractive
>    [javac] location: class org.apache.log4j.chainsaw.vfs.VFSLogFilePatternReceiver
>    [javac]   public static class MyUserInfo implements UserInfo, UIKeyboardInteractive {
>    [javac]                                                       ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/color/RuleColorizer.java:235:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
>    [javac]         File f = new File(SettingsManager.getInstance().getSettingsDirectory(),
URLEncoder.encode(name + COLORS_EXTENSION));
>    [javac]                                                                                           ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/color/RuleColorizer.java:267:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
>    [javac]     File f = new File(SettingsManager.getInstance().getSettingsDirectory(),
URLEncoder.encode(name) + COLORS_EXTENSION);
>    [javac]                                                                                       ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:156:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
>    [javac]         		URLEncoder.encode(p.getNamespace() + ".properties"));
>    [javac]         		          ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java:248:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
>    [javac]                                 		 URLEncoder.encode(profileable.getNamespace()) + ".properties")));
>    [javac]                                 		           ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/LogPanel.java:1399:
warning: [deprecation] Date(java.lang.String) in java.util.Date has been deprecated
>    [javac]             	value = timestampExpressionFormat.format(new Date(table.getValueAt(row, column).toString()));
>    [javac]             	                                         ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/LogPanel.java:1592:
warning: [deprecation] Date(java.lang.String) in java.util.Date has been deprecated
>    [javac]             	value = timestampExpressionFormat.format(new Date(table.getValueAt(row, column).toString()));
>    [javac]             	                                         ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/LogPanel.java:1845:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
>    [javac]                 .getSettingsDirectory(), URLEncoder.encode(identifier) + ".xml");
>    [javac]                                                    ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/LogPanel.java:1954:
warning: [deprecation] encode(java.lang.String) in java.net.URLEncoder has been deprecated
>    [javac]               .getSettingsDirectory(), URLEncoder.encode(identifier) + ".xml");
>    [javac]                                                  ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/NoReceiversWarningPanel.java:625:
warning: [deprecation] toURL() in java.io.File has been deprecated
>    [javac]                     return file.toURL();
>    [javac]                                ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/vfs/VFSLogFilePatternReceiver.java:344:
cannot access com.jcraft.jsch.UserInfo
>    [javac] class file for com.jcraft.jsch.UserInfo not found
>    [javac]                     	SftpFileSystemConfigBuilder.getInstance().setUserInfo(opts, new MyUserInfo(password));
>    [javac]                     	                                         ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/vfs/VFSLogFilePatternReceiver.java:391:
setUserInfo(org.apache.commons.vfs.FileSystemOptions,com.jcraft.jsch.UserInfo) in
org.apache.commons.vfs.provider.sftp.SftpFileSystemConfigBuilder cannot be applied to (org.apache.commons.vfs.FileSystemOptions,org.apache.log4j.chainsaw.vfs.VFSLogFilePatternReceiver.MyUserInfo)
>    [javac]                             SftpFileSystemConfigBuilder.getInstance().setUserInfo(opts, new MyUserInfo(password));
>    [javac]                                                                      ^
>    [javac]
/srv/gump/public/workspace/logging-chainsaw/src/main/java/org/apache/log4j/chainsaw/zeroconf/ZeroConfDeviceModel.java:60:
warning: [deprecation] getAddress() in javax.jmdns.ServiceInfo has been deprecated
>    [javac]                 return info.getAddress().getHostName() + ":" + info.getPort();
>    [javac]                            ^
>    [javac] Note: Some input files use unchecked or unsafe operations.
>    [javac] Note: Recompile with -Xlint:unchecked for details.
>    [javac] 6 errors
>    [javac] 10 warnings
> 
> BUILD FAILED
> /srv/gump/public/workspace/logging-chainsaw/build.xml:81: Compile failed; see the compiler
error output for details.
> 
> Total time: 4 seconds
> ---------------------------------------------
> 
> To subscribe to this information via syndicated feeds:
> - RSS: http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/rss.xml
> - Atom: http://vmgump.apache.org/gump/public/logging-chainsaw/logging-log4j-chainsaw/atom.xml
> 
> ============================== Gump Tracking Only ===
> Produced by Gump version 2.3.
> Gump Run 05000006072010, vmgump:vmgump-public:05000006072010
> Gump E-mail Identifier (unique within run) #28.
> 
> --
> Apache Gump
> http://gump.apache.org/ [Instance: vmgump]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
> For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
> 

Gmane