-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing JARs for 1.4.x in official Maven Repos #339
Comments
Yes that's exactly how it's supposed to be. Every version since 1.3 Moneta has been modular and you need to use it as a "BOM", see https://github.com/JavaMoney/javamoney-examples/blob/master/console/javamoney-console-simple/pom.xml or the README in this repo. |
Sorry, but this can not be used, how a BOM is supposed to be used. When importing the BOM
you should be able to import the artifacts without using the version number:
but this is not possible, as the If you try to use:
the |
As this is the Moneta Parent POM the version number in dependency management is totally fine. |
Not sure what you mean by this. How is you "BOM" supposed to be used? Can you give an example where only the |
I think the problem is, that your "BOM" already defines dependencies and not only versions, what BOMs should only do. |
Well somewhere you must define them, otherwise you won't find any, but defining a "BOM" is up to you, the examples work the way they are. If you feel the need or would like to contribute to a true "BOM", see this very old ticket: JavaMoney/javamoney-parent#4 |
No JAR files of the releases 1.4.* are available anymore. Only *.pom files.
Please check.
https://repo1.maven.org/maven2/org/javamoney/moneta/1.4.2/
https://repo1.maven.org/maven2/org/javamoney/moneta/1.4.1/
https://repo1.maven.org/maven2/org/javamoney/moneta/1.4/
https://oss.jfrog.org/artifactory/oss-release-local/org/javamoney/moneta/1.4.2/
https://oss.jfrog.org/artifactory/oss-release-local/org/javamoney/moneta/1.4.1/
https://oss.jfrog.org/artifactory/oss-release-local/org/javamoney/moneta/1.4/
The text was updated successfully, but these errors were encountered: