Re: request a "native" Git repository

Guten Tag Alexandru Zbarcea, am Freitag, 3. Januar 2014 um 21:24 schrieben Sie: > I propose to request for a "native" git repository. I vote against because I prefer Subversion anyways, but from my understanding Apache still focuses on it and I really don't see the benefit from switching to anoth

setup Continuous Integration

Hi, I created a ticket #418 to address the Continuous Integration. I believe a healthy project should provide confidence that it builds, the tests work and so on. Based on Christian suggestion I propose on setting a CI on the http://ci.apache.org

request a "native" Git repository

Hi Everyone, I propose to request for a "native" git repository. Cheers, Alex On Fri, Jan 3, 2014 at 1:46 PM, Christian Grobmeier wrote: > On 3 Jan 2014, at 18:04, Alexandru Zbarcea wrote: > >> Can we consider the .git (git://git.apache.org/log4cxx.git) repo as the >> main repo and not the su

[Logging-log4cxx Wiki] Trivial Update of "AlexZbarcea" by AlexZbarcea

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Logging-log4cxx Wiki" for change notification. The "AlexZbarcea" page has been changed by AlexZbarcea: https://wiki.apache.org/logging-log4cxx/AlexZbarcea New page: ##master-page:HomepageTemplate #format wiki #language en =

Re: Create new branches and revert trunk

> As we now know that the website is not build from trunk automatically... (Thank you for checking). > I would be fine with leaving trunk as it is and using it for upcoming > development, but creating "new" release branches from the history of > the trunk for 0.11.0 and 0.11.1 as described before

Re: Create new branches and revert trunk

Guten Tag Rhys Ulerich, am Freitag, 3. Januar 2014 um 16:59 schrieben Sie: > I like the 0.11.0, 0.11.1, and 0.12.0 plan that Thorsten set out with > the implication that "trunk" means the last, public, stable release. > That makes the public APIs and website reflect stable in a > straightforward m

Re: SVN Access granted

Guten Tag Christian Grobmeier, am Freitag, 3. Januar 2014 um 19:36 schrieben Sie: > Personally I would suggest we use log4cxx-dev for commit notifications > until the commit traffic > becomes so overwhelming that we can't manage it anymore Even then every reader of the dev list should be able to

Re: Question re: pom.xml comment block in r1414037

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

Re: Question re: pom.xml comment block in r1414037

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 clas

Re: SVN Access granted

> 2) in log4j we use the log4j-dev@ list for commits. You might want to > reconsider using log4cxx-dev as well > > Personally I would suggest we use log4cxx-dev for commit notifications until > the commit traffic > becomes so overwhelming that we can't manage it anymore > > Wdyt? Let's go with you

Re: Create new branches and revert trunk

On 3 Jan 2014, at 18:04, Alexandru Zbarcea wrote: Can we consider the .git (git://git.apache.org/log4cxx.git) repo as the main repo and not the subversion one? http://git.apache.org/ Can we push/commit to this git repository directly? Currently this is a git mirror of the svn repos. However

Re: How gets the website published?

Basically we'll need to co-operate with publishing the website. Here are instructions: http://wiki.apache.org/logging/ManagingTheWebSite Basically you can say the website is generated via in example maven, then committed to a special svn branch: https://svn.apache.org/repos/infra/websites/produc

Re: SVN Access granted

On 3 Jan 2014, at 17:10, Rhys Ulerich wrote: Is there a commit notification mailing list for our repo? Yes there should be one - actually it should be the dev list. Just on a hunch, I tried log4cxx-cvs-subscr...@apache.org but it bounced. I'd prefer having a separate commit notification list

Re: please grant karma

Hi, i fixed the username, now you can edit Cheers On 3 Jan 2014, at 16:03, Alexandru Zbarcea wrote: Hi Christian, Thank you for pointing that out to me. I created the user AlexZbarceaon the moinmoin: https://wiki.apache.org/logging-log4cx

[Logging-log4cxx Wiki] Update of "ContributorsGroup" by ChristianGrobmeier

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Logging-log4cxx Wiki" for change notification. The "ContributorsGroup" page has been changed by ChristianGrobmeier: https://wiki.apache.org/logging-log4cxx/ContributorsGroup?action=diff&rev1=3&rev2=4 Comment: fixed alex use

Re: Question re: pom.xml comment block in r1414037

> 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 sim

Re: Question re: pom.xml comment block in r1414037

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 wrote: > Hi Roland, > > > Just wanted to mention that... GNU autotools based build should remain > > workable. > > Thanks for speaking up. I definitely p

Re: Question re: pom.xml comment block in r1414037

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

Re: Create new branches and revert trunk

> Can we push/commit to this git repository directly? Doesn't look like it... "This is a collection of read-only Git mirrors of Apache codebases." > Can we set up a travis/jenkins for CI? Dunno. Is there some CI infrastructure already available through the ASF? - Rhys

Re: Create new branches and revert trunk

Hi, Can we consider the .git (git://git.apache.org/log4cxx.git) repo as the main repo and not the subversion one? http://git.apache.org/ Can we push/commit to this git repository directly? I would rather manage stable (release/intermediary release) with "tags". In this way, you know you have a s

Re: Question re: pom.xml comment block in r1414037

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 Aut

Re: Question re: pom.xml comment block in r1414037

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=6ebb930b694e97e5cf85a72495

How gets the website published?

Hello Christian, could you point me to some docs where I can read how the publishing of the website itself works, without any code releases etc.? I thought it gets build automatically from repository trunk but from digging around maven project sites docs and such stuff I have the feeling it needs

Re: SVN Access granted

>> Is there a commit notification mailing list for our repo? > > Yes there should be one - actually it should be the dev list. Just on a hunch, I tried log4cxx-cvs-subscr...@apache.org but it bounced. I'd prefer having a separate commit notification list as it keeps the traffic lower on log4cxx-d

Anything of value in branches/mcatan/

Hi Michael, A group of folks are re-incubating log4cxx. We're trying to get some pre-incubation releases prepped reflecting the state of work from before we arrived. I noticed there's a http://svn.apache.org/repos/asf/incubator/log4cxx/branches/mcatan/ present in SVN. Is there anything that

Re: Create new branches and revert trunk

>>> I would like to create the branches 0.11.0, 0.11.1 and 0.12.0 base on >>> the current history and would like to revert trunk back to the last >>> official release 0.10.0. The only changes I would keep in trunk would >>> be those from Christian regarding the website etc., but no changes to >>> t

Re: Create new branches and revert trunk

Guten Tag Joseph Southwell, am Freitag, 3. Januar 2014 um 15:49 schrieben Sie: > Perhaps I am behind the times, but that doesn't match my > expectation when I go check out a source repository for a project. > If I want to try the bleeding edge of development code I always go > checkout trunk. Havi

Re: please grant karma

Hi Christian, Thank you for pointing that out to me. I created the user AlexZbarceaon the moinmoin: https://wiki.apache.org/logging-log4cxx Thanks, Alex On Fri, Jan 3, 2014 at 5:30 AM, Christian Grobmeier wrote: > Hi, > > just gave you per

Re: Create new branches and revert trunk

Perhaps I am behind the times, but that doesn't match my expectation when I go check out a source repository for a project. If I want to try the bleeding edge of development code I always go checkout trunk. Having that not be the bleeding edge seems like another thing we would have to document a

Re: Question re: pom.xml comment block in r1414037

> 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 rec

Create new branches and revert trunk

Hello, as we now have commit access to log4cxx, I would like to create a new directory structure to get new patches etc. applied and move towards our first incubation release which will be entirely based on the "old" codebase with all the patches since 0.10.0 which seemed to never ever make it int

Re: Question re: pom.xml comment block in r1414037

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 a

Re: Question re: pom.xml comment block in r1414037

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. use

Re: Question re: pom.xml comment block in r1414037

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 r

[Logging-log4cxx Wiki] Update of "ContributorsGroup" by ChristianGrobmeier

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Logging-log4cxx Wiki" for change notification. The "ContributorsGroup" page has been changed by ChristianGrobmeier: https://wiki.apache.org/logging-log4cxx/ContributorsGroup?action=diff&rev1=2&rev2=3 Comment: added alexz

Re: please grant karma

Hi, just gave you permission to both. The wiki by the way is this one: https://wiki.apache.org/logging-log4cxx Are we on the same page here? Cheers Christian On 3 Jan 2014, at 1:10, Alexandru Zbarcea wrote: > Hi, > > I successfully pushed the first commit to log4cxx in the svn repo. > > I also

Re: SVN Access granted

On 3 Jan 2014, at 0:01, Rhys Ulerich wrote: >> History is still keeping an eye on the list :-) > > In that case, we should keep The Old Guard (TM) happy in case we have > to ask them questions. :P > I added that crew to pom.xml as emeritus roles. Be unfair to inherit > a decade of code without s