You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by Rhys Ulerich <rh...@gmail.com> on 2014/01/03 04:42:36 UTC
Question re: pom.xml comment block in r1414037
Hi Christian,
I'm taking a stab at getting an Ant- and/or Maven-based development
build going following either
https://logging.apache.org/log4cxx/building/maven.html or
https://logging.apache.org/log4cxx/building/ant.html. I'm rusty with
Ant, a noob at Maven, and I'm hitting some trouble.
I noticed there's a large block of dependencies in pom.xml that you
commented out in r1414037 (svn diff -c 1414037) but that the pom.xml
changes don't jive with the commit message (svn log -r 1414037) or the
patch attached to LOGCXX-404. Do you recall why you commented out
that large plugin section within the pom.xml?
Generally,
Anyone have hints for building from a dev checkout with Ant/Maven that
works against trunk? Normally I'm a ./configure && etc fellow but I'd
like to try getting the Maven/Ant stuff working as I suspect it's the
best way to support cross-platform builds.
Thanks,
Rhys
Re: Question re: pom.xml comment block in r1414037
Posted by Christian Grobmeier <gr...@gmail.com>.
On 3 Jan 2014, at 18:31, Rhys Ulerich wrote:
>> Is there a ticket for this? I'd like to help.
>>
>> autotools
>> ant
>> maven
>
> Offhand, not that I'm aware of.
Just saying: I found creating a ticket for each "change" pretty helpful
when generating release notes.
Cheers
> At least by 0.12.0, I'd planned to take a pass through JIRA for
> tickets like LOG4CXX-385 (which Roland mentioned) to make Autotools
> happy again out-of-the-box.
>
> That particular issue is simple enough, and the patch handy enough,
> that it might be worth merging before 0.12.0.
>
> - Rhys
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB
Re: Question re: pom.xml comment block in r1414037
Posted by Rhys Ulerich <rh...@gmail.com>.
> Is there a ticket for this? I'd like to help.
>
> autotools
> ant
> maven
Offhand, not that I'm aware of.
At least by 0.12.0, I'd planned to take a pass through JIRA for
tickets like LOG4CXX-385 (which Roland mentioned) to make Autotools
happy again out-of-the-box.
That particular issue is simple enough, and the patch handy enough,
that it might be worth merging before 0.12.0.
- Rhys
Re: Question re: pom.xml comment block in r1414037
Posted by Alexandru Zbarcea <zb...@gmail.com>.
Hi Rhys,
Is there a ticket for this? I'd like to help.
autotools
ant
maven
+1
Regards,
Alex
On Fri, Jan 3, 2014 at 12:03 PM, Rhys Ulerich <rh...@gmail.com>wrote:
> Hi Roland,
>
> > Just wanted to mention that... GNU autotools based build should remain
> > workable.
>
> Thanks for speaking up. I definitely plan to keep the Autotools alive
> and well. I've been worrying about Ant/Maven since they're what
> permits cross-platform. I personally plan to develop against
> Autotools and then run Ant/Maven as a final sanity check before
> commit.
>
> - Rhys
>
Re: Question re: pom.xml comment block in r1414037
Posted by Rhys Ulerich <rh...@gmail.com>.
Hi Roland,
> Just wanted to mention that... GNU autotools based build should remain
> workable.
Thanks for speaking up. I definitely plan to keep the Autotools alive
and well. I've been worrying about Ant/Maven since they're what
permits cross-platform. I personally plan to develop against
Autotools and then run Ant/Maven as a final sanity check before
commit.
- Rhys
Re: Question re: pom.xml comment block in r1414037
Posted by Alexandru Zbarcea <zb...@gmail.com>.
Hi Roland,
You may find these commits useful:
https://github.com/azbarcea/log4cxx/pull/1/files
These commits I remember Christian pushed them in the main/trunk. The
first, is similar to yours.
As a rule of thumb, we should not keep in the repo, generated files, even
if they are .h files. You end up making hooks (like rm -fr <generated
files>).
Regards,
Alex
On Fri, Jan 3, 2014 at 11:55 AM, Roland Uuesoo <ro...@gmail.com> wrote:
> Hi everybody!
>
> Just wanted to mention that... GNU autotools based build should remain
> workable.
>
> I have used log4cxx with autotools for 3 years at least. Last year it was
> added to buildroot project which uses autotools also.
>
>
> http://git.buildroot.net/buildroot/commit/?id=6ebb930b694e97e5cf85a724957d9c0eb129dea7
>
> Buildroot http://buildroot.uclibc.org/ (allows cross compilation of
> software for many diffferent embedded CPU architectures from linux
> environment)
>
> Notice, trunk tree from old log4cxx repository needed one patch minimun to
> be able to build... LOG4CXX_385
>
> https://github.com/roland2025/log4cxx this builds on ARM (tested by me) -
>
> confirmed working GCC/G++ versions (application running in embedded
> device, using RollingFileAppender with FixedWindowRollingPolicy. variable
> work loads, haven't seen crashes caused by log4cxx )
>
> Intel PXA270 GCC4.6.1
> Freescale i.MX25 GCC4.5.3
> Freescale i.MX53 GCC4.5.3
> Freescale i.MX51 GCC 4.?
>
> http://www.artila.com/en/p_som.html
> M501(Atmel 9200) GCC3.3.4
> M502(Atmel 9G20) GCC4.6.1
>
>
> I've only had trouble on PC with extra high logging load (TRACE) when some
> apr library crashes while using socketappender.
>
>
> Best regards,
> Roland Uuesoo
>
>
>
> On Fri, Jan 3, 2014 at 4:26 PM, Rhys Ulerich <rh...@gmail.com>wrote:
>
>> > I tend to believe that we should start to build log4cxx with Ant. My
>> feeling is that
>> > Maven was using Ant to build it. If the Ant stuff works, we could
>> renenable the Maven build for it,
>> > or leave it out.
>>
>> Ah, sorry for crying wolf. I had hit a classpath issue with the cpptasks
>> JAR. I didn't recognize it at first from the stacktrace.
>>
>> With those lines enabled in the pom.xml I can get somewhere. Christian is
>> the pom used in some automated fashion by Apache Infra jobs? Do I need to
>> worry about breaking a cronjob if I remove the comments around those
>> plugins?
>>
>> - Rhys
>>
>
>
Re: Question re: pom.xml comment block in r1414037
Posted by Roland Uuesoo <ro...@gmail.com>.
Hi everybody!
Just wanted to mention that... GNU autotools based build should remain
workable.
I have used log4cxx with autotools for 3 years at least. Last year it was
added to buildroot project which uses autotools also.
http://git.buildroot.net/buildroot/commit/?id=6ebb930b694e97e5cf85a724957d9c0eb129dea7
Buildroot http://buildroot.uclibc.org/ (allows cross compilation of
software for many diffferent embedded CPU architectures from linux
environment)
Notice, trunk tree from old log4cxx repository needed one patch minimun to
be able to build... LOG4CXX_385
https://github.com/roland2025/log4cxx this builds on ARM (tested by me) -
confirmed working GCC/G++ versions (application running in embedded device,
using RollingFileAppender with FixedWindowRollingPolicy. variable work
loads, haven't seen crashes caused by log4cxx )
Intel PXA270 GCC4.6.1
Freescale i.MX25 GCC4.5.3
Freescale i.MX53 GCC4.5.3
Freescale i.MX51 GCC 4.?
http://www.artila.com/en/p_som.html
M501(Atmel 9200) GCC3.3.4
M502(Atmel 9G20) GCC4.6.1
I've only had trouble on PC with extra high logging load (TRACE) when some
apr library crashes while using socketappender.
Best regards,
Roland Uuesoo
On Fri, Jan 3, 2014 at 4:26 PM, Rhys Ulerich <rh...@gmail.com> wrote:
> > I tend to believe that we should start to build log4cxx with Ant. My
> feeling is that
> > Maven was using Ant to build it. If the Ant stuff works, we could
> renenable the Maven build for it,
> > or leave it out.
>
> Ah, sorry for crying wolf. I had hit a classpath issue with the cpptasks
> JAR. I didn't recognize it at first from the stacktrace.
>
> With those lines enabled in the pom.xml I can get somewhere. Christian is
> the pom used in some automated fashion by Apache Infra jobs? Do I need to
> worry about breaking a cronjob if I remove the comments around those
> plugins?
>
> - Rhys
>
Re: Question re: pom.xml comment block in r1414037
Posted by Christian Grobmeier <gr...@gmail.com>.
On 3 Jan 2014, at 15:26, Rhys Ulerich wrote:
>> I tend to believe that we should start to build log4cxx with Ant. My
> feeling is that
>> Maven was using Ant to build it. If the Ant stuff works, we could
> renenable the Maven build for it,
>> or leave it out.
>
> Ah, sorry for crying wolf. I had hit a classpath issue with the
> cpptasks
> JAR. I didn't recognize it at first from the stacktrace.
>
> With those lines enabled in the pom.xml I can get somewhere. Christian
> is
> the pom used in some automated fashion by Apache Infra jobs? Do I need
> to
> worry about breaking a cronjob if I remove the comments around those
> plugins?
Not that I am aware of.
Maybe there is some long time unmaintained CI server, but we most likely
will be notified if it would break.
Besides that there should be nothing. One thing all projects (should)
have is a DOAP file. But i already cared about its location when I moved
around the svn location.
In short: feel free to edit as you need it.
Cheers
>
> - Rhys
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB
Re: Question re: pom.xml comment block in r1414037
Posted by Rhys Ulerich <rh...@gmail.com>.
> I tend to believe that we should start to build log4cxx with Ant. My
feeling is that
> Maven was using Ant to build it. If the Ant stuff works, we could
renenable the Maven build for it,
> or leave it out.
Ah, sorry for crying wolf. I had hit a classpath issue with the cpptasks
JAR. I didn't recognize it at first from the stacktrace.
With those lines enabled in the pom.xml I can get somewhere. Christian is
the pom used in some automated fashion by Apache Infra jobs? Do I need to
worry about breaking a cronjob if I remove the comments around those
plugins?
- Rhys
Re: Question re: pom.xml comment block in r1414037
Posted by Christian Grobmeier <gr...@gmail.com>.
On 3 Jan 2014, at 11:55, Thorsten Schöning wrote:
> Guten Tag Christian Grobmeier,
> am Freitag, 3. Januar 2014 um 11:36 schrieben Sie:
>
>> The question actually is: what is the best way to build a
>> multi-platform
>> C++ project of that kind?
>
> I have no experience, we do C++ and use log4cxx on Windows and with
> Embarcaderos C++ Builder only. PCRE e.g. uses CMAKE, which seems
> widely known, but was never used by us.
>
> Maybe we should first spent quite some time looking at what log4cxx
> already
> provides, try to get that running and decide later. Build tools and
> all that stuff seem to have good potential for flamewars. :-)
Makes sense :-)
Well, I can help with Maven related issues in regards to the site.
I am unfortunately not good with building C++ things and maintaining
that part of the build.
I tend to believe that we should start to build log4cxx with Ant. My
feeling is that
Maven was using Ant to build it. If the Ant stuff works, we could
renenable the Maven build for it,
or leave it out.
>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>
> Telefon...........05151- 9468- 55
> Fax...............05151- 9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB
Re: Question re: pom.xml comment block in r1414037
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Christian Grobmeier,
am Freitag, 3. Januar 2014 um 11:36 schrieben Sie:
> The question actually is: what is the best way to build a multi-platform
> C++ project of that kind?
I have no experience, we do C++ and use log4cxx on Windows and with
Embarcaderos C++ Builder only. PCRE e.g. uses CMAKE, which seems
widely known, but was never used by us.
Maybe we should first spent quite some time looking at what log4cxx already
provides, try to get that running and decide later. Build tools and
all that stuff seem to have good potential for flamewars. :-)
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Question re: pom.xml comment block in r1414037
Posted by Christian Grobmeier <gr...@gmail.com>.
Hi,
On 3 Jan 2014, at 4:42, Rhys Ulerich wrote:
> I noticed there's a large block of dependencies in pom.xml that you
> commented out in r1414037 (svn diff -c 1414037) but that the pom.xml
> changes don't jive with the commit message (svn log -r 1414037) or the
> patch attached to LOGCXX-404. Do you recall why you commented out
> that large plugin section within the pom.xml?
The only thing i can recall is that I needed to update the site
with maven. Thats maybe likely that I commented all that stuff, because
it looked unnecessary or even broke the site build.
In general, the whole Maven build here is pretty oldschool.
> Anyone have hints for building from a dev checkout with Ant/Maven that
> works against trunk? Normally I'm a ./configure && etc fellow but I'd
> like to try getting the Maven/Ant stuff working as I suspect it's the
> best way to support cross-platform builds.
I think others should comment here as well.
So far, the pom.xml accesses the ant stuff to build something.
I think there are better ways to work with C++ and I believe you
folks should do whats usus in the C++ world and what you are familiar
with.
I'd even say, we should just maintain one build system - either maven,
or ant
or whatever else is good (gradle, make, buildr).
From my point of view, Maven currently just has the benefit to create a
proper
website in an instant. We could keep this mvn site ability but move the
actual
building things to whatever works good.
The question actually is: what is the best way to build a multi-platform
C++ project
of that kind?
Cheers
Christian
>
> Thanks,
> Rhys
---
http://www.grobmeier.de
The Zen Programmer: http://bit.ly/12lC6DL
@grobmeier
GPG: 0xA5CC90DB