Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] EE4J code conventions?

Well by taking the burden, honor and responsibility of a 20y Enterprise standard Eclipse will also have to do a bit of standard-setting now, at least in this particular area.

If at least a minimum level of code quality and consistency in the codebase cannot be archieved, why would large enterprises still use Java / Jakarta EE instead of Dropwizard, Spring Boot, Angular or a combination of JS from GitHub that certainly don't care about each other's coding standards or quality?;-)

Spring has a Java Coding Styleguide: It is somewhat inspired by Google's efforts:

I strongly suggest, something similar also gets created if not for all of Eclipse then EE4J does something similar. A tiny skeleton exists: but it merely covers things like license headers now.

The failure to even get TCKs work under a single umbrella or get a proper BOM, Parent POM, etc. at MicroProfile show us how bad it would be for Jakarta EE if those things continue to happen the same way here.

The balance between a reliable Enterprise platform that survives for at least another 2 decades and "Sons of Anarchy" may be hard to find, but it should be found if Jakarta EE still wants to matter. Pivotal and Google may play a very similar role as Oracle does in the current Java EE and Java ecosystem, but both have their projects developed Open Source for most parts and contributors stick to those conventions whether they enforce it via build tools or not.


On Mon, Apr 9, 2018 at 3:18 PM, <ee4j-community-request@xxxxxxxxxxx> wrote:
Send ee4j-community mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ee4j-community digest..."

Today's Topics:

   1. Re: EE4J code conventions? (Alexander Salvanos)
   2. Re: EE4J code conventions? (Mike Milinkovich)


Message: 1
Date: Mon, 9 Apr 2018 15:16:33 +0200
From: "Alexander Salvanos" <salvanos@xxxxxx>
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] EE4J code conventions?

Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL: <>


Message: 2
Date: Mon, 9 Apr 2018 09:18:35 -0400
From: Mike Milinkovich <>
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] EE4J code conventions?
Content-Type: text/plain; charset="utf-8"; Format="flowed"

On 2018-04-09 9:11 AM, arjan tijms wrote:
> On Mon, Apr 9, 2018 at 1:58 PM, Kevin Sutter <sutter@xxxxxxxxxx
> <mailto:sutter@xxxxxxxxxx>> wrote:
>     +1, Dmitry.? Coding conventions should be a project-specific
>     requirement, not an EE4J requirement.? EE4J could possibly
>     recommend some coding conventions, but the requirements should be
>     left up to each individual project.
> While the goal is to have code conventions, and having them at the
> project level is definitely better than having none at all, I do
> wonder why we would even want different conventions per project?

Because Eclipse Foundation open source projects are self-governing
meritocracies, and we don't tell them what to do. Ultimately, it is the
committers who would need to do the work, and I don't think any of us
get to tell them how to spend their time.

I'm not saying that this is an unreasonable idea. But generally speaking
open source projects don't respond well to being ordered about. Ivar has
already said that he'll raise it with the PMC. Let's wait and see how
that plays out.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>


ee4j-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

End of ee4j-community Digest, Vol 8, Issue 36

Back to the top