Re: [daemon] moving to git ? and bump java version.

The code could be made better by fixing bug reported in JIRA... Gary On Wed, Jul 19, 2017 at 4:41 PM, wrote: > > Yes, that's mentioned in my previous mail, I was also curious to know from > the C developers here in dev-list that how can we make *that* C code > better?

RE: [daemon] moving to git ? and bump java version.

Yes, that's mentioned in my previous mail, I was also curious to know from the C developers here in dev-list that how can we make *that* C code better? basically I'm looking findbug, checkstyle, jococo, junit *equivalent* for C code. CodeSentry provide a cloud version for scanning opensource

Re: [daemon] moving to git ? and bump java version.

At thus point I would like to see: - A release - Go through JIRA and fix issues - A release We can update to Java 6 to allow the project to be built by Java 9 at any time, no big deal IMO. Crud, the oldest Java I have installed is Java 6. Hm, I'll push out Java 6 as the req and get that out of

Re: [daemon] moving to git ? and bump java version.

On Jul 16, 2017 11:49 AM, "Matt Sicker" wrote: C quality somewhat depends on which version of C you're trying to remain compatible with (I'm guessing C89 due to Windows, though I could be wrong). Valgrind and other tracing tools are typically used. Valgrind is a default

Re: [daemon] moving to git ? and bump java version.

There is no fixed process to determine when it is releases time. Sometimes a component has momentum and a release manager is picked and leads the way, sometimes a committer needs a release and volunteers to manage a release. Gary On Jul 17, 2017 06:00, "Amey Jadiye" wrote:

Re: [daemon] moving to git ? and bump java version.

Hi Gary, I will take a look at pending issues if something is blocker to release, I see already 9 issues are done for 1.1.0 release . if we are ok with these 9, anyone can release it. BTW how do you guys decide that "this is a time to release!" for any component ? Regards, Amey On Jul 16,

Re: [daemon] moving to git ? and bump java version.

If someone here is really going to put time and energy into daemon, it would be fantastic to start with a release. It's been so long... Then fiddle away on tweaks, and release again. Gary On Jul 16, 2017 08:49, "Matt Sicker" wrote: > C quality somewhat depends on which

Re: [daemon] moving to git ? and bump java version.

C quality somewhat depends on which version of C you're trying to remain compatible with (I'm guessing C89 due to Windows, though I could be wrong). Valgrind and other tracing tools are typically used. I'd take a look at what OpenOffice is doing for local examples (though they have a crazy build

Re: [daemon] moving to git ? and bump java version.

On 15 July 2017 at 15:21, Amey Jadiye wrote: > Yes, that's mentioned in my previous mail, I was also curious to know from > the C developers here in dev-list that how can we make *that* C code > better? basically I'm looking findbug, checkstyle, jococo, junit >

Re: [daemon] moving to git ? and bump java version.

Yes, that's mentioned in my previous mail, I was also curious to know from the C developers here in dev-list that how can we make *that* C code better? basically I'm looking findbug, checkstyle, jococo, junit *equivalent* for C code. Regards, Amey On Sat, Jul 15, 2017 at 7:44 PM, sebb

Re: [daemon] moving to git ? and bump java version.

Also note that there is hardly any Java code; most of it is written in C. On 14 July 2017 at 00:43, Gary Gregory wrote: > It seems OK to me to update to Java 6 for now and get this to compile under > java 9 for those folks who will try... > > Gary > > On Wed, Jul 12, 2017

Re: [daemon] moving to git ? and bump java version.

It seems OK to me to update to Java 6 for now and get this to compile under java 9 for those folks who will try... Gary On Wed, Jul 12, 2017 at 9:09 AM, Amey Jadiye wrote: > Thanks for great insights Mark. > > On Wed, Jul 12, 2017, 9:28 PM Mark Thomas

Re: [daemon] moving to git ? and bump java version.

Thanks for great insights Mark. On Wed, Jul 12, 2017, 9:28 PM Mark Thomas wrote: > On 12 July 2017 16:33:01 CEST, Matt Sicker wrote: > >Are there plans to require 1.7 for Tomcat anytime? Otherwise, it might > >be > >necessary to make a new major version of

Re: [daemon] moving to git ? and bump java version.

On 12 July 2017 16:33:01 CEST, Matt Sicker wrote: >Are there plans to require 1.7 for Tomcat anytime? Otherwise, it might >be >necessary to make a new major version of daemon eventually for Java 8 >or 9. Tomcat major versions are aligned with Java EE versions which in turn have

Re: [daemon] moving to git ? and bump java version.

Are there plans to require 1.7 for Tomcat anytime? Otherwise, it might be necessary to make a new major version of daemon eventually for Java 8 or 9. Anyways, 1.6 minimum makes sense to me mainly due to Java 9's compiler not supporting Java 5 targets anymore. On 12 July 2017 at 09:19, Mark

Re: [daemon] moving to git ? and bump java version.

On 11 July 2017 21:02:54 CEST, Amey Jadiye wrote: >Hi Daemon Maintainers / All, > >Daemon seems to be still being maintained on svn, do we have any plan >moving code base to git ? No preference on this. >As fact there is low activity in daemon no one thought of bumping

Re: [daemon] moving to git ? and bump java version.

As far as migrating from svn to git, it's just busy work an Apache Committers needs to volunteer to do. Certainly not critical, especially since this component does not get much attention these days. Gary On Tue, Jul 11, 2017 at 12:02 PM, Amey Jadiye wrote: > Hi Daemon

Re: [daemon] moving to git ? and bump java version.

The only reason to update to Java 6 is that Java 9 will no longer compiler for targets below Java 6, which is fine with me. Java 7 would also be OK by me. Gary On Tue, Jul 11, 2017 at 12:02 PM, Amey Jadiye wrote: > Hi Daemon Maintainers / All, > > Daemon seems to be still

Re: [daemon] moving to git ? and bump java version.

We could migrate to git as we've been slowly doing for most of Commons. Someone needs to take charge and handle it, though. A lazy vote thread to do so is the usual way to start the process. On 11 July 2017 at 14:02, Amey Jadiye wrote: > Hi Daemon Maintainers / All, > >

[daemon] moving to git ? and bump java version.

Hi Daemon Maintainers / All, Daemon seems to be still being maintained on svn, do we have any plan moving code base to git ? As fact there is low activity in daemon no one thought of bumping version from 1.5 to 1.6 OR we are keeping it purposefully to 1.5 ? shall we bump it minimum to 1.6 ?