-
Notifications
You must be signed in to change notification settings - Fork 22
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
Project cannot be built from current public facing repositories referenced in pom.xml #100
Comments
All of the redhat maven repositories are failing periodically, so they are impossible to use. These two calls were within a couple of minutes. First it works, then a 404. I guess nobody is properly maintaining those repositories any longer. Dougs-MBP:wsdl2rest dougnewton$ wget https://repository.jboss.org/nexus/content/groups/ea/org/apache/camel/camel-parent/2.23.2.fuse-790031/camel-parent-2.23.2.fuse-790031.pom camel-parent-2.23.2.fuse-790031.pom 100%[====================>] 230.93K 759KB/s in 0.3s 2021-04-27 13:40:47 (759 KB/s) - ‘camel-parent-2.23.2.fuse-790031.pom’ saved [236471/236471] wget https://repository.jboss.org/nexus/content/groups/ea/org/apache/camel/camel-parent/2.23.2.fuse-790031/camel-parent-2.23.2.fuse-790031.pom |
it is the way the Fuse productization team has chosen to work. The versions are overriden automatically in the pipeline that builds all pieces of the product and the versions in source code are left behind. The versions in the ea repository are available only few days for most of it. |
I would understand if I was trying to build an old version, but I was thrown by the fact that I cannot build any version of this project. I do a fresh pull of the current branch and cannot build it. Of course, probably most of the problem is the instability of the public redhat/jboss repositories that sporadically fail or report 404 for certain artifacts. That case I mentioned above was a temporary problem. The artifact came back a few minutes later. Maybe it is certain servers in their cluster that are out-of-sync. |
It would appear that the maintainers of this project need to check the build directly against the public repositories referenced in the pom.xml, as it currently requires releases that do not (or no longer) exist in those repositories.
The text was updated successfully, but these errors were encountered: