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

What about setting a convention and plugin for spec implementation approval?

Each project is free to do their code as they want, but once they submit it to the Jakarta EE Spec WG for compliance certification, we could ask them for the code to be follow a certain convention.

This would not be a trivial task for the project, but would allow both their autonomy on creation, and give us a more homogeneous code base at the umbrella project level.
Also, while still not trivial, the use of plugins to reformat the code as needed would make this task doable

Mariano Amar

Senior Consultant

email/hangouts:Âmariano.amar@xxxxxxxxxx
skype:Âmarianoamar

AVISO DE CONFIDENCIALIDAD DE CORREO ELECTRÃNICO

Esta comunicaciÃn contiene informaciÃn que es confidencial y tambiÃn puede contener informaciÃn privilegiada. Es para uso exclusivo del destinatario. Si usted no es el destinatario tenga en cuenta que cualquier distribuciÃn, copia o uso de esta comunicaciÃn o la informaciÃn que contiene està estrictamente prohibida. Si usted ha recibido esta comunicaciÃn por error por favor notifÃquelo por correo electrÃnico(info@xxxxxxxxxx) o por telÃfono (+54 11 3249 7503)

This communication contains information that is confidential and may also be privileged. It is for the exclusive use of the recipient. If you are not the intended note that any distribution, copying or use of this communication or the information it contains is strictly prohibited. If you have received this communication in error please notify us by email(info@xxxxxxxxxx) or phone (+54 11 3249 7503)


On Mon, Apr 9, 2018 at 10:18 AM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> wrote:
On 2018-04-09 9:11 AM, arjan tijms wrote:
On Mon, Apr 9, 2018 at 1:58 PM, Kevin Sutter <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.



_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community