Pebble 1.6.1 available
Pebble 1.6.1 is available to download from SourceForge (upgrade notes here) and provides the following enhancements over 1.6:
- PEB-179 : Support for RSS 2.0 enclosures
- PEB-180 : Friendly javablogs referers
- PEB-184 : HTML looks a mess in trackbacks
- PEB-195 : Improve documentation how to set multiple users/contributors for Jetty
- Added permalink provider plugin API.
- Integrated existing documentation into Pebble weblog.
Enjoy!
Re: Pebble 1.6.1 available
Re: Pebble 1.6.1 available
I've been running Pebble since 1.3 and I just upgraded to 1.6 recently and I'm seeing a lot of exceptions being thrown which eventually wedges the Tomcat 5 instance. So to troubleshoot I'd like to attach the source to the instance and debug, but I don't know how to get the correct source attached to my Pebble instance. How do I get the correct source?
Last but not least, it would be nice if you had a "how to upgrade from version x to version y" section in the installation notes.
Re: Pebble 1.6.1 available
You can grab the source for Pebble 1.6 by doing the following:
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pebble login cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/pebble checkout -r v1_6_0 pebbleWhen prompted for a password, just press enter (there is no password).
I have started doing upgrade instructions (see here) but I still need to do a 1.5 to 1.6 guide and of course maintain it going forward. Hopefully theme upgrades won't be so hard in the future now that things are becoming more established!
Re: Pebble 1.6.1 available
Re: Pebble 1.6.1 available
All the 'podcasting' client software I've look at so far (I settled on Nimiq) basically gets the enclosures but completely ignores the text description. Which is a pity because then people automatically downloading stuff just get the content in the ID3 tag of the mp3. I think at least the clients should download the content text and put it in a .txt file next to the mp3.
Aside from that I am thinking how to best integrate pebble ant tasks and enclosures into a continuous integration and test setup I am doing for a client at the moment. This would be set up so that at the end of each test build, the ant script publishes both the result summary and the artifacts that were used to produced the summary onto an internal pebble blog. A great way to build releases too I think!
Simon is a hands-on software architect and has a BSc (Hons) in Computer Science from the University of Reading. Over the past 12 years, he’s been involved in projects ranging from rich desktop clients and web applications through to highly scalable distributed systems and service-oriented architectures; predominantly within the finance industry. He's also undertaken consulting and training roles with a broader focus on people, process and technology.

