Buckminster – LogSaw Project https://logsaw.sourceforge.io LogSaw - a high-performance log viewer based on Eclipse Sat, 12 Nov 2011 18:24:34 +0000 en-US hourly 1 https://wordpress.org/?v=6.4.3 Build infrastructure changes https://logsaw.sourceforge.io/?p=277 Sat, 22 Oct 2011 15:53:11 +0000 http://logsaw.sourceforge.net/?p=277 Continue reading "Build infrastructure changes"]]> First of all, sorry for the slow updates! I’ve been quite busy lately, and LogSaw already does pretty much all I need, so the pressure for me to make changes has been quite low. Though, it’s still all alive and development should continue soon 🙂

I have been playing around with Buckminster some more recently, and I ended up making the whole development process alot easier (did I already mention, that I really like Bucky?). So, if you ever wanted to play around with the LogSaw source yourself, but were unsure on how to get started: The new Building LogSaw tutorial should help you to get started.

]]> RCP Product configuration best practice with Buckminster https://logsaw.sourceforge.io/?p=208 https://logsaw.sourceforge.io/?p=208#comments Sat, 27 Nov 2010 22:07:24 +0000 http://logsaw.sourceforge.net/?p=208 Continue reading "RCP Product configuration best practice with Buckminster"]]> P2 update should work now, after I have changed the product configuration to follow a standard layout that is recommended by the Buckminster folks.
RCP Product configuration best practice
The configuration is depicted in the diagram shown above. For building, we first import site.feature. This feature in turn includes the product.feature and buckminster.cspex that will contribute the create.product and create.product.zip Buckminster actions.

Next, the product feature includes all the components that make up the actual product. Most notably, it also contains the product definition itself. This product definition is based solely on the product feature and has no version defined. Because of this, the product version will be copied from the product feature which makes the whole versioning more simple and easier to grasp.

Finally, using Buckminsters built-in qualifier replacement, the qualifier part of the product feature and plugins will be replaced using the SVN revision number. This will ensure that updates are found and only those parts are updated that have changed.

That’s about it, I hope this info will help out someone or another 🙂

]]> https://logsaw.sourceforge.io/?feed=rss2&p=208 1