Posts Tagged ‘Apache’

Welcome Zeta Components!

Wednesday, June 2nd, 2010

Before a while, there was a very promising Proposal called Zeta Components at the Apache Incubator list. It described a set of PHP components similar which eases the life of us all. It has already progressed very good before developers decided to switch to Apache. In the past days this library has been developed under the name eZ Components and was wellknown to the community.

In my opinion this new project will be very important to the ASF. Apache only hosts two other PHP projects, Log4PHP and Shindig. Since PHP is becoming more and more popular for big business (think on Facebook) I think its necessary to attract more developers and bring them into the Apache community. Many PHP projects out there use the GPL license, and that is sometimes very difficult to combine with commerical work. Good that we now have a component framework under ASL! Together with Log4PHP it’s a good start for much proprietary work.

More in future, I think that even the PIWI Framework will benefit of this change. I already had some trouble with dependent GPL code in it and hopefully Zeta can address most of my wishes. PIWI built upon Log4PHP and Zeta would be charming. But as already said, this will need a while.

At the moment, Zeta Components do already have a mailinglists and status page on the incubator. Jira will follow and after finally the CLAs of the initial developers have been processed, work can begin. However, if you are interest in helping this project subscribe to the user and to the dev list mentioned in the status page.

Lucky me I have been elected into the Apache Incubator PMC and can now serve as a mentor to this project. It’s not only honour to me, it’s also a good chance to work with obviously very nice people and excellent technicians. Also it makes it easy to me to step into this project and learn all I need.

So, welcome Zeta Components!! I am glad you arrived at the Apache Software Foundation!

Apache Log4PHP graduated!

Thursday, March 11th, 2010

Good news! The Apache Incubator Log4PHP project graduated as subproject to the Apache Logging project. This is really a big step forward! The next days I will try to push the real work behind a graduation forward, moving webpages and svn and such. After that move we’ll continue with a new small release. Cheers all!

Log4PHP tries to graduate to Apache Logging

Tuesday, March 2nd, 2010

The past year has been very well for Log4PHP. As you might have noticed, the Log4PHP 2.0.0 release is out. There has been some good feedback so far. Some users even contributed smaller bugfixes or the trace level which wasn’t in the API before. Besides that, there is a good activity on the mailinglist and there are at least 3 active committers. In other terms: time to graduate an bring out Log4PHP from the temporary incubator project :-)

Now Log4PHP needs to succeed 3 votes. One for the Log4PHP team to vote for graduating; one for Apache Logging to accept the podling as a subproject. And finally – after the first two have succeeded – a vote on the incubator list to release the podling to its final destination.

The first two votes are already running and it looks very good so far. Votes need to be open another day then the next step can be done. For those who are interested – there is a detailed document about graduation available.

Let’s see how it works out – I think everything could be in place in quite less time, maybe the next two or three weeks.

Apache Log4PHP 2.0.0 released

Monday, December 14th, 2009

After long work, I sent out the announcement for the first Log4PHP release this morning. Let’s see how this one works out – first reports from DBpedia users were promising. :-)

It’s an exciting time for all involved, and is the result of a culmination of many like-minded individuals. Everyone’s worked hard and as the initial test community seem to have responded positively and in such detail they could test anything from Word to Think Bingo (http://www.thinkbingo.com/) with their eyes closed. The people behind the development had a few words on the announcement of the first Log4PHP.

Here is the original statement:

The Log4PHP community is pleased to introduce the Apache Log4PHP 2.0.0 (Incubating) release [1]. It’s the first Log4PHP release since 2004 and tons of changes have been done. Finally Log4PHP has become a well tested framework made for PHP 5. Many thanks to all the contributors who made this release possible. Please download [2] Log4PHP and enjoy :-)

The Log4PHP team

[1] http://incubator.apache.org/log4php/changes-report.html
[2] http://incubator.apache.org/log4php/download.html

Book review: Apache Geronimo Quick Reference

Wednesday, December 9th, 2009

Apache Geronimo BookI recently got a copy of Apache Geronimo 2.1: Quick Reference. This book should help me with my first steps with this container. Here is a little review for this brand new release of Packt publishing.

My first impression was: wow, is that really a quick reference? The book has a good format and comes with roundabout 370 pages. I hoped for a short book in these times I don’t have too much time for huge novels in the kind of “Gone with the wind”. However, I jumped through the content and figured out that this is actually a quick reference  - very good for the impatient developers like me!

In fact, this book covers all relevant topics I can imagine: it starts with an introduction and a description of Geronimos architecture, which gives an brief (sometimes a bit short) overview of how Geronimo works with its plugins and its deployment strategy. I would have loved to read a bit more about the “hot deployment” feature of Geronimo. In JBoss world, this has brought me some headache. In this book it’s only covered with roundabout one page, just saying that it exists, were you need to place your files and how you can monitor that activity. Even later it’s not mentioned in special. Well, but that’s ok for a Quick Reference.

After this, one gets in touch with the most important knowledge of JMS, Database connectivity and JPA. Then there is an extraordinary good chapter about Security. Its one of the biggest chapters in this book and one can feel quite well how expierenced these guys are. Topics are handled in some kind of How-To way, like “Creating a new keystore” or “Changing a private key password”. These guys know what they speak about, probably the best chapter in this book.

Then it comes to CORBA, which I found also interesting, but to short in general. JNDI was reduced to the most important “put your hands there” information. Then it comes to Geronimo Plugins. This one was very interesting too and I wished to read more about it, but well, again, it’s short reference.  You can find much Listings in this chapter, but I cannot say that they helped me too much without digging in the containers documentation.

In the administration chapter, the authors show the different portlets Geronimo provides for monitoring actions. It’s basically a walk through of the different pages of the Geronimo console. I think, this chapter could have been improved much more. For example, the Thread Pools Portlet is described with just one sentence: “…lists the thread pools defined in the server, and lets you monitor the thread pools.”. Ok, I don’t need a book for that information. Some other portlets are described a bit more in detail, but nothing which makes me to a Geronimo Guru.

Later you will have a How-To use the Geronimo Eclipse Plugin. It contains lots of screenshots which helps you to create a project specifically for the Geronimo. More impressive was the Cluster chapter. Clustering is a difficult topic and I would use this section for doing the job. It’s a good mix between explanation and reference.

Last chapter I was eager to see was the one with the Geronimo Internals. At some parts it reads like a smaller version of an API. It should help to develop own GBeans and it does, but not so much that I would have a huge benefit compared to the docs.

Final words: this one is really a reference and not a teaching book. If you would like to buy it, you should have some knowledge about JEE and about Containers in general. This book will not help you to understand the technologies behind. It’s more a collection of How-Tos, and that is what I expected from a Quick Reference. The authors made this point clear on the cover, were they are stating that you need to know about JEE5 concepts. At some points I would have preferred some more information. Sometimes I would have wished that they put not so much unnecessary listings (I don’t need import statements in java listing nor do I need XML-Comments in a 10 line XML file). I think, if you are developing an application, this book is a nice to have. If you are more an administrator and need to develop, package or cluster Geronimo, this book will probably give you some benefits. Especially the security chapter is well done.

However, thanks for this book, I like it, but it’s not one of my all-time faves.

JavaMagazin publishes Compress article online

Wednesday, October 28th, 2009

The JavaMagazin decided to put the little Commons Compress article online. Originally it has been published in the JavaMagazin 08/2009. Enjoy!

Tika uses Commons Compress

Friday, July 31st, 2009

It just came in with a newsletter: Tika 0.4 is using Commons Compress from now on. Thats really great! It’s the first big app I know which is using Commons Compress. Hopefully that motivates me to get back bugfixing Compress in near future :-)

More TIKA changes: http://www.apache.org/dist/lucene/tika/CHANGES-0.4.txt

SVN Properties – Client Config

Sunday, July 5th, 2009

You  know I am working on several open source projects, and lately one of my comrades told me I should stop coding asap and:”please correct your client configs I don’t want to fix the stuff anymore.”. This shout made me think about my bad behaviour and to be honest, I didn’t know why I should do this and how.

After some small googling, I figured out that the most cool feature of the SVN properties is to ensure that if you check out something from repository, you’ll get the line endings you need.

“In other words, if a user on a Windows machine checks out a working copy that contains a file with an svn:eol-style property set to native, that file will contain CRLF EOL markers. A Unix user checking out a working copy which contains the same file will see LF EOL markers in his copy of the file.”

Quote from: http://svnbook.red-bean.com/en/1.1/ch07s02.html#svn-ch-7-sect-2.3.5

So, this is client config. That means YOU have to make sure that you add your files with the correct properties. Let’s assume you want to add a file named test.txt. You would do:

svn add test.txt

After adding you need to perform:

svn propset -R svn:eol-style native test.txt

to set the properties correctly.

Having that beeing said. most people will complain now that this is a difficult task and very error proven. Well it is. But you don’t have to take care if you are sure that only one operating systems (means: one development enviroment)  is set up. This is true for most projects I guess.

If it is NOT the case, you can force your developers to create a default config setup. On windows it just some entries in the registry (please try this, I am not using windows for open source stuff anymore), on Mac OS X and Linux the file ~/.subversion/config must be edited.

In my case, this did do the trick:

[miscellany]
enable-auto-props = yes
[auto-props]
*.java = svn:mime-type=text/plain;svn:eol-style=native
*.css = svn:mime-type=text/plain;svn:eol-style=native

or at least mostly.  SVN told me, after I wanted to change properties to native, that my css files were binary, which this wasn’t the case, of course! I couldn’t change it, until Sebastian Bazley came up with the following:

svn pl -v

showed:

Properties on 'maven.css':
  svn:mime-type
    application/octet-stream

He further told me to do:

svn pd svn:mime-type maven.css

And that was it – SVN is forced to use mime type I want.

Last but not least, here is the link to the apache recommendation or SVN config.

JavaMagazin article about Commons Compress

Friday, July 3rd, 2009

javamagazin82009In the latest edition of the JavaMagazin you’ll find a small introduction into Apache Commons Compress. It’s not explaining everything, just a good start. Having this beeing said, I think I should note that this one has been written by myself :-) – consider this blog entry as shameless self promotion. :-)

However, if you read the article: please enjoy. If there are any further questions about the usage of Commons Compress, consider to add yourself to the mailinglists.

Committing to Log4PHP

Monday, April 27th, 2009

I just was off for a weekend to celebrate the wedding of good friends – and after returning I found myself beeing committer to Log4PHP. Well, OK, I wasn’t surprised since Gavin and I tried for over a month to get access to this repository. Finally we made it. :-)

Log4PHP is an api for logging within PHP applications. As the name suggests, it’s a port from Log4J which is todays standard in Java applications. Log4PHP has had several attempts to get running, but always went dry. It was february 2007 where lads kicked off the project again.

However, since I need this  Log4PHP as a dependency on PIWI I really don’t want to let it go. It has so much benefits to PIWI. And finally I don’t know a better logging tool than Log4J or its port Log4PHP is. Beside that Log4PHP is a great api, I think it will help to get PHP developers more attracted to Apache. This is important since there are so less PHP guys here. Apache Incubator Shindig is the only project I know with a regular contribution for PHP. Well, hopefully we get a community back the next days and hopefully some of those users turn into fullfledget committers too. We’ll see.

It’s some stuff todo. Nothing critical, just some design issues, small errors and some todos. I guess, we can work on a 1.0 once those issues are resolved. We’ll see :-)

Here are some links for further reading:

http://incubator.apache.org/log4php/

https://issues.apache.org/jira/browse/LOG4PHP

http://incubator.apache.org/projects/log4php.html

  • Recent Posts

  • Tags

  • Categories

  • Archives

  • Wave Notifications

    Download Adobe Wave now!

    This application requires Adobe® AIR™ to be installed for
    Mac OS or Windows.




Feeds