Thank you for your quick response,
> The foundation doesn't have a vision for Daemon. The direction of the
> project is set from the ground up by the community using and developing the
> software rather than from the top down. Project direction is agreed by
> consensus.
> You are proposing a
Hello,
Is there some ready-to-use checkstyle descriptors for Java,C etc. to help
developers to have an uniformed formatting on each Apache commons projects ?
Best regards,
Hello everyone,
I would like to give you a feedback on my developments that I made on my
GIT copy of the Apache Daemon project (see
https://github.com/gchauvet/commons-daemon).
My goal is to be able to provide a more homogeneous way of writing a Java
service regardless of the host operating
Hello,
I've noticed that daemon parent pom version is 35, why not upgrading to 41
now ?
okay, I am available to help to solve issues. Just contact me ;)
Best regards,
Guillaume
2016-11-01 16:55 GMT+01:00 Gary Gregory :
> Hi,
>
> I'm not sure I get the big picture here of changes like this one... Since
> Microsoft has a free tools [1] and this code targets the Microsoft
> environment, it seems like jumping through more hoops to "de-Microsoft" the
Hi,
I've created a pull request at
https://github.com/apache/commons-daemon/pull/1
If someone of Daemon team can review my proposal, I would be grateful ;).
Best regards,
>
> With all of the change above, my question would be "Why?". What are the
> benefits of the proposed changes? What are the impacts on the other
> supported operating systems?
>
Originally, I was surprised by the use of MSVC as main toolchain for
Windows, then I've planned to allow Apache Daemon
Dear Daemon's developers,
I'm working on some improvements for Apache Daemon on my Github fork of
your mirror and I would like to know your opinions about these
changes/involvements :
- Removing MSVC specific features (e.g try/catch);
- Building C sources with MinGW for windows; [1]
- Migrating