I have nothing specific in mind. The way things usually work around here is
that you can dig through JIRA and find issues you want to fix. Then you
attach a patch to the ticket with a unit test if possible.
Gary
On Tue, Nov 1, 2016 at 10:02 AM, Guillaume Ch wrote:
> okay, I am available to help
okay, I am available to help to solve issues. Just contact me ;)
Best regards,
Guillaume
On 1 November 2016 16:38:27 GMT+00:00, Guillaume Ch wrote:
>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 jumpin
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
> code, don't you think?
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
code, don't you think?
On the flip side, this component has not seen a relea
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
On Oct 8, 2016 12:21 PM, "Mark Thomas" wrote:
>
> On 08/10/2016 16:46, Guillaume Ch wrote:
> > 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 :
> >
On 08/10/2016 16:46, Guillaume Ch wrote:
> 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);
> - Buildi
A link would be nice :)
On Sat, Oct 8, 2016 at 8:46 AM, Guillaume Ch wrote:
> 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
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 Ma
Whilst trying to use procrun to launch a 3rd party java application that
made use of RMI within Windows I ran into a few issues with the current
release (actually tested against the latest code from SVN). They can be
summarised as follows:
1) Lack of support for wildcards in classpaths as per Java
12 matches
Mail list logo
