Re: NAnt and Mono (was Re: Happy to help)

2016-09-12 Thread Ryan Boggs
On Sep 12, 2016 7:43 AM, "Stefan Bodewig"  wrote:
>
> On 2016-09-12, Ryan Boggs wrote:
>
> > On Sep 12, 2016 1:43 AM, "Stefan Bodewig"  wrote:
>
> >> It looks as if System.dll now resides in mono/4.0-api rather than
> >> mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll).
>
> > Ok, initial glance tells me that this could be fixed simply by updating
the
> > app.config file to look in the new *-api directories. I can try to fix
this
> > if time allows.
>
> Thanks.
>
> > Are you trying to build the log4net from the master branch?
>
> trunk - log4net is still in svn. :-)
Ah, ok.
>
> > And what platform are you using to build?Linux?
>
> The error occured on Linux which is where I do all my development.
>
> My preference would be able to use Mono on Windows as well so that I can
> build a log4net release for all supported platforms in a single build
> process. Unfortunately NAnt doesn't seem to detect any version of Mono
> I've installed on my Win7 VM at all. I tried Mono 3.12.1 and 4.4.2.11.

Yeah, i noticed that this morning as well. Looks like i never got around to
putting in that setup after they fixed the registry settings in the
installer.  Since (i think off the top of my head) this is also in the
app.config file, i can try to kill two birds with one stone. Ill see what i
can do.

Thanks,
Ryan
>
> Stefan


Re: NAnt and Mono (was Re: Happy to help)

2016-09-12 Thread Stefan Bodewig
On 2016-09-12, Ryan Boggs wrote:

> On Sep 12, 2016 1:43 AM, "Stefan Bodewig"  wrote:

>> It looks as if System.dll now resides in mono/4.0-api rather than
>> mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll).

> Ok, initial glance tells me that this could be fixed simply by updating the
> app.config file to look in the new *-api directories. I can try to fix this
> if time allows.

Thanks.

> Are you trying to build the log4net from the master branch?

trunk - log4net is still in svn. :-)

> And what platform are you using to build?Linux?

The error occured on Linux which is where I do all my development.

My preference would be able to use Mono on Windows as well so that I can
build a log4net release for all supported platforms in a single build
process. Unfortunately NAnt doesn't seem to detect any version of Mono
I've installed on my Win7 VM at all. I tried Mono 3.12.1 and 4.4.2.11.

Stefan


Re: NAnt and Mono (was Re: Happy to help)

2016-09-12 Thread Ryan Boggs
On Sep 12, 2016 1:43 AM, "Stefan Bodewig"  wrote:
>
> On 2016-09-11, Ryan Boggs wrote:
>
> > On Sep 11, 2016 9:21 AM, "Stefan Bodewig"  wrote:
>
> >> On 2016-09-11, Ryan Boggs wrote:
>
> >>> On Sep 11, 2016 2:23 AM, "Stefan Bodewig"  wrote:
>
>  On 2016-09-09, Ryan Boggs wrote:
>
> > Fyi - One thing i do know regarding NAnt, mono, and windows is that
> > when
> > they updated the installer for 4, they omitted the registry settings
> > for
> > the first couple of releases so NAnt couldn't find it.
>
>  I went back to 3.12.1 after your comment but NAnt 0.92 still doesn't
>  recognize Mono.
>
>  On Linux things aren't really any better as NAnt considers Mono 4.x
as
>  "mono-4.5" framework and won't build anything at all as the framework
> > is
>  not supported. And it really doesn't seem to find the compiler and
>  reference assemblies (that are likely not there, anyway) when I run
> > Nant
>  with -t:mono-4.0
>
> >>> What version of NAnt are you using?
>
> >> 0.92 downloaded from the project site.
> > Can you do me a favor and try it with the last nightly build? I did
commit
> > some changes related to mono-4.5 that should be in that build.
>
> At least it doesn't complain about mono-4.5 not being supported but when
> trying to build log4net
>
> ,
> | $ nant
> | WARNING: The runtime version supported by this application is
unavailable.
> | Using default runtime: v4.0.30319
> | NAnt 0.93 (Build 0.93.5521.0; nightly; 12.02.2015)
> | Copyright (C) 2001-2015 Gerry Shaw
> | http://nant.sourceforge.net
> |
> |
> | BUILD FAILED
> |
> | Mono 4.0 Profile (mono-4.0) is not installed, or not correctly
configured.
> |
> | The 'System.dll' assembly does not exist in framework assembly
directory '/usr/lib/pkgconfig/../../lib/mono/4.0'.
> |
> | For more information regarding the cause of the build failure, run the
build again in debug mode.
> |
> | Try 'nant -help' for more information
> `
>
> It looks as if System.dll now resides in mono/4.0-api rather than
> mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll).

Ok, initial glance tells me that this could be fixed simply by updating the
app.config file to look in the new *-api directories. I can try to fix this
if time allows. Are you trying to build the log4net from the master branch?
And what platform are you using to build?Linux?

Thanks,
Ryan
>
> Stefan


Re: NAnt and Mono (was Re: Happy to help)

2016-09-12 Thread Stefan Bodewig
On 2016-09-11, Ryan Boggs wrote:

> On Sep 11, 2016 9:21 AM, "Stefan Bodewig"  wrote:

>> On 2016-09-11, Ryan Boggs wrote:

>>> On Sep 11, 2016 2:23 AM, "Stefan Bodewig"  wrote:

 On 2016-09-09, Ryan Boggs wrote:

> Fyi - One thing i do know regarding NAnt, mono, and windows is that
> when
> they updated the installer for 4, they omitted the registry settings
> for
> the first couple of releases so NAnt couldn't find it.

 I went back to 3.12.1 after your comment but NAnt 0.92 still doesn't
 recognize Mono.

 On Linux things aren't really any better as NAnt considers Mono 4.x as
 "mono-4.5" framework and won't build anything at all as the framework
> is
 not supported. And it really doesn't seem to find the compiler and
 reference assemblies (that are likely not there, anyway) when I run
> Nant
 with -t:mono-4.0

>>> What version of NAnt are you using?

>> 0.92 downloaded from the project site.
> Can you do me a favor and try it with the last nightly build? I did commit
> some changes related to mono-4.5 that should be in that build.

At least it doesn't complain about mono-4.5 not being supported but when
trying to build log4net

,
| $ nant
| WARNING: The runtime version supported by this application is unavailable.
| Using default runtime: v4.0.30319
| NAnt 0.93 (Build 0.93.5521.0; nightly; 12.02.2015)
| Copyright (C) 2001-2015 Gerry Shaw
| http://nant.sourceforge.net
| 
| 
| BUILD FAILED
| 
| Mono 4.0 Profile (mono-4.0) is not installed, or not correctly configured.
| 
| The 'System.dll' assembly does not exist in framework assembly directory 
'/usr/lib/pkgconfig/../../lib/mono/4.0'.
| 
| For more information regarding the cause of the build failure, run the build 
again in debug mode.
| 
| Try 'nant -help' for more information
`

It looks as if System.dll now resides in mono/4.0-api rather than
mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll).

Stefan


Re: NAnt and Mono (was Re: Happy to help)

2016-09-11 Thread Ryan Boggs
On Sep 11, 2016 9:21 AM, "Stefan Bodewig"  wrote:
>
> On 2016-09-11, Ryan Boggs wrote:
>
> > On Sep 11, 2016 2:23 AM, "Stefan Bodewig"  wrote:
>
> >> On 2016-09-09, Ryan Boggs wrote:
>
> >>> Fyi - One thing i do know regarding NAnt, mono, and windows is that
when
> >>> they updated the installer for 4, they omitted the registry settings
for
> >>> the first couple of releases so NAnt couldn't find it.
>
> >> I went back to 3.12.1 after your comment but NAnt 0.92 still doesn't
> >> recognize Mono.
>
> >> On Linux things aren't really any better as NAnt considers Mono 4.x as
> >> "mono-4.5" framework and won't build anything at all as the framework
is
> >> not supported. And it really doesn't seem to find the compiler and
> >> reference assemblies (that are likely not there, anyway) when I run
Nant
> >> with -t:mono-4.0
>
> > What version of NAnt are you using?
>
> 0.92 downloaded from the project site.
Can you do me a favor and try it with the last nightly build? I did commit
some changes related to mono-4.5 that should be in that build.

Thanks,
Ryan
>
> ,
> | WARNING: The runtime version supported by this application is
unavailable.
> | Using default runtime: v4.0.30319
> | NAnt 0.92 (Build 0.92.4543.0; release; 09.06.2012)
> `
>
> Stefan


Re: NAnt and Mono (was Re: Happy to help)

2016-09-11 Thread Stefan Bodewig
On 2016-09-11, Ryan Boggs wrote:

> On Sep 11, 2016 2:23 AM, "Stefan Bodewig"  wrote:

>> On 2016-09-09, Ryan Boggs wrote:

>>> Fyi - One thing i do know regarding NAnt, mono, and windows is that when
>>> they updated the installer for 4, they omitted the registry settings for
>>> the first couple of releases so NAnt couldn't find it.

>> I went back to 3.12.1 after your comment but NAnt 0.92 still doesn't
>> recognize Mono.

>> On Linux things aren't really any better as NAnt considers Mono 4.x as
>> "mono-4.5" framework and won't build anything at all as the framework is
>> not supported. And it really doesn't seem to find the compiler and
>> reference assemblies (that are likely not there, anyway) when I run Nant
>> with -t:mono-4.0

> What version of NAnt are you using?

0.92 downloaded from the project site.

,
| WARNING: The runtime version supported by this application is unavailable.
| Using default runtime: v4.0.30319
| NAnt 0.92 (Build 0.92.4543.0; release; 09.06.2012)
`

Stefan


Re: NAnt and Mono (was Re: Happy to help)

2016-09-11 Thread Ryan Boggs
On Sep 11, 2016 2:23 AM, "Stefan Bodewig"  wrote:
>
> On 2016-09-09, Ryan Boggs wrote:
>
> > Fyi - One thing i do know regarding NAnt, mono, and windows is that when
> > they updated the installer for 4, they omitted the registry settings for
> > the first couple of releases so NAnt couldn't find it.
>
> I went back to 3.12.1 after your comment but NAnt 0.92 still doesn't
> recognize Mono.
>
> On Linux things aren't really any better as NAnt considers Mono 4.x as
> "mono-4.5" framework and won't build anything at all as the framework is
> not supported. And it really doesn't seem to find the compiler and
> reference assemblies (that are likely not there, anyway) when I run Nant
> with -t:mono-4.0

What version of NAnt are you using?
>
> Stefan
>


NAnt and Mono (was Re: Happy to help)

2016-09-11 Thread Stefan Bodewig
On 2016-09-09, Ryan Boggs wrote:

> Fyi - One thing i do know regarding NAnt, mono, and windows is that when
> they updated the installer for 4, they omitted the registry settings for
> the first couple of releases so NAnt couldn't find it.

I went back to 3.12.1 after your comment but NAnt 0.92 still doesn't
recognize Mono.

On Linux things aren't really any better as NAnt considers Mono 4.x as
"mono-4.5" framework and won't build anything at all as the framework is
not supported. And it really doesn't seem to find the compiler and
reference assemblies (that are likely not there, anyway) when I run Nant
with -t:mono-4.0

Stefan



Re: Happy to help

2016-09-09 Thread Ryan Boggs
On Sep 9, 2016 7:03 AM, "Stefan Bodewig"  wrote:
>
> On 2016-09-09, Ryan Boggs wrote:
>
> > On Sep 8, 2016 9:23 PM, "Stefan Bodewig"  wrote:
>
> >> It feels like this is only a short term solution as NAnt is becoming
> >> more of an obstacle than help by not supporting recent frameworks
> >> anymore. So I expect we'll start discussing alternative solutions
> >> soonish.
>
> > If people wanna help get NAnt up to speed with the framework support, it
> > would be appreciated. I hit a wall with it.
>
> Ryan, I really appreciate NAnt and your work on it - and I think you
> know that. It has helped us tremendously.  What I said wasn't intended
> as a slant against NAnt.
No worries, I didn't take it as a slant. I was honestly saying that i hit a
wall with it and was seeing if there were others on the list who would want
to take a look at it to get it where you guys need it to be.

Fyi - One thing i do know regarding NAnt, mono, and windows is that when
they updated the installer for 4, they omitted the registry settings for
the first couple of releases so NAnt couldn't find it. They put it back
when i inquired about it but i think they changed the registry keys a bit.
I remember working on it some months ago but i forgot how far i got or if i
committed those changes.  I would have to look.

Hope that sheds some light for you guys.

>
> I wish I had time to contribute to NAnt, but you see yourself how little
> I manage to contribute to log4net.
I understand. I'm in the same boat myself.
>
> Stefan

Thanks,
Ryan


Re: Happy to help

2016-09-09 Thread Stefan Bodewig
On 2016-09-09, Ryan Boggs wrote:

> On Sep 8, 2016 9:23 PM, "Stefan Bodewig"  wrote:

>> It feels like this is only a short term solution as NAnt is becoming
>> more of an obstacle than help by not supporting recent frameworks
>> anymore. So I expect we'll start discussing alternative solutions
>> soonish.

> If people wanna help get NAnt up to speed with the framework support, it
> would be appreciated. I hit a wall with it.

Ryan, I really appreciate NAnt and your work on it - and I think you
know that. It has helped us tremendously.  What I said wasn't intended
as a slant against NAnt.

I wish I had time to contribute to NAnt, but you see yourself how little
I manage to contribute to log4net.

Stefan


Re: Happy to help

2016-09-08 Thread Ryan Boggs
On Sep 8, 2016 9:23 PM, "Stefan Bodewig"  wrote:
>
> Hi Jim
>
> On 2016-09-08, Jim Christopher wrote:
>
> > I hear log4net needs some help.  I'm happy to offer what time I can.
>
> this is great.
>
> > Please point me at something you'd like me to tackle.
>
> The log4net JIRA holds a lot of open tickets. Maybe something looks
> interesting to you.
>
> Right now I use the time I have on integrating the new .NET Core
> assemblies and nuget package creation with the NAnt build process in
> order to become able to cut a new release.
>
> It feels like this is only a short term solution as NAnt is becoming
> more of an obstacle than help by not supporting recent frameworks
> anymore. So I expect we'll start discussing alternative solutions
> soonish.
If people wanna help get NAnt up to speed with the framework support, it
would be appreciated. I hit a wall with it.

>
> What I wish I had time to look into is verifying that all tickets that
> have been resolved with target version 1.3.0 - a branch we've abandoned
> by now - have actually been ported back to trunk. I'm afraid we've
> missed some.
>
> Apart from that we know RollingFileAppender has a lot of issues, likely
> so many that writing a replacement might be in order.
>
> Please yell if something feels wrong and clumsy.
>
> Oh, if you intend to contribute more than just smallish patches it would
> be good if you signed a contributor's agreement - i.e. you legally allow
> the ASF to publish your contributions.
>
> https://www.apache.org/licenses/#clas
>
> Cheers
>
> Stefan

Thanks,
Ryan


Re: Happy to help

2016-09-08 Thread Stefan Bodewig
Hi Jim

On 2016-09-08, Jim Christopher wrote:

> I hear log4net needs some help.  I'm happy to offer what time I can.

this is great.

> Please point me at something you'd like me to tackle.

The log4net JIRA holds a lot of open tickets. Maybe something looks
interesting to you.

Right now I use the time I have on integrating the new .NET Core
assemblies and nuget package creation with the NAnt build process in
order to become able to cut a new release.

It feels like this is only a short term solution as NAnt is becoming
more of an obstacle than help by not supporting recent frameworks
anymore. So I expect we'll start discussing alternative solutions
soonish.

What I wish I had time to look into is verifying that all tickets that
have been resolved with target version 1.3.0 - a branch we've abandoned
by now - have actually been ported back to trunk. I'm afraid we've
missed some.

Apart from that we know RollingFileAppender has a lot of issues, likely
so many that writing a replacement might be in order.

Please yell if something feels wrong and clumsy.

Oh, if you intend to contribute more than just smallish patches it would
be good if you signed a contributor's agreement - i.e. you legally allow
the ASF to publish your contributions.

https://www.apache.org/licenses/#clas

Cheers

Stefan