search

fabric8io / fabric8

fabric8 is an open source microservices platform based on Docker, Kubernetes and Jenkins
http://fabric8.io/
1.76k stars 504 forks source link

Dependencies in repository.jboss.org but not Maven Central #3498

Open rawlingsj opened 9 years ago

rawlingsj commented 9 years ago

With a clean maven repo the build fails. I can solve the repository.jboss.org host issue in my environment but I wanted to check as I seem to remember something on IRC suggesting that all dependencies should be available in maven central?

Could not transfer artifact org.overlord:overlord-commons-i18n:pom:2.0.11.Final from/to jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/): Connect to repository.jboss.org:80 [repository.jboss.org/10.5.105.47]
[INFO] Fabric8 :: Gateway :: ApiMan ....................... FAILURE [02:10 min]
[INFO] Fabric8 :: Gateway :: Model ........................ SKIPPED
[INFO] Fabric8 :: Gateway :: Core ......................... SKIPPED
[INFO] Fabric8 :: Gateway :: Fabric Support ............... SKIPPED
[INFO] Fabric8 :: Gateway :: Servlet ...................... SKIPPED
[INFO] Fabric8 :: Gateway :: Servlet :: Example ........... SKIPPED
[INFO] Fabric8 :: Karaf Features .......................... SKIPPED
[INFO] Fabric8 :: MQ :: Parent ............................ SKIPPED
[INFO] Fabric8 :: MQ :: Client ............................ SKIPPED
[INFO] Fabric8 :: MQ :: Camel AMQ Component ............... SKIPPED
[INFO] Fabric8 :: Swagger Model ........................... SKIPPED
[INFO] Fabric8 :: JGroups ................................. SKIPPED
[INFO] Fabric8 :: APM Agent ............................... SKIPPED
[INFO] Fabric8 :: CDI ..................................... SKIPPED
[INFO] Fabric8 :: Tooling ................................. SKIPPED
[INFO] Fabric8 :: Tooling :: Archetype Builder ............ SKIPPED
[INFO] Fabric8 :: Forge Addons ............................ SKIPPED
[INFO] Fabric8 :: Forge Addons :: Kubernetes .............. SKIPPED
[INFO] Fabric8 :: Wiki .................................... SKIPPED
[INFO] Fabric8 :: Integration Tests ....................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:53 min
[INFO] Finished at: 2015-02-21T17:19:52+00:00
[INFO] Final Memory: 138M/699M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project gateway-apiman: Could not resolve dependencies for project io.fabric8:gateway-apiman:jar:2.2-SNAPSHOT: Failed to collect dependencies at io.apiman:apiman-gateway-engine-core:jar:1.0.1.Final -> org.overlord:overlord-commons-i18n:jar:2.0.11.Final: Failed to read artifact descriptor for org.overlord:overlord-commons-i18n:jar:2.0.11.Final: Could not transfer artifact org.overlord:overlord-commons-i18n:pom:2.0.11.Final from/to jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/): Connect to repository.jboss.org:80 [repository.jboss.org/10.5.105.47] failed: Connection timed out -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :gateway-apiman
Build step 'Execute shell' marked build as failure
IRC notifier plugin: Sending notification to: #fabric8-cd
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE
davsclaus commented 9 years ago

@KurtStam is jboss overload going to be published to maven central, or in other words is all of api man dependencies eventually in maven central for community point of view?

KurtStam commented 9 years ago

On 3/9/15 12:11 PM, Claus Ibsen wrote:

@KurtStam https://github.com/KurtStam is jboss overload going to be published to maven central, or in other words is all of api man dependencies eventually in maven central for community point of view?

— Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/3498#issuecomment-77884645.

Is is already in maven central. Is there an issue?

davsclaus commented 9 years ago

@KurtStam its not api-man, but overload.

Overload is not there at all http://search.maven.org/#search%7Cga%7C1%7Corg.overlord

davsclaus commented 9 years ago

And it seems api-man uses overload.

KurtStam commented 9 years ago

It's not supposed to. Eric will address it.

EricWittmann commented 9 years ago

Yes, apiman currently has a dependency on overlord-commons. I've been slowly moving away from overlord-commons to reduce the set of dependencies, at least for the API Gateway.

I will remove this one as well, asap.

davsclaus commented 9 years ago

@EricWittmann , @KurtStam are we all set now? Is there anymore dependencies from apiman that are not from maven central?

EricWittmann commented 9 years ago

Not quite yet. However, I'll be releasing apiman 1.1.2.Final today or tomorrow and I will remove the remaining overlord-commons references for this version.

EricWittmann commented 9 years ago

Confirmed: the next version of apiman will be devoid of all overlord-commons references. Didn't manage to get a release done today, but hopefully tomorrow.