These are chat archives for spring-cloud/spring-cloud

16th
Nov 2015
Spencer Gibb
@spencergibb
Nov 16 2015 15:24
spring-cloud/spring-cloud-netflix#166
Borna Safa
@jarmaker
Nov 16 2015 17:04
    <dependency>
        <groupId>org.springframework.cloud</groupId>
        <artifactId>spring-cloud-starter-bus-rabbit</artifactId>
    </dependency>
does not work when checkout as part of start.spring.io 1.3.0 version
gives version error.
Dave Syer
@dsyer
Nov 16 2015 17:05
Must be a bug in the Spring Cloud BOM then. What version does it select?
Borna Safa
@jarmaker
Nov 16 2015 17:05
it does not:
my mvn -DskipTest clean run gives:
[ERROR] 'dependencies.dependency.version' for org.springframework.cloud:spring-cloud-starter-bus-rabbit:jar is missing.
relying on the parent BOM probably.
Dave Syer
@dsyer
Nov 16 2015 17:06
No, what version of Spring CLoud does it select?
I assume Brixton.BUILD-SNAPSHOT
Just raise an issue with spring-cloud-bus
Actually don't
There is no such starter
Probably needs to be fixed in start.spring.io
Spencer Gibb
@spencergibb
Nov 16 2015 17:07
that’s what I was thinking, should be -amqp
Borna Safa
@jarmaker
Nov 16 2015 17:08
@spencergibb ok. great, and yes Brixton.BUILD-SNAPSHOT @dsyer
I will just update my local pom to -amqp then thanks.
Dave Syer
@dsyer
Nov 16 2015 17:09
Looks like start.spring.io is trying to make a dictinction:
        - name: Cloud Bus AMQP
          id: cloud-bus-amqp
          description: A simple control bus with AMQP and spring-cloud-bus-amqp
          versionRange: "[0.0.0.RELEASE,1.3.0.M5]"
          groupId: org.springframework.cloud
          artifactId: spring-cloud-starter-bus-amqp
        - name: Cloud Bus Rabbit
          id: cloud-bus-rabbit
          description: A simple control bus with Rabbit and spring-cloud-bus
          versionRange: "(1.3.0.M5,9999.9.9.RELEASE]"
          groupId: org.springframework.cloud
          artifactId: spring-cloud-starter-bus-rabbit
It thinks we changed the name of the module from "-amqp" to "-rabbit"
(which would make sense given the names of the s-c-stream projects)
But we didn't
spring-io/initializr@6aea29f
Borna Safa
@jarmaker
Nov 16 2015 17:43
thanks
Dave Syer
@dsyer
Nov 16 2015 17:54
@jarmaker are you really @joshlong ?
(He's the one that usually always breaks start.spring.io by selecting everything just to see if it works)
Borna Safa
@jarmaker
Nov 16 2015 17:54
nope
but I like @joshlong
Spencer Gibb
@spencergibb
Nov 16 2015 17:55
:wink2:
Borna Safa
@jarmaker
Nov 16 2015 17:55
he recommended me to joint gitter
Dave Syer
@dsyer
Nov 16 2015 17:55
You seem to have picked up his habits
(Not a bad thing)
Borna Safa
@jarmaker
Nov 16 2015 17:56
Cool :P
so I broke something by giving you misdirection I suppose.
got to come up with the concept of elastic jars rather than glass, because once you break the conventional glass it is hard to make it ;P
Borna Safa
@jarmaker
Nov 16 2015 18:18
or did I?
Believe it or not it was his cloud-native workshop on git that instructed to do so :)
Is there a new milestone for SpringCloud that doesn't rely on that class?
Or is Snapshot the only option?
Spencer Gibb
@spencergibb
Nov 16 2015 19:05
Brixton.M2?
It is based on spring-boot 1.3.0.RC1
@checketts :arrow_up:
Spencer Gibb
@spencergibb
Nov 16 2015 19:11
looks like that’s in RC1, what problem are you seeing?
Dave Syer
@dsyer
Nov 16 2015 19:11
That class isn't in 1.3.0.RELEASE
I guess that means we need Brixton.M3 immediately
You can still use snapshots of course
Spencer Gibb
@spencergibb
Nov 16 2015 19:12
well, M2 is built on RC1 so it shouldn’t be broken
Dave Syer
@dsyer
Nov 16 2015 19:12
Yeah. I was just guessing it was mixing Brixton.M2 with Boot 1.3.0
I bet that's what it is if you look at the classpath
Spencer Gibb
@spencergibb
Nov 16 2015 19:13
right, that won’t work
checketts
@checketts
Nov 16 2015 19:36
@spencergibb @dsyer Yeah, I'm using Brixton.M2 and Boot 1.3.0.RELEASE
I'll hold off on our Boot upgrade til SpringCloud M3 is released.