after seeing this issue and the way it was solved JCenter and Bintray not in Sync I'm wondering if this is a general or specific problem. I'm having the same issue, I published version 1.2.0 and synced OK, but then I published 1.2.1 and it never made it to JCenter.
I did update the groupId in between releases, may that be related?
http://jcenter.bintray.com/com/mofiler/
https://bintray.com/btafel/maven/mofiler-sdk
Thanks.
We have relinked your package according to the new GroupID. This is indeed similar to the scenario described in the linked mentioned by you:
The package was included to JCenter under a particular GroupID and changing that, would need a path prefix change for the inclusion path.
Usually, when a change for the for GroupID of a JCenter linked package is needed, one should create a new package with the updated path in order to preserve consistency of other users depending on the already included artifacts.
Related
Yarg library https://bintray.com/cuba-platform/main/yarg is linked to JCenter repository. When I try to check JCenter storage: https://jcenter.bintray.com/com/haulmont/yarg/yarg/ There are only old versions from Maven Central. Why does JCenter includes them?.
Why do new versions are not synced to JCenter? It seems that the new package is conflicting with these old packages.
Thank you for putting this into our attention.
With regards to the issue you describe, we have managed to find the root cause for it.
There was a sync issue between Bintray and JCenter after approving the package to JCenter. Since that, new packages could not sync.
We hope this clarifies and resolves your enquiry.
Please let us know if you have any follow up questions.
Yonatan Brand,
JFrog Support.
I have a package in Bintray called "tripod" which is here:
https://bintray.com/bbende/bbende-maven/tripod
The tripod package is a Maven project with a standard multi-module setup where the root pom artifactId is tripod, with sub-modules of tripod-search-api, tripod-search-solr, and tripod-search-lucene.
In my personal Maven repo, all of these artifacts are published under the groupId com.bbende.tripod as shown here:
https://dl.bintray.com/bbende/bbende-maven/com/bbende/tripod/
When I requested to link the tripod package to JCenter using the link on the main package page for "tripod" it ended up linking only the artifact for the top-level pom as seen here:
http://jcenter.bintray.com/com/bbende/tripod/
How are you supposed to get the entire package linked to JCenter?
I believe this is the same issue here which looks like it requires manual intervention from someone at bintray/jcenter:
Bintray does not sync one of the artifacts of the package to the jcenter
A Bintray package is linked to jcenter with a specific path prefix, so that all submodules and versions under the base path will automatically be linked to jcenter without further manual intervention.
It seems like your package is linked under the base path containing only one of the submodules, therefore, the other submodules are not linked to jcenter.
In such cases, you should contact JFrog support in order to fix the inclusion path. In this case, we have already fixed it and all submodules are correctly linked to jcenter.
Best Regards,
Itamar
I published a Scala library in Bintray, for Scala 2.11 and 2.10
But in JCenter, it is only available the Scala 2.10 version.
I thought that it was in sync automatically, but looks like I was wrong.
Any idea how to sync both repositories?
Usually when changing the artifact path you won't be able to resolve your content through JCenter although it was previously included.
The reason for this is that the inclusion of your scala library in JCenter is for the files’ path.
Therefore, it was originally included under the path prefix 'com/acervera/osm4scala/osm4scala-core_2.10'.
However, we have re-linked your scala library on the GroupId level so your versions will be synchronized automatically:
'osm4scala-core_2.10', 'osm4scala-core_2.11', etc..
Guy.
My organization has several maven repositories on bintray. Most of these repositories contain a single package of the same name as the repository.
These packages seem highly related and I would like to reorganize them by creating a single repository and moving all these packages into it.
What is the best way to move packages between own repositories given the following constraints:
the package must remain available in the old repository as a link to the package in the new repository.
some of packages are linked to jcenter and they must remain linked after the moving.
I'll quote here a response from my conversation with JFrog support:
Since it is not possible to link a package from one repository to another within the same organisation, the best option would be to move these packages to the new repository while maintaining the link to jcenter. This leave the old repositories empty and then you would be able to delete them entirely. It is not possible to retain a link from the old repository to the new one.
Please notice that the move operation is an internal process and can only be done by us.
Unfortunately this approach doesn't satisfy my first requirement that the package must remain available for downloading from the old repository.
i have following requirement.
i need to download the latest version of artifact from custom nexus repository rather than snapshot repository.
please suggest
Thanks.
To get the latest version of any artifact, just omit the <version> tag from the dependency. This way maven will always fetch the latest version of this artifact from the remote repo.
Warning: Keep in mind that this is not the preferred way to handle dependencies nor it is the proper flow of dependency management. By keeping the version number open ended, there is a very high probability that your project may fetch a particular version of any library that is now not backward compatible and may break your functionality in the project. It is, therefore, always recommended to specify a particular version number of all artifacts that are required for any application and when updating any library version, one should properly test it.
EDIT
For maven3 you can use the facility of an open ended version tag. Something like this
<version>[1.12.4,)</version>
Take a look into this page for further details about version ranges
According to this issue: https://issues.apache.org/jira/browse/MNG-3092 snapshots cannot be excluded (at least until this is fixed).