Nani Pluginis in the Video Creation Tools Industry

Nani Plugin

naniplugin

A central aspect of Java's philosophy is that . names matter Brian Goetz, Java Language Architect and author of Java Concurrency in Practice Packages If you work for "acme.com" and you're working on a project called "foo" then is for your root package to be . the convention com.acme.foo Being a , we tend to add lots of "grouping" packages. Our foo project is a utility library, and we might make other ones, so we put it into , to make sure there is space for other utility projects. If we're really forward-looking, we'll take into account that foo is a utility library for manipulating text, so we better put it into . On the other hand, . forward-looking bunch com.acme.util.foo com.acme.util.text.foo YAGNI In the javascript world, there are no packages, you just get one name - - and that's it. I'm glad that I do most of my work on the JVM rather than a runtime which was , but whenever I start nesting my root package deeper than , I try to remember that all those gobs of software being written in Node.js are getting by without any nesting at all, so maybe I can get by with 3 or 4 levels of nesting for my root package, rather than 5 or 6. foo designed and built in 10 days com.acme.foo Maven groupId:artifactId One nice thing about files is that you don't have to pick names for them - they get their name automatically from a 1:1 mapping on the file they came from. Unfortunately, maven asks you to pick names, so it can't be that simple. Luckily, maven also provides not only , but slightly different conventions for how to pick these names! .class .java two one two Accordingly, if you ask , you'll see two popular answers. And when a major library like RxJava ships a new version, you'll need a to figure out what the names ought to be. StackOverflow 12-screen-long debate Luckily, there is a mechanistic answer out there! JitPack turns any git commit into a maven artifact at , which I've found to be huge improvement over for integration testing. The naming convention that it uses is: https://jitpack.io -SNAPSHOT (also , , and ) com.github.{user}:{repo} com.gitlab org.bitbucket com.gitee for multi-module builds com.github.{user}.{repo}:{subproject} If you use JitPack's integration, then you can replace with com.acme for a professional touch. Even if you don't use JitPack, using this convention will mean that you , and it lays down a simple rule that works well enough for . custom domain com.github.{user} could all these people Gradle plugin id In Gradle-land, you can apply a plugin like this: . plugins { id 'any.plugin.id.you.want' } Gradle provides an excellent : guideline As a convention, we recommend you use an ID based on the reverse-domain pattern used for Java packages, for example org.example.greeting. The trouble is, a huge number of the plugins which have been published so far are named... . It seems reasonable while you're the plugin, and you don't realize how silly it is until you it from a distance: gradle-plugin writing use plugins {
    id id id } 'com.acme.gradle.foo' 'org.nonprofit.bar.bar-gradle-plugin' 'beetlejuice.beetlejuice.gradle' What kind of car is that? That's the Chevy Corvette Car. What kind of phone is that? It's an iPhone XS Phone. Wouldn't this be better? plugins {
    id id id } 'com.acme.foo' 'org.nonprofit.bar' 'beetlejuice' It's interesting, because the guidelines that Gradle gives are very good - no excessive nesting, no unnecessary , just the bare minimum. And yet, a lot of the people who it feel like they should add a or two, just in case. Probably the only way to save us from ourselves would be for the gradle tooling to search for in the id and throw a warning, to help us think about it a little before we publish. gradle.gradle use gradle gradle Lessons Designing namespaces is a rare opportunity. Most of us never do it even once in our entire career. And since nobody has experience in it, we're still making lots of beginner mistakes, even in the quarter-century-old world of java. It's hard! Typosquatting, , there are so many pitfalls. If I ever end up defining a namespace, I'm gonna try to remember these lessons: IDN homograph attacks namespaces are helpful for identifying the author/maintainer: com.acme.foo 👍 namespaces are overkill for fine-grained categories: com.acme.util.text.foo 👎 defining the name to be a tuple of two other names is 👎 if the names are all plugins to foobar, people are just gonna name them my-foobar-plugin, and it might be good to warn them ¯\_(ツ)_/¯ Previously published at https://dev.to/nedtwigg/names-in-java-maven-and-gradle-2fm2

Stories, News & Mentions about NANIPLUGIN

Naniplugin’s Stories on HackerNoon