In my own experience regarding the difficulty of naming something, it has always indicated the codebase is too big and multi-functional.
Thus, there are two paths to take: 1) Slap a brand name on it because no descriptive name can succinctly capture all the provided functionality 2) Break down the code base so you can apply individual descriptive names So, perhaps a change of perspective could help here.... Has anyone thought about breaking apart Aether after the import? Cheers, Paul On Thu, Aug 4, 2016 at 11:27 AM, Robert Scholte <rfscho...@apache.org> wrote: > It is all about Maven coordinates: groupId + artifactId + version + > extension ( + classifier) > This all together results in a URL to a repository. In case of remote > repositories these work both with M1 and M2 repository layouts (yes, the > name is confusing...) > So it is not just about java files/artifacts, any file with a Maven > coordinate will do. > > Robert > > > On Thu, 04 Aug 2016 01:29:17 +0200, Christian Schulte <c...@schulte.it> > wrote: > > It's really all about JARs... >> >> "Java Artifact Repository Specification" >> >> JARS >> >> Happenstance. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
