A JBoss Project
Red Hat

Posts tagged with 'jbosscentral'

A few days ago we released JBoss Tools 4.2 Beta3 for Eclipse Luna.

In that update was also a change to our update site urls that we recommend for testing our Nightly builds.

In the past if you used http://download.jboss.org/jbosstools/updates/nightly/core/master/ we recommend you start using the following instead:

Note the 'luna' segment in the URL above indicates this site targets Eclipse 4.4 (Luna). Once we begin building on Eclipse 4.5 (Mars), there will be a new URL with a 'mars' segment.

Why the change ?

To understand why we are changing it its good to try understand how our builds for JBoss Tools is setup to have commits in builds be picked up by Jenkins which then publishes the result to our nightly build update sites.

The following picture is a simplification of the process and how the bits moves through the various sites and gets community tested.

nightly development stable

We have ~40 repositories with more or less independent plugin sets in our Github jbosstools organization. When these change we build an update site for each of them and when one is built the content gets aggregated into an "uber" jbosstools update site.

In the beginning this was not a big problem but over the years with more traffic and more frequent builds users risk having update errors because during their update the build from which they were updating could be overwritten with a newer one.

To remedy this we now offer a composite of the latest nightly builds instead. This means that parsing the site’s metadata will be slightly slower but after that the download speed will be the same, and you should now rarely encounter the above issue.

Another advantage is that with this site you can now revert to an earlier nightly build, in case that works better.

Thus, in short - if you are willing to test our JBoss Tools nightly builds - please use this as your update site:

Talking about nightly builds…​

If you are trying out latest nightly builds why not signup as part of JBoss Tools CAT member and help by giving us feedback to know if we are going in the right direction ?

To do this start here.

Have fun!

Max Rydahl Andersen
@maxandersen

Happy to announce JBoss Tools 4.2 Beta3 and Red Hat JBoss Developer Studio 8 Beta3 for Eclipse Luna is now available.

JBoss Developer Studio 8 Splashscreen

Installation

JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it and install it like this:

java -jar jboss-devstudio-{version}-installer-{standalone|eap}.jar

JBoss Tools or JBoss Developer Studio Bring-Your-Own-Eclipse (BYOE) requires a bit more:

This release requires at least Eclipse 4.4 (Luna) but we recommend using the Eclipse 4.4 JEE Bundle since then you get most of the dependencies preinstalled.

Once you have installed Eclipse, you either find us on Eclipse Marketplace under "JBoss Tools (Luna)" or "JBoss Developer Studio (Luna)".

For JBoss Tools you can also use our update site directly if you are up for it.

http://download.jboss.org/jbosstools/updates/development/luna/

Note: Integration Stack tooling will become available from JBoss Central at a later date.

What is new ?

This release is mainly a bunch of bug fixes but also a few new features and a very important regression fix.

Better Plugin Management for Apache Cordova

Our Hybrid Mobile Tools now supports automatically downloading the plugins listed in your config.xml giving you two benefits:

  1. Allow you to exclude the physical plugin binaries from your source control

  2. On import the right plugin will be fetched dynamically, great for sharing examples and code.

Also don’t forget we have proposed and contributed Hybrid Mobile Tools at Eclipse under Eclipse Thym.

CordovaSim is now less meme-compatible

CordovaSim using Ripple had a "easter-egg" in the sense when you used a Cordova plugin that the Ripple engine did not understand would show a dialog titled "I Haz Cheeseburger?!?!". Great for those with a great love for internet memes but it was not very informative.

Now we provide a less meme heavy dialog letting the user know what plugin that is not supported and allow you to not have to see the message again.

Plug-in not supported dialog

Btw. if you use a popular and/or important plugin that is not supported open a jira or PR against CordovaSim.

Ionic framework in palette

We’ve added support for Ionic framework. Ionic is a AngularJS based framework that provides nice mobile components that works especially well with Cordova based application.

Ionic palette

Maven Central archetype catalog

One of the improvements in m2e 1.5 for Luna was that it no longer by default download the Nexus indexes for all repositories by default. It was simply too slow.

Thus that had to go but by removingt this the list of archetypes for the 'New Maven Project' was heavily reduced.

In Beta3 we’ve added the Maven Central Archetype catalog meaning you get access to ~9600 archetypes in a few seconds vs several minutes in pre m2e 1.5 days.

Maven Central Archetype Catalog

Review commit changes when pushing to OpenShift

When pushing changes to OpenShift and you have uncommitted changes we now show a variation of the standard git commit dialog allowing you to be selective about what files you want to get committed/added before your push.

Review changes before committing to OpenShift

JMX Navigator grouping of connections

With all the great additions to the JMX tooling in last beta we realized the JMX Navigator view could benefit from having its connections grouped by type.

Allows you to more easily find what you are looking for and when auto-discovered connections come and go the view stays stable.

JMX Navigator group by connection type

Fixed incremental deployment regression

…​and finally we fixed a rather severe regression in our server tools. The server adapter were triggering full redeployments if your project had certain type or module or jar dependencies.

Making your development workflow really slow compared to the more or less instant feedback you should get when just updating dynamic content like html or jsf.

Sorry for having that broken but now it is fixed - thus if you felt the server publishing was slow then please try it now! It should be back to its fast self again.

…​and more

There are more improvements covered in the more detailed: What’s New.

What is Next

This Beta is the last planned Beta for JBoss Tools 4.2 and Developer Studio 8. The next release is set to be the candidate release thus please do try this release out and give feedback to make sure you’ll have a good experience with JBoss Tools on Eclipse Luna!

Let us know what you think in the comments below!

Hope you enjoy it and remember…​

Have fun!

Max Rydahl Andersen
@maxandersen

In our recent milestone releases of JBoss Tools 4.2 we’ve started gathering additional data from those who are have agreed sending back anonymous usage data to us (Thank you!).

Reminder: As always, this is my personal interpretation of the data and again it is early days for the data collection. These numbers are just for the last month of beta testers thus do take these absolute numbers with a grain of salt!

In any case I find the numbers interesting and thought I would share since there are some lessons to be learned.

JBoss Server Usage

One of the data points are which JBoss servers users create.

Mind you we don’t collect the exact version of the server installed, just which server adapter users are using - i.e. EAP 6.1 also covers EAP 6.2 and 6.3, WildFly 8 covers 8.0 and 8.1 etc.

server creation stats

The numbers above shows the last two weeks of server creation by our beta users. Not surprisingly majority of users are using the community version of the latest JBoss servers (AS 7.1 and WildFly 8), and it’s great to see the third most used server is the free for development/enterprise supported EAP 6.1/6.2/6.3.

Oldie but goodie

What I find funny is that there are still users using the latest/greatest development tools, but who runs JBoss AS 3.2 - this was last released back in 2006! Talk about dedication :)

Importance of Multiple runtime support

What the list shows to me is the importance of development tools need to support multiple versions because even though most are using latest/greatest runtime there are still a great bunch of users that will be using older versions of runtimes. Many developers tend to forget or blissfully ignore this.

I’m convinced as users move to our release that gathers these data we will start see even higher numbers of "older" runtime usage.

Deploy Only Server

What is a bit disconcerting is how few seem to know about our Deploy only server (in this list noted as systemCopyServer ). This server allows you to use Eclipse’s support for incremental deployments to any directory locally or remotely available. Really useful for deploying to a non-JBoss server, a remote PHP or just a plain html app.

You should try it out!

File ▸ New ▸ Server ▸ Basic ▸ Deploy Only

Combine this with our LiveReload support and you get a great and fast workflow!

Uptake of Eclipse versions

Another data item we have insight to is the uptake of Eclipse versions.

Uptake of Eclipse versions

The graph above is our recorded startups of Eclipse Java EE installs since January pr. week. Be aware the versions listed are the EPP versions, not Eclipse release train versions - I’ll do the mapping for you below.

Two things to note: the "Drop" at the end is just the effect of the numbers ending middle of the month, the "Dip" in mid April I’m not sure what is but we see it across all our Google analytics thus I expect it was an Google Analytics anomoly. The numbers have since stabilized, that said…​lets interpret!

This graph shows how Eclipse Kepler SR1 release (2.0.1) usage is dropping as users upgrade to Kepler SR2 release (2.0.2) - this are most likely the effect of users using Eclipse built-in update mechanism to upgrade.

What also can be seen is that the latest stable release (4.4.0) uptake is gaining faster than total Eclipse version usage (the faint lines are even older eclipse versions). Meaning total usage of JBoss Tools is up/stable. Eclipse isn’t dead yet :)

I wish Google Analytics had a way to show this graph cumulative instead of per line…​anyone up for a data extraction and visualization project ? I’ll give you access to the data to play with.

Uptake of Eclipse Luna

Finally, my personal main interest was to see what the uptake of Eclipse Luna is.

You can see what effect a GA release of Eclipse has. The red line is Eclipse Luna going from a couple of hundreds starts to now 7.000 starts pr. week since its release - but do notice that there is no corresponding drop (yet) in Kepler. Looks like most are installing Luna next to their Kepler installs (my theory at least ;)

This mimicks previous years uptake patterns and once everyone gets back from vacation and Luna SR1 release comes out it should be close to the level of Eclipse Kepler installs. Good to see users continue to picking up latest greatest features and bugfixes!

I’ll go look at the numbers again in a few months to see if the trend continues.

If there is some additonal data you are interested or questions about the above let me know in comments and I’ll try include/answer it!

Have fun!

Max Rydahl Andersen
@maxandersen

In this article, I’m happy to introduce you the OAuth authorization via Phonegap’s inAppBrowser plugin with CordovaSim.

I was inspired to write this blog after reading a great article about Google API OAuth with PhoneGap’s InAppBrowser by Michael Dellanoce. I also want to spill the beans about new CordovaSim’s features like: JavaFx web engine, hybrid app debugging and eclipse console logging, that will be available in Beta3 (but you can try them now from the nightly build 4.2.x update site).

Overview

OAuth is an open standard for authorization. It specifies a process for resource owners to authorize third-party access to their server resources without sharing their credentials. Designed specifically to work with Hypertext Transfer Protocol (HTTP), OAuth essentially allows access tokens to be issued to third-party clients by an authorization server, with the approval of the resource owner, or end-user. PhoneGap Developers use inAppBrowser’s API to show the OAuth consent page.

Demo

CordovaSim supports inAppBrowser plugin and handles OAuth authorization. Here is a short video with OAuth demo and brand-new CordovaSim’s features (source code is also taken from the Michael Dellanoce’s article):

How to give it a go?

The sample should work with JBoss Tools 4.2.0 Beta3 release and later versions.

  • Clone the demo project

  • File → Import → Import Cordova Project

  • Right-click on the project → Properties → Hybrid Mobile Engine → Download → 3.4.0 (select as default engine)

  • Create a Google Developers Console project

  • Copy and paste Client ID and Client secret to index.js (lines 80-81) of the hybrid project

  • Right-click on the project → Run As.. → Run with CordovaSim

A few things to notice here : first, the Hybrid Mobile Tools imports the project into Eclipse and configures the proper plugins without there being any Eclipse specfic setup in the project. This works because the project is following the conventions from Cordova CLI generated projects and the import wizard understands this.

Secondly, when using Java 8, you can connect the Chrome debugger to the CordovaSimulator (Right click → Debug on browser) allowing you to step through the code, introspect variables and so forth.

Conclusion

We are trying our best to make CordovaSim as good as possible. User feedback is what we are seeking for now. We are looking forward to hearing your comments / remarks!
Have fun!

Ilya Buziuk
@ilyabuziuk

I believe very much in our tools are only as good as our users think they are.

Today I’m calling out to you reading this blog to help us make the tools better.

As Thanks you get better tools that works better with your usecases!

Today we are introducing JBoss Tools Community Acceptance Testing (CAT) program to make sure we hear from you to know what is working and what is not working.

JBoss Tools CAT Logo

What is it ?

JBoss Tools CAT is a program where you signup and give feedback on new features and we will help you in any issues you have. We’ll also be doing some surveys where JBoss Tools CAT members get to tell us if you find JBoss Tools are ready to be released or not.

The program will run for every major release, this time we are focusing on JBoss Tools 4.2 and Developer Studio 8.0 - current release for that is 4.2.0.Beta2

You can see the details about the program at the CAT page.

How do I participate ?

If you are interested in participating please go and Register!

Is this not similar to NetBeans CAT ?

Yes, the Netbeans CAT program is what inspired us to do this. We think it will work equally well for us too.

What is in it for you ?

Besides you being able to influence the readyness of JBoss Tools for your usecases we will also at the release of the final JBoss Tools put your name as part of the release and dependent on the number of participants give out some extra prizes.

You can see more at the JBoss Tools CAT web page.

Again, if you are interested in helping making the tools work better for you, please Register!

Lets Have fun!

Max Rydahl Andersen
@maxandersen

It is time to get some more Eclipse Love out in the world - we start by shipping JBoss Tools 4.2 Beta2 and Red Hat JBoss Developer Studio 8 Beta2 for Eclipse Luna.

JBoss Developer Studio 8 Splashscreen

Nice, ain’t it?

Installation

JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it and install it like this:

java -jar jboss-devstudio-{version}-installer-{standalone|eap}.jar

JBoss Tools or JBoss Developer Studio Bring-Your-Own-Eclipse (BYOE) requires a bit more:

This release requires at least Eclipse 4.4 (Luna) M7 but we recommend using the Eclipse 4.4 JEE Bundle since then you get most of the dependencies preinstalled.

Once you have installed Eclipse, you either find us on Eclipse Marketplace under "JBoss Tools (Luna)" or "JBoss Developer Studio (Luna)".

For JBoss Tools you can also use our update site directly if you are up for it.

http://download.jboss.org/jbosstools/updates/development/luna/

Note: Integration Stack tooling will become available from JBoss Central at a later date.

What is new ?

This Beta 2 contains quite some new additions that I believe you will like!

Java 8

To start with, this is now tested and developed against Eclipse Luna M7 and newer which means it comes with Java 8 tooling support out-of-the-box.

Early Access in JBoss Central

To allow users of JBoss Developer Studio to try out plugins which have not yet reached supported level more easily we’ve added the notion of Early Access to JBoss Central.

JBoss Central Early Access

For now we’ve moved Eclipse VJET into this area and made Arquillian Tools and AngularJS available for Developer Studio users.

The "Early Access" features are from an isolated update site that only gets added if you press "Show Early Access" and when you unselect "Early Access" we will remove/disable those update sites thus you will not receive anymore updates of those features.

Try it out!

VPE is dead, long live VPE!

VPE has been refactored to use the new HTML Preview feature.

This means we will use your system native browser to preview HTML5 based pages (XHTML/JSF will still use the old XULRunner based browser if possible).

Visual Page Editor

This new preview has much better Javascript support and just looks better.

If you do not like the split editor view you can also open it as a separate view which will show the HTML representation of editors that uses the WTP based XML DOM model (i.e. our html editor and wtp xml editors).

The preview supports navigating between source and the visual elements allowing you to easily find the right place in the code.

Better JavaScript

To improve Eclipse JSDT default JavaScript we’ve done many fixes to it that are available in stock Eclipse, but for JBoss Tools we’ve started to try use Tern behind the scenes via Angello Zerr’s angularjs-eclipse and tern-java projects.

In JBoss Tools Tern is now automatically enabled on Javascript based projects intended to give you much stronger and better content assist in addition to what Eclipse JSDT provides.

JavaScript ECMA 5

We are trying to make it that there is no user setup needed for most common javascript functionallity to work.

For example if you create a Hybrid Mobile Tooling project we will enable the support for Apache Cordova Javascript out of the box.

CordvaJS Content assist

AngularJS support

As an experiemnt, we’ve made AngularJS available from JBoss Central under "Early Access" to give a try if you are an Angular user.

Angular JS Support

We are really interested in hearing if these improvements to JavaScript and Angular support work for you!

OpenShift Quickstarts

The OpenShift wizard now supports OpenShift’s notion of quickstarts or instant apps.

OpenShift Quickstarts

This means it is now possible to just use OpenShift Wizard in Eclipse to use one of the many custom defined quickstarts without having to use the browser.

Examples of interesting JBoss server related quickstarts are WildFly 8.1, AeroGear Push server and CapeDwarf.

OpenShift Snapshots

On request OpenShift now supports saving and restoring your OpenShift instances via Snapshots.

Save/Restore snapshots

Local Java Process Monitoring via JMX Navigator on steroids!

The view before called 'MBeans Explorer' is now called 'JMX Navigator' and it now can do much more than before.

First off, it will automatically list locally detected Java Virtual Machines which you can connect to and browse their internal state via JMX MBeans.

Locally detected processes

Once you have this view open you can browse the MBeans, but with a little bit of magic you can also get various performance metrics displayed.

Timeline of a java process

You can even get profiling info such as hotspots, memory usage etc.:

hotspots monitor

Basically, JBoss Tools now comes with a built-in Java profiler out of the box.

This functionallity originally comes from Fuse IDE which adopted jvmmonitor which we have now moved into JBoss Tools core to unify our access to JMX and Java processes.

JBoss Modules Classpath Container

Until now JBoss Tools core have used basic file patterns to find appropriate jars for your classpath and for introspecting the JBoss servers. With JBoss Modules where there can be multiple versions and several layers of patching this kind of simple file pattern searching is not sufficient.

Thus now our WildFly/JBoss EAP based servers understand the notion of JBoss Modules and will locate the proper module.

JBIDE 9479

It even will detect if your manifest.mf has Dependencies and add them to the list of jboss modules to the classpath Eclipse will use for compiling.

…​and more

There are more improvements in the areas of JAX-RS, Maven, Mobile palette, Forge. See details here: What’s New.

Let us know what you think in the comments below!

Hope you enjoy it and remember…​

Have fun!

Max Rydahl Andersen
@maxandersen

Maintenance updates of your favorite integration tools!

jbosstools jbdevstudio blog header

The Integration Stack for JBoss Tools Developer Studio is a set of plugins for Eclipse that provides tooling for the following frameworks:

  • BPEL Designer - Orchestrating your business processes.

  • BPMN2 Modeler - A graphical modeling tool which allows creation and editing of Business Process Modeling Notation diagrams using graphiti.

  • Drools - A Business Logic integration Platform which provides a unified and integrated platform for Rules, Workflow and Event Processing.

  • JBoss ESB - An enterprise service bus for connecting enterprise applications and services.

  • Fuse Apache Camel Tooling - A graphical tool for integrating software components that works with Apache ServiceMix, Apache ActiveMQ, Apache Camel and the FuseSource distributions.

  • jBPM3 - A flexible Business Process Management (BPM) Suite - JBoss Enterprise SOA Platform 5.3.x compatible version.

  • Modeshape - A distributed, hierarchical, transactional and consistent data store with support for queries, full-text search, events, versioning, references, and flexible and dynamic schemas. It is very fast, highly available, extremely scalable, and it is 100% open source.

  • Savara (JBoss Tools only) - A tool for ensuring artifacts defined at different stages of the software development lifecycle are valid against each other, and remain valid through the evolution of the system.

  • SwitchYard - A lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications.

  • Teiid Designer - A visual tool that enables rapid, model-driven definition, integration, management and testing of data services without programming using the Teiid runtime framework.

All of these components have been verified to work with the same dependencies as JBoss Tools 4.1 and Developer Studio 7, so installation is easy.

Installation

To install the Integration Stack tools, first install JBoss Developer Studio from the all-in-one installer, bundled and configured out of the box with everything you need to get started. Alternatively, if you already have eclipse-jee-kepler installed, you can install JBoss Developer Studio or JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace…​

jbtis b1

Once Developer Studio is installed, restart Eclipse and select the Software/Update tab in the JBoss Central view and look for the JBoss Developer Studio Integration Stack installation section. Select the items you’d like to install:

jbtis b2

If you want to try out Savara you will need to use the JBoss Tools Integration Stack URL instead:

Note: If you installed into your own Eclipse you should bump up the launch resource parameters:

--launcher.XXMaxPermSize 256m --launcher.appendVmargs -vmargs -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms512m -Xmx1024m

What’s Been Updated?

Fix release versions of Fuse Tooling 7.2.1, jBPM/Drools 6.0.3, SwitchYard 1.1.6 and Teiid Designer 8.3.3. Look for specific bug fixes in the Release Notes.

Keep up to date with the JBoss Tools home

Don’t miss the new Features tab for up to date information on your favorite Integration Stack component !

I just got the great news that last night Red Hat JBoss Developer Studio 7 (built on top of JBoss Tools 4.2) was one of the Winners in the CODiE Awards.

We won in the Best Mobile Development Solution category.

Really happy to see that happening!

A big giant thank you and congratulations to the JBoss Tools and Developer Studio team and contributors for making it all possible!

One of the materials submitted was this video outlining the mobile features in particular:

Take a look at that and know since the nomination back in September 2013 we now got JBoss Developer Studio 8 Beta 1 with even more goodies, including Mobile tooling improvements.

Worth mentioning that OpenShift won in the Best Cloud Platform as a Service category too - Congratulations!.

Have fun!

Max Rydahl Andersen
@maxandersen

A few weeks back Eclipse launched their Java 8 Support for Eclipse Kepler.

Its a great page with links to various resources about Java 8 and how to install the various components into Eclipse.

The four components you want to install if you are doing web/java development for Eclipse are the ones covering:

  • Java core (JDT)

  • Java Web Tools (WTP)

  • Maven (m2e)

  • OSGI (PDE)

For now those need to be installed individually.

We wanted to make that even simpler.

Thus today we deployed our Java 8 packaged install and update site which does not require you to do four different installs.

There are two ways to use this. Using JBoss Central or the composite update site.

Using JBoss Central

  • Open JBoss Central

  • Click Software/Update

JBoss Central showing Java 8 Install connector
  • Choose Java 8

  • Click Install

You will then be shown a screen where you can choose to install all or select a subset.

If you have JBoss Tools installed the recommended way is that you install them all since then you get the best Java 8 coverage possible in Eclipse.

Using plain old update site

If you do not want to use JBoss Central you can also use this update site directly:

http://download.jboss.org/jbosstools/updates/stable/kepler/central/java8/

Please note that this site includes plugins for 'm2e' with "Optional" in their name which are only relevant if you are an Eclipse plugin developer. You can skip those - just there for completeness.

Limitations

We know that Java 8 support is not fully working for WildFly 8 server adapter in our Kepler based JBoss Tools version - if you want to use that try out our recent builds of JBoss Tools for Luna where this is being supported.

But otherwise you can now build and run Java 8 projects with JBoss Tools for Eclipse Kepler today.

Have fun!

Max Rydahl Andersen
@maxandersen

The last few days an error have started popping up during validation of all our existing JBoss archetypes and examples.

The error you will see in Eclipse problems view will be:

Referenced file contains errors (http://docs.jboss.org/ironjacamar/schema/datasources_1_0.xsd).
For more information, right click on the message in the Problems View and select "Show Details..."

on various *-ds.xml files.

The cause of this error is that the IronJacamar project moved their xsd’s and rest of their content to http://ironjacamar.org back in June 2013.

I’m sorry for that inconvenience, but do not despair - the solution is here.

Solution

For now we have requested that the content will be restored to make this true but annoying error to go away without you having to do anything.

But until that is fixed you can also fix it locally by using the updated ironjacamar url/namespace in your .xml files:

Change this:

<datasources xmlns="http://www.jboss.org/ironjacamar/schema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.jboss.org/ironjacamar/schema http://docs.jboss.org/ironjacamar/schema/datasources_1_0.xsd">

to

<datasources xmlns="http://www.ironjacamar.org/doc/schema"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://www.ironjacamar.org/doc/schema http://www.ironjacamar.org/doc/schema/datasources_1_0.xsd">

Basically replacing http://www.jboss.org/ironjacamar/schema with http://www.ironjacamar.org/doc/schema. The namespace name changes, but otherwise the content/semantics should stay the same.

Why this validation errors have not shown up before we are still looking into and I’ll let you know when we have that answer.

For now just live with the validation error for a few days or update your xsd files to use the new namespace.

Again, sorry for the inconvenience.

Despite this - do Have fun!

Max Rydahl Andersen
@maxandersen

JBoss Tools 4.12.0.AM1 for Eclipse 2019-06

by Jeff Maury on Jun 12, 2019.

Integration Tooling for Eclipse 2019-03

by Paul Leacu on May 30, 2019.

Quarkus

by Jeff Maury on May 13, 2019.

Looking for older posts ? See the Archived entries.
back to top