Versions referred to in the pom.xml and tutorials may not be in sync with release 4.0.2
See original GitHub issueDescribe the bug
The cells that load the Jars for the notebooks under https://github.com/oracle/tribuo/tree/main/tutorials are not consistently loading the Jars for version 4.0.2 as per the release version.
Also in the pom.xml
(see source), it says <version>4.1.0-SNAPSHOT</version>
, should this not be in sync with the release and increment each time.
To Reproduce
Load the notebooks using an external docker image via here (would be the same if run in native mode)
Expected behaviour
Tutorials and pom.xml
be in sync with the release
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
POM Reference - Maven
xml tells Ant precisely what to do when it is run (procedural), a POM states its configuration (declarative). If some external force causes...
Read more >Maven Build Failure -- DependencyResolutionException
The error "Blocked mirror for repositories" is referred to explicitly in Maven's release note for version 3.8.1:.
Read more >Maven packages in the Package Repository - GitLab Docs
Publish Maven artifacts in your project's Package Registry. Then, install the packages whenever you need to use them as a dependency.
Read more >7 Understanding Maven Version Numbers - Oracle Help Center
In a Maven environment, it is very important to understand the use of version numbers. A well thought out strategy can greatly simplify...
Read more >The Google Services Gradle Plugin
The google-services.json file is generally placed in the app/ directory (at ... XML files which you can reference as Android resources in your...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Perfect,
v4.0.X-release-branch
works for me!There will be a release branch for each minor release which contains the point releases for that version, so depending on what you want you should either use the
v4.0.X-release-branch
or a specific version tag.