When I prepared my KUG talk and ran Scratch files for each of the README examples, I stumbled across problems with uom-systems dependencies and underlying calls. Not sure, why it did not show in the build, but some of them only seem to occur at runtime. As 0.9 of both si-units and all uom-systems was released on top of Indriya 1.0 I migrated everything to the Indriya version (still JSR 363)

I proposed a new version 1.1.4.0.

The way Physikal is currently packaged on maven central, the pom e.g. of si-units-1.1.1.0 currently includes:

    <dependency>
      <groupId>si.uom</groupId>
      <artifactId>si-parent</artifactId>
      <version>0.7.1</version>
      <scope>compile</scope>
    </dependency>

This breaks consumers of Physikal using maven to build:

[ERROR] Failed to execute goal on project model-nosql: Could not resolve dependencies for project de.xxx.core:model-nosql:jar:0.9: The following artifacts could not be resolved: systems.uom:systems-parent:jar:0.7.2, si.uom:si-parent:jar:0.7.1: Failure to find systems.uom:systems-parent:jar:0.7.2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]

I think the situation si somewhat similar to https://stackoverflow.com/questions/27110014/could-not-find-artifact-in-maven-central-repo-when-search-returns-a-match

In any case, I believe the parent pom is not necessary as a direct dependency. I confirm I can build and consume phyiskal to my local repo just fine using the change in this PR.

Tenkiv/Physikal now has a Chat Room on Gitter

@ejberry has just created a chat room. You can visit it here: https://gitter.im/Tenkiv/Physikal.

This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.

Happy chatting.

PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.