LJC JCP Committee Meeting 8th March 2018


  • Martijn Verburg
  • Sean Landsman
  • Sabrina Wons
  • Ilan Pillemer
  • Somay Nakhal
  • Abraham Marin-Perez
  • Ingo Hoffmann

Java EE -> Jakarta EE

Java EE has been donated to the Eclipse Foundation and reside as Eclipse EE4J projects, with the brand name of Jakarta EE.

The Committee discussed the pertinent founding documents:

Of particular interest was the Working Group charter where the new Guest Membership level (aimed at Java User Groups etc.) would give entities like the LJC a view into the Jakarta EE specification and steering groups, but would not give entities like the LJC a vote.

Action Item – Create a Poll

The Committee decided to poll the LJC membership and other important JCP / JSR related communities including (but not limited to):

  • LJC Membership
  • Global Java User Groups
  • London JBoss User Group
  • Java Champions
  • Java EE Guardians
  • EE4J Community

The poll will ask whether they still want the LJC to have a voting presence in the new Jakarta EE.  If so then the LJC can explore options to participate at that level, perhaps coming in as a Solutions Member.

Questions in the Poll

The London Java Community (LJC) and SouJava currently represent the global Java User Group community with regards to Java EE standards, i.e. technical review, legal review and voting on whether standards should progress.

With Java EE moving to the Eclipse Foundation (as Jakarta EE), a new Working Group with specification / steering committees governing the future of this technology has been formed.  The LJC would like to understand if Java User Group members) around Java EE technology is still interested in us representing them at Eclipse. So here are some questions!

  1. Do you directly or indirectly develop with or use Java EE technology?
    (if you use Spring, then this is a Yes).
  2. Are you aware that Java EE has moved to the Eclipse Foundation as Jakarta EE?

Please read the following documents before answering the next questions:

  1. Would you like the LJC to have voting status at Eclipse for Jakarta EE?
    1. Yes
    2. No
    3. I don’t know – it’s too complicated to figure out
    4. I don’t know – I didn’t read the docs I was asked to 🙂

  2. Please leave any further comments

OpenJDK / Java SE

The Committee discussed the pertinent founding documents:

Action Item – Continue Discussing JEP12

A longer discussion on the drawbacks vs benefits of JEP12 is required, including:

  • Impact on independent implementers of Java (e.g Azul, IBM etc).
  • Impact on tooling vendors (e.g App Dynamics, Jetbrains etc).
  • Impact on libraries (e.g ByteBuddy, Spring etc).

Action Item – Test Drive Java 10

Martijn encouraged members to try Java 10 out early and give feedback.  We’ll also encourage the LJC at large to do this.

Action Item – 6 month release cycles and support

The committee discussed the concerns around the 6 month release cycle and the lack of Oracle’s LTS support for OpenJDK.

Other vendors and/or the community could of course support OpenJDK (and variants / versions of it), but that support is likely to be seen as fragmented by the ecosystem.

Adopt OpenJDK Build Farm

Martijn introduced the Adopt OpenJDK Build farm, the new place where the OpenJDK community (including several LJC members) are collaborating on a new build farm for Java to be shared and used by the community at large:


We voted “Yes” for the re-submission of this specification within.  Jigsaw and Java 9 will represent a solid foundation for a new evolution of the Java platform, one that is nimbler, more lightweight and more secure.  Is this work complete?  No, there are still outstanding issues and feature requests to go, especially as the ecosystem learns to use the new modulepath and friends.  But the basis is sound and we think a large minority will take up the new module system once Java 9 goes GA.

The results of the vote on the reconsideration ballot (Public Review) for this JSR are here: https://jcp.org/en/jsr/results?id=6016

We voted no the first time around because we wanted to see final consensus on the last few outstanding issues as well as some bedding in time of recent, far-reaching consensus decisions.

Our official comment

The LJC votes yes and echos IBM’s thanks to Oracle (as the specification leader) and those in the JSR 376 Expert Group who dedicated their time to reworking and clarifying areas of the specification that we were concerned about.

The LJCs concerns (https://londonjavacommunity.wordpress.com/2017/05/09/explanation-of-our-no-vote-on-jsr-376-java-platform-module-system/) over interoperability with the Java ecosystems defacto build tool / module repository (Apache Maven) have been addressed as have the concerns over the ability for independent implementations of the compiler to be built (noticeably ejc).

The disposition of outstanding issues as agreed amongst the Expert Group was handled really well and it was heartening to see the evident collaboration as described in the detailed minutes of the EG’s meetings in the past month.

We see this release of JPMS as the strong foundation for a new Java SE platform architecture, and expect to build upon this with feedback and experience from Java User Group members.

Further Notes

The specific technical details of what was agreed and what was deferred are in the minutes:

Some highlights include:

  • Agreement on version name format(s).
  • Agreement on rules around Automatic Module Naming and a guide on how to best use those (important for the Maven ecosystem).
  • Dealing with multiple versions of the same module was deferred.
  • Agreement on relaxing Strong encapsulation as a default (means fewer apps will break out of the box, but get a warning instead).
  • Tidying up on some keyword usage (allowing the Eclipse compiler to be built).

We think the Spec lead and EG did a great job in coming together to resolve the outstanding concerns and hope that this can be a model for further collaboration over particularly far-reaching / complex part of the Java ecosystem development going forwards.

Martijn (on behalf of the LJC JCP Committee, on behalf of the LJC)


We voted No because we want to see final consensus on the last few outstanding issues as well as some bedding in time of recent, far-reaching consensus decisions.  No we don’t think this should or will delay Java 9 significantly, we expect a re-submission and eventual “Yes” vote to this specification within 30 days, please see the JCP Process Document for how this works.  No, we don’t think JPMS/Jigsaw is fundamentally flawed.  Yes we want extra time and thought going into JPMS by the wider ecosystem (and its authors) as this new module system will impact Java far more than the move to generics in Java 5.

The results of the vote on the Public Review for this JSR are here: https://jcp.org/en/jsr/results?id=5959

Our official comment

We echo SAP’s comments in that we absolutely recognize the tremendous achievements and the great work that has been carried out until now by the EG members as well as (and especially) by the Spec Lead himself.

The LJC is voting “No” on the spec *as it was submitted* at the start of the voting period. During the 14 day voting period, great progress was made by the Spec Lead and the EG to reach consensus on some very difficult issues such as #AutomaticModuleNames. However, there are still on going conversations on some of those issues and there simply has not been enough time spent by the ecosystem to discuss some of the new designs in enough depth or enough time spent implementing and testing prototypes based on the latest spec, e.g. The Eclipse ejc compiler or the latest Automatic Module Naming design in Maven.

If required, we very much look forward to being able to vote ‘YES’ in <= 30 days on a version that has had that little bit of extra time for the EG (and the ecosystem) to discuss / implement / test some of these difficult spec items. Certainly the last 14 days have shown that consensus can be reached even when viewpoints have started in opposing corners, and we think another short time period to really bed in the last sticking points is needed.

Further Notes

We voted “No” based on careful technical analysis of JPMS, the RI (Jigsaw), comments on the mailing list as well as out in other public forums.  We then put the existing specification to the test on a Java 9 hackday along with the Virtual JUG and ~15 JUGs worldwide.  The conclusion was that JPMS still has some outstanding issues to be resolved or issues that (despite having recent resolutions), were still not bedded in the minds and/or prototypes of the larger ecosystem.

For our membership, interoperability with the Maven build ecosystem and the ability to build an alternative compiler implementation (i.e. Eclipse’s ejc compiler) is paramount.  Although consensus is rapidly forming around those two items, our membership felt that they needed some extra time before they felt comfortable with voting “Yes”.

This is what the JCP is for (no, not just politics)

Casual observers and some parts of the tech media will likely come to the conclusion that this is all just about big company politics. Recent public blog posts and open letters will have fuelled that sentiment, but we urge people to read the comments accompanying “No” votes.

Although Oracle are the stewards of Java, the JCP Executive Committee (EC) is meant to act as guide for the Java ecosystem as a whole and we feel strongly that it is working as intended in this case.

What next?

The Spec Lead (Mark Reinhold) has publicly stated that if it needs more time, then it will get more time, so we expect to see a revised spec within the 30 days and expect to vote “Yes” in good conscience and not delay Java 9 (the spec).
Martijn’s Personal View 
There was a lot deep dive technical analysis and tough discussion in the past two weeks with a lot of smart, passionate technologist’s who all love Java.  This cannot be a bad thing :-).  That said, I’m tired and will now have a sleep before Devoxx UK!
Martijn (on behalf of the LJC JCP Committee, on behalf of the LJC)

Attendeed: Martijn Verburg, Sean Landsman, Ingo Hoffmann, Omar Bashir

  • Welcomed Omar as a new member!
  • Discussed JSR 363 – Units and Measures. Omar pointed out that it looked good overall but he had some concerns about the verbosity / boilerplate nature of having to use Factories and Builders in order to get going. He noted that the Java 6 compatibility made sense (IoT, Android and other older platforms). Martijn commented that DI of some sort might help tackle the verbosity, but that the Spec Lead and EG had likely discounted that in order to allow it to be used across a wider set of projects.  Omar will send in final feedback by Sunday the 7th.
  • Discussed the vote for JSR 380 – Bean Validation 2.0.  Unanimous yrs, Ingo noted it was early stages and that we should have a more careful review when there was the beginnings of a RI.
  • Discussed the vote for JSR 367 – JSONB – Group looked at outstanding issues and send a message to the Spec Lead over a concern that JSONPointer support had not been addressed.  Will wait until Sunday evening (7th) before casting final vote.
  • Discussed nominations for JCP awards. Unit of Measure and Jigsaw seemed to be the outstanding JSRs, more research required on the Adopt a JSR award.
  • Martijn will give feedback at the next meeting about the Aug 7th EC phone conference, covering Java EE 8 as Oracle sees it.


Martijn (on behalf of the LJC JCP Committee)

Attendeed: Martijn Verburg, Sean Landsman, Ingo Hoffmann, Abraham Marin-Perez

  • Welcomed Abraham and Ingo as new members!
  • Discussed MicroProfile.io and status of JavaEE 8 – the LJC will officially support MicroProfile and run hackdays against vendor implementations of the profile.  The LJC is waiting until JavaOne in Sept to see what is happening with Java EE 8 but hopes that Oracle will join the collaborative MicroProfile effort.
  • Discussed JSRs under review and agreed to go away and do more research and send feedback to the list:JSR 380 – Bean Validation 2.0 – JSR Review
    Appears on the ballot: 26 July 2016
    URL for proposal:
    https://jcp.org/en/jsr/detail?id=308JSR 362 – Portlet Specification 3.0 – Early Draft Review 2
    Last day of review: 12 September 2016
    URL for EDR 2 materials:

    JSR 367 – Java API for JSON Binding – Public Review
    Appears on the ballot: 26 July 2016
    URL for Public Review materials:

    JSR 363 – Units of Measurement API – Proposed Final Draft
    URL for PFD materials:

  • Discussed an IP and copyright of APIs proposal that was put to the EC.  Decided that further in depth study was required before commenting.
  • Martijn will arrange the next meeting before the Aug 7th EC phone conference


Martijn (on behalf of the LJC JCP Committee)

TLDR: Go to microprofile.io and join the mailing list there and fill out the survey!

Recently the LJC officially put its support behind MicroProfile, a new open source project and collaborration between Java EE vendors and the developer community to provide enterprise developers comfortable with Java EE a way to move into the microservices space.  The LJC will host hackdays as Microprofile gets closer to its first GA release in September 2016.

The recent interview with JAX Enter sums up the current state nicely, so I’ve repeated it here verbatim.

JAXenter: Red Hat, IBM, Tomitribe, Payara and the London Java Community joined forces to create MicroProfile. What are the objectives of this initiative?

Martijn Verburg: The initial goal is to provide developers who are most comfortable with enterprise Java (Java EE if you will) a starting point to work with microservices in a non vendor specific way (which is what they’re used to from the Java EE world).  The aim is then for the developer community to actually drive what they feel they need in microservices runtime/API, so instead of the vendors ‘guessing’ that you might want security, or logging or discovery or whatever. It’ll be up to the MicroProfile community to help define what should go in and what should stay out.

Some open standards will likely fall out of this to give businesses confidence about the longevity and the vendor neutrality, which is something they’ve enjoyed and trusted from the Java EE ecosystem.

JAXenter: What is the London Java Community’s take on the current state of Java EE? How can MicroProfile bring it forward?

Martijn Verburg: Java EE has clearly stalled with the lack of progress on Java EE 8. Although many of us feel that the time for the monolithic Java EE platform standard is possibly over, there’s still enormous value in having standards around key pieces of Java Enterprise technology. Enterprise Java does after all still drive billions of dollars worth of IT business and directly or indirectly drives trillions of dollars in the global economy.

JAXenter: How is the goal of MicroProfile different from Java EE Guardians’? What is the London Java Community’s contribution to this new initiative?

Martijn Verburg: The goal of MicroProfile is to bring collaboration around microservices for enterprise Java developers.  This is very separate to the Guardians group, who are advocating Oracle to put resources back into the Java EE 8 platform.

JAXenter: How can MicroProfile push forward microservice innovation in Enterprise Java?

Martijn Verburg: By asking the community what they want and releasing early and often.  Then standardizing on what the community and the vendors feel are the right APIs that need longevity.

JAXenter: Do you hope to generate a reaction from Oracle?

Martijn Verburg: We hope they join in the initiative!  Oracle has shown that it can lead in open source via OpenJDK and we know that like all vendors, they have an interest in microservices.  Some common ground between all of the vendors and the community will help ensure that enterprise Java is well placed for the challenges going forwards.

JAXenter: How can the community participate in the MicroProfile effort?

Martijn Verburg: By going to microprofile.io and joining the mailing list there, filling out the survey and shortly contributing code!

Hi all,

We’ve been remiss in posting our thoughts on our official votes for various Java standards that go through the  Java Community Process (JCP) Executive Committee (EC). So in order to get back into the swing of things we thought we’d start with the all important Java 9 SE vote!

For JSR 379 – Java SE 9 (See full results from all voters) we voted Yes for the JSR Review Ballot with the following comment:

We are very happy with the technical content and have high hopes that it will increase the longevity of Java in the age of containers and smaller devices.

We are disappointed with the relatively late release of this JSR. Since much of the RI and TCK has already been built, it makes it much harder for independent implementations to reach the market in a timely manner.

We see that Red Hat, IBM, Google and Oracle will likely make up the EG and we hope to also see wider participation from other JVM vendors.

In terms of technical merit we’re broadly happy.  There are certainly issues with Jigsaw vs the ‘real world’, which was anticipated and hopefully will be mitigated by further early testing of JAva 9 and some compromises made by both the authors of libraries, frameworks and products and the authors of the Jigsaw module system.  The rest of Java 9 offers up loads of exciting new features including HTTP 2 support, JShell and a host more.

To add some further insight on the other half of our comment, we need to explain the current challenge we have with OpenJDK vs the JCP standardardization process.  In short, OpenJDK is the GPLv2 licensed open source project that is the Reference Implementation (RI) for Java SE.  Oracle and most (not quite all) other vendors create their commercial ‘Java’ releases from OpenJDK.

However, in order to release a ‘Java’ which can be called Java, you must pass the Technical Compatibility Kit (TCK) which is produced as part of the Java Specification Request (JSR). If the JSR is delivered late on in the development of OpenJDK it puts vendors who produce a non OpenJDK based implementation at a massive disadvantage and even puts the vast majority basing their implementations off OpenJDK at a disadvantage in terms of getting their product complaint and to the market.

There’s also no real mechanism for the community to push back against proposed changes via the JCP, as so much work has already been done in OpenJDK. That is, what’s in OpenJDK is effectively fait accompli.  That’s not necessarily a bad thing as OpenJDK generally speaking provides that highly collaborative open source environment which allows for plenty of community feedback and influence (it’s still nominally Oracle controlled, but it’s about as good as you can get given single vendor ownership).

It does place OpenJDK and the JCP at odds though and we look forward to working with Oracle and the JCP to resolve that (there are some early proposals being discussed).


Martijn (On behalf of the LJC JCP Committee)

Hi all,

After much thought and consideration the LJC JCP Committee have cast their votes for the JCP elections (Look for the Executive Committee Elections link at jcp.org).  We’re making our vote public and will give our reasons according to the openness and transparency requirements for the committee.

The list of nominees for the seats are as follows (link also contains useful recordings and notes from the nominees):

There are 8 ratified seats and 5 open seats up for election.  Although it may seem like the ratified seats are shoe-ins since to the number of candidates == the number of available seats, enough no votes can make a candidate ineligible to take the seat.

Ratified Seat Vote

Freescale, Gemalto M2M GmbH, Goldman Sachs, MicroDoc, SAP, Software AG, TOTVS and V2COM all get yes votes – they are important players in the Java ecosystem.

In particular they represent:

  1. Strength in the emerging IoT market (Gemalto, Freescale and MicroDoc)
  2. The increasing importance of the BRIC economies on the ecosystem (TOTOVS and V2COM)
  3. The massive impacts on SE and EE platforms today (SAP, Software AG and Goldman Sachs).

In short, we think Oracle have chosen well and see no reason not to ratify these candidates.

Open Seat Vote

This was a very close vote as the strength of candidates was unprecedented. Here are our yes votes:

  1. Azul Systems – Azul is one of the few JVM vendors out in the marketplace. Their inclusion is vital in order to keep Java SE as an open standard and Gil Tene’s insights around thorny legal issues have proved to be invaluable to the EC.
  2. ARM Systems – The world needs Java to run well on ARM, they should be involved in evolving Java, simple as that!
  3. Hazelcast – Represent both strength in the EE space (JSR 107 and 347 for caching and distributed data grids) and also push the SE envelope with the requirements for their core product. Greg Luck is a long time experienced member of the JCP process, his expertise would be welcome.
  4. Waratek – Bring innovative new thinking about the JVM with regards to scalability and security in cloud environments with their multi-tenanted VM. As with Azul, it would be great to see other JVM vendors on the EC to keep help keep Java modern.
  5. Morocco JUG – Representing the voice of developers in the Middle East and Africa.  It’s estimated that a majority of new developers will come from these nations over the coming years and so they should continue to be included at the highest levels of Java.
  6. Geir Magnusson Jr – Geir was instrumental in helping shape Java in the early years of its existence and brings a wealth of experience and understanding of the broader Java ecosystem.  It’s great to see him back!

There were lots of other worthy candidates, but we feel these 5 candidates represent the best balance to face the challenges of the industry in 2015.


Although the Committee has voted for and endorsed these particular candidates, any LJC member who is also a JCP member can (and no doubt will!) vote any way they wish to.


Martijn (on behalf of the LJC JCP committee

Hi guys,

My name is Maggie Cranford and I’m a professional writer currently working with RecWorks, strengthening and developing tech communities in and around London.

I hope you enjoyed a break this summer.  We’re well into September already, and a new season of talks, meet-ups and workshops is getting underway in and around London.
Whether you are looking for details of regular sessions where you can get together with like-minded people, or sessions focused on more specific topics such as learning Apache Cassandra or tools and techniques to improve coding, all the contact details and information you need are given below.
Please do let us know which events you find particularly useful, as this will help the organisers of events in the future.

Monday 15th September
Evening Code and Coffee / Craft Beer
Every fortnight, we meet for coffee, code, craft beer, and some great food.
This is a great opportunity to:
• meet other cool software craftsmen
• work on pet or open source projects
• pair with someone else on whatever you like (katas, koans, etc)
• ask someone to join or help you with your own project
• have a face-to-face meeting with your mentor or mentee
• have a nice chat over coffee and beer
We’ll be meeting in “Look mum no hands!”, a laptop friendly cafe/bar that’s open until 10pm, and sells great coffee, excellent beers, and some tasty food. They also repair bikes and hang them from the ceiling like chandeliers, because why not? http://www.lookmumnohands.com/
London Software Craftsman Community

Monday 15th September
7 languages in 7 weeks: Clojure day 1
A workshop run in the Code Dojo format for people reading and working through the Pragmatic Programmers book “Seven Languages in Seven Weeks” by Bruce Tate. This time, we’ll be starting Clojure.
London Code Dojo

Wednesday 17th September
“Leaning on the two Ts” Mani Sarkar, & “Tests need love too” Colin Vipurs
Talk 1 – Leaning on Tools & Techniques to Improve Code Quality – Presented by Mani Sarkar (45 mins approx.)
Attendees of this talk will learn about my experience when learning to use static analysis tools (i.e. SonarQube) and some of its features. In addition also find out how it can be used to improve your code quality and personal practice. A number of tools will also be mentioned and how to include them in your practise.
Talk 2 – “Tests Need Love Too: Common Reasons Unit Tests Are Brittle” – Presented by Colin Vipurs (45 mins approx)
Any developer who cares about software quality should be committed to writing unit tests. Used well it can be a vital tool in every developer’s toolbox, but unfortunately the theory and practice don’t always match up. Easily-made mistakes can lead to brittle, unmaintainable and ‘write-only’ tests that not only become difficult to work on, but can lead to a hatred of unit testing in general. Presented here are examples of these mistakes with code samples, why you’re making them and how to avoid them in future.
London Java Community

Wednesday 17th September
1: Couchbase and Hadoop. 2: Sub-millisecond response times with Couchbase.
We needed a bridge between the real-time tier, where we used Couchbase, and the batch tier, built on Hadoop. When we couldn’t find a suitable option, we built our own: Couchdoop – an open-source Hadoop connector for Couchbase.
Based on our experience with Couchdoop, we will discuss best practices in creating connectors for Hadoop and NoSQL DBs. We’ll address the challenges we encountered while developing Couchdoop and share how we tuned it for performance.
Together with Bigstep, we will also show how much throughput that can be squeezed from a Hadoop connector. We have benchmarked Couchdoop for performance and we’ll talk about the behavior you can expect and tweaks that can improve the performance of your big data setup.

Thursday 18th September
Scala Coding Dojo
A regular coding dojo session run on every third Thursday of the month. The dojo is now held regularly at the central London offices of Springer.
London Scala Users’ Group

Thursday 18th September
HTML5, AngularJS, Groovy, Java and MongoDB all together – what could go wrong?
It seems to have been a common theme amongst startups to create the MVP (Minimum Viable Product) in a language that facilitates rapid prototyping (for example Ruby), and then migrate to the JVM when the application has proved itself and requires more in terms of stability and performance..
Virtual Java User Group

Monday 22nd September
Couchbase Server developer day
The ideal opportunity for developers to get their first taste of the Couchbase Server NoSQL document database.
In this hands-on session we’ll cover:
Couchbase concepts and architecture.
First steps with the Couchbase Java SDK.
Building a first simple Java app using Couchbase.
Querying data with Couchbase.
Introduction to data modelling with Couchbase.
Introduction to Couchbase Mobile.
All you need to bring is your laptop with your favourite Java IDE installed.
Lunch is provided.
We expect this event to fill up quickly so please note that we can offer access only to people who register using this Eventbrite event.

Monday 22nd September
Hazelcast introduction
David Brimley, Solutions Engineer at Hazlecast, will come give an introduction to the Hazlecast open source in-memory data grid.
Hazelcast will also be kindly providing pizza and drinks.
London NoSQL

Tuesday 23rd September
Michael Donaghy: Stacking Monads High
Scala’s rich type system makes it easy to include composable effects as part of a method’s type. Monads like Validation, Future, and Reader give us explicit control over when these effects happen; stacked monad transformers mean we can track several different kinds of effects without sacrificing code reuse. But if we try to control every effect we can quickly wind up wondering how we call our UserName => Reader[ApplicationContext, UserProfile] with an EitherT[({type L[A]=ReaderT[ApplicationContext, Future, A]})#L, NonEmptyList[NetworkError], UserName]. This talk looks at ways to keep monad stacks clear and concise.
London Scala Users’ Group

Thursday 2nd October
Apache Cassandra for Java Developers – Why, What & How – Johnny Miller
Java developers interested in learning about Apache Cassandra and how to use it. Attendees will be introduced to some of its most popular use cases and given an architectural overview of Cassandra. They will also be show how to model their data on Cassandra and how to use the Java driver.
London Java Community

Saturday 4th October
Architect Camp 5
Good architects Practice, Practice, Practice. A whole day architecting a system. Interview, Design, Validate. 30 people 6 teams, one objective… to become better at our craft. Java, .Net python….who cares… all welcome, just leave your ego’s at the door.
Software Architect & Mentorship Group

Wednesday 1st October
Meet A Mentor – University College London
**Undergraduates/Graduates only** Have you always wondered what you want to do when you graduate?
Are you worried about all the talk of grads finding it hard to find work and what it will mean for you?
Do you want to know the difference between working in a bank, a gaming company or a startup?
What technology should you specialise in? Java, Ruby or any of the other countless programming languages?
Now is the chance to find out. You may well have heard the buzz about the Meet a Mentor events – this is the next in a series of events open to all students.
Graduate Developer Community

Thursday 2nd October
London Platform as a Service – Heroku: time for a fresh look
Get a developer’s point of view on deploying your code without spending weeks learning DevOps tools. If you already know Git*, you know how to use Heroku. There are a lot of new things to see, from a new dashboard in Node.js to a new stack based on Ubuntu 14.04. We’ll cover the basics of how Heroku works underneath and the different levels of compute resources you can select (P1, P2 and PX dynos).
We will round off with some fun with Heroku Button, enabling anyone to deploy your app from your public Git repo to their own Heroku account at the press of a button!
* If you don’t know Git yet, we’ll be happy to show you how.
The London PaaS User Group (LOPUG)

That’s everything for now. If you’re interested in getting your group or event on the list then please let us know – bc @recworks.co.uk

Until next time,



Hi guys,

I hope you are enjoying the hot weather and managing to miss the thunderstorms!

Here’s a round up of the events that are taking place in and around London over the next couple of weeks that I’m sure you’ll want to check out.

The list includes details of the Whitechapel CoderDojo coding event for kids. We are always keen to do what we can to promote quality events for children, as they will be the developers of the future. If you don’t have kids yourself who would be interested, please mention the event to friends and family so as many budding developers as possible get the chance to find out what coding is all about.

Tuesday 22nd July
Speaking Out: A workshop for public speaking in tech
Public speaking is a great opportunity for people to raise their professional profile and employment opportunities. Unfortunately its also regularly identified as the activity which people fear the most. Its ok – we’re here to help! If you’ve thought about giving talks at your workplace, local user group or even international developer conferences but just need a little support to get started then you should come along to this event..
London Java Community

Friday 25th – Sunday 27th July
Summer of Hack
Summer of Hack 25-27, July 2014 @Shoreditch Village Hall at 7:00pm
MAY THE BEST MOBILE APP WIN! The Salesforce Summer of Hacks awaits you. Compete to win cash prizes by building the best mobile app that runs in the Salesforce1 Mobile App container found on the Apple App Store and Google Play. Bring fresh ideas, meet new people and build cool apps!
Go to http://www.summerofhacks.com/ to register now. Space is extremely limited!

Saturday 26th July
Test Camp
Good Software Architects Practice,Practice,Practice.
A whole day of defining “WHAT” to test.
Interview, Design, Validate. up to 30 people 6 teams, one objective… to become better at our craft. Java, .Net python….who cares… all welcome, just LEAVE your ego’s at the door.
Software Architect & Mentorship Group

Wednesday 30th July

Java 8 – Part 2!
Mark Harrison will continue our Java 8 discussions with a talk on Lambdas and Streams
Manchester Java Community

Saturday 2nd August
Whitechapel CoderDojo
CoderDojo Whitechapel for kids is a free coding club.
Saturday, 2nd August, from 2 to 5pm
At this session, there will be plently of things to choose to do:
learn how to code a website
host your website for your friends to see
learn how Java works and make some cool quizzes
or just work on your own projects with some assistances from the mentors
Don’t worry if you’ve never coded before, all you will need to do is bring a laptop and have fun. There will be mentors to assist you at every point.

Save the Date – Wednesday 6th August
GDG London
Do you like +Polymer or are you a frontend web developer and don’t know anything about Polymer yet?
Save *6th August* in your calendars, because +Eric Bidelman will be in London, details (including the registration link) to follow in nearest weeks.
Keep watching our channels.

Thats everything for now, If you’re interested in getting your group or event on the list then please let me know – bc@recworks.co.uk

Until next time,



What is the LJC

The London Java Community (LJC) is a group of Java Enthusiasts who are interested in benefiting from shared knowledge in the industry. Through our forum and regular meetings you can keep in touch with the latest industry developments, learn new Java (& other JVM) technologies, meet other developers, discuss technical/non technical issues and network further throughout the Java Community.