Re: PEAR package name

OK about the name change On Thu, Oct 29, 2009 at 1:24 PM, Christian Hammers wrote: > Hello > > The new pear package name "apachelog4php" looks a bit ugly, what about > Apache_log4php? Usually a package should probably be named exactly > like the contained class i.e. ju

PEAR package name

Hello The new pear package name "apachelog4php" looks a bit ugly, what about Apache_log4php? Usually a package should probably be named exactly like the contained class i.e. just log4php but if we want to have the prefix it should at least be more readable. And should we somewhen aft

Re: pear package

Hi Am Tue, 27 Oct 2009 08:16:34 +0100 schrieb Christian Grobmeier : > Hi Christian, > since it was already there i did some tweak to the existing code. > Please look at it. It now creates a package.xml and includes it to the > correct position in the assembly. Only pear package

Re: pear package

Hi Christian, since it was already there i did some tweak to the existing code. Please look at it. It now creates a package.xml and includes it to the correct position in the assembly. Only pear package fails for me because of some strange error with role mappings... Would be great if you could

pear package

Hi I really tried but I can't get a working PEAR package using the assembly descriptors. Therefore I reverted back to the original ant task inside the pom.xml and deleted the src/assembly/ant-package.xml. (the changes are not yet committed as they are mixed with the ones from my last mail)

Re: Release 2.0 and PEAR package?

been fixed. Yes, it is - i closed it > Can we release afterwards? :) For me yes > Apropos, as our users have to install log4php somehow I'm wondering if > we can already build PEAR packages (ant pear-package currently fails) > and if there is something like pear.apache.or

Re: PEAR package?

Hi The "ant pear-package" still works, it was just pear on my Debian unstable system hat has some problems. Only $state in package-config.php would have to be changed to 'stable'. bye, -christian- Am Sun, 11 Oct 2009 02:19:54 +0200 schrieb Christian Hammers : > Hello

Release 2.0 and PEAR package?

was raised yesterday. Can we release afterwards? :) Apropos, as our users have to install log4php somehow I'm wondering if we can already build PEAR packages (ant pear-package currently fails) and if there is something like pear.apache.org or if we may upload the package to another pear r

Re: PEAR package available

On May 19, 2009, at 3:14 AM, Knut Urdalen wrote: Note I had a problem with the "foreach" taskdef in build.xml while developing this. If you just want to run the "pear-package" target you can just comment out line 25 in build.xml. I see that this is some Maven depen

[jira] Resolved: (LOG4PHP-44) PEAR package

[ https://issues.apache.org/jira/browse/LOG4PHP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Urdalen resolved LOG4PHP-44. - Resolution: Fixed > PEAR package > > > Key

PEAR package available

Hi, You should now be able to build and install a valid PEAR package in trunk. This should be a good start. *Build* $ ant pear-package *Install* $ sudo pear install target/pear/log4php-2.0.0.tgz *Uninstall* $ sudo pear uninstall log4php *About the setup* - The packaging is done with

[jira] Created: (LOG4PHP-44) PEAR package

PEAR package Key: LOG4PHP-44 URL: https://issues.apache.org/jira/browse/LOG4PHP-44 Project: Log4php Issue Type: Improvement Components: Code Affects Versions: 2.0 Reporter: Knut Urdalen

Re: Continuous Integration (was Re: PEAR package)

Curt Arnold wrote: mvn test (Mac OS/X) currently fails with the current message: test: [exec] [exec] Warning: require_once(PHPUnit/Util/Filter.php): failed to open stream: Not a directory in /usr/bin/phpunit on line 40 You need a recent version of PHPUnit installed [1]. Knut [1] ht

Continuous Integration (was Re: PEAR package)

On May 6, 2009, at 3:09 AM, Johannes Frandsen wrote: Had a quick glaze at buildbot: It is of course a pretty compelling reason to choose buildbot over cruisecontrol based on the notion that buildbot is a part ASF and is provided as a service for all projects but.. * I dont see anyw

Re: PEAR package

Johannes Frandsen wrote: Do we have a buildserver (cruisecontrol/phpundercontrol) or otherwise maybe I could start by looking in to this project. I haven't looked into setting up a CI tool for log4php yet. But Gavin mentioned about Buildbot (http://ci.apache.org/buildbot.html) on this list

RE: PEAR package

> -Original Message- > From: Knut Urdalen [mailto:[email protected]] > Sent: Wednesday, 6 May 2009 5:05 PM > To: Log4PHP Dev > Subject: Re: PEAR package > > Johannes Frandsen wrote: > > Do we have a buildserver (cruisecontrol/phpundercontrol) or otherwise > >

Re: PEAR package

Johannes Frandsen wrote: Do we have a buildserver (cruisecontrol/phpundercontrol) or otherwise maybe I could start by looking in to this project. I haven't looked into setting up a CI tool for log4php yet. But Gavin mentioned about Buildbot (http://ci.apache.org/buildbot.html) on this list ye

Re: PEAR package

Do we have a buildserver (cruisecontrol/phpundercontrol) or otherwise maybe I could start by looking in to this project. When we have build server we should make it package the product(log4php) for pear automatically and maybe deploy it to a pear repository as a aplha/beta/something. We s

PEAR package

I think we should allow installation of log4php through the PEAR installer. A typical installation could be: $ sudo pear channel-discover pear.apache.org $ sudo pear install apache/log4php While upgrading to latest stable release would be: $ sudo pear upgrade apache/log4php Utilizing installa