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

5th
May 2016
Marcos Barbero
@marcosbarbero
May 05 2016 14:04
@dsyer related to this issue spring-cloud/spring-cloud-netflix#865 I’m still getting status code 200 even when the route is down.
In my case I’ve a fixed route configured in zuul.routes, when the service is running it works fine but when it’s down I receive this exception com.netflix.zuul.exception.ZuulException: Forwarding error and status 500 in RibbonRoutingFilter but the final response is 200.
I’m using Brixton.RC2
Pedro Vilaça
@pmvilaca
May 05 2016 14:49
hey guys
I’m upgrading a service to Brixton.RC2 but I’m getting an error while running the build that doesn’t happen when using RC1
<dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>org.springframework.cloud</groupId>
                <artifactId>spring-cloud-starter-parent</artifactId>
                <version>Brixton.RC2</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>
error:
[WARNING] The POM for org.springframework.cloud:spring-cloud-starter-security:jar:1.1.0.RC2 is missing, no dependency information available
Spencer Gibb
@spencergibb
May 05 2016 14:51
artifactId should be spring-cloud-dependencies
Pedro Vilaça
@pmvilaca
May 05 2016 14:51
thanks @spencergibb
let me try
Spencer Gibb
@spencergibb
May 05 2016 14:52
I think that was fixed, but you might need to delete the bom from the local maven repo.
Pedro Vilaça
@pmvilaca
May 05 2016 14:52
I’m getting the same error
which bom?
Spencer Gibb
@spencergibb
May 05 2016 14:53
the spring cloud starters bom
Pedro Vilaça
@pmvilaca
May 05 2016 14:55
well.. it’s weird because the dependency is in the dependency management
it looks like a problem in the repo itself
let me check
Spencer Gibb
@spencergibb
May 05 2016 14:55
yeah, that version never existed,
Pedro Vilaça
@pmvilaca
May 05 2016 14:56
ah.. so you re-released Brixton.RC2?
Spencer Gibb
@spencergibb
May 05 2016 14:57
Yes, I think that is what happened. So if you already downloaded it in the window, you have the faulty one.
Pedro Vilaça
@pmvilaca
May 05 2016 14:58
I need to delete it from our nexus repo
Spencer Gibb
@spencergibb
May 05 2016 14:58
ahh
Pedro Vilaça
@pmvilaca
May 05 2016 15:04
the artifact is coming form atlassian repo
and not from spring milestones repo
Spencer Gibb
@spencergibb
May 05 2016 15:07
which repo?
Pedro Vilaça
@pmvilaca
May 05 2016 15:08
in our nexus repo
Spencer Gibb
@spencergibb
May 05 2016 15:08
ok
Pedro Vilaça
@pmvilaca
May 05 2016 15:08
we also have the atlassian repo
as a remote repo
and spring milestones repo
and when I’m running a build, Brixton.RC2 is coming from atlassian repo and stored on our nexus repo
thanks anyway
I’ll check how to solve this
btw.. when are you planning to do the final release?
Spencer Gibb
@spencergibb
May 05 2016 15:10
after spring boot 1.3.4 which lands friday. So beginning of next week.
Pedro Vilaça
@pmvilaca
May 05 2016 15:12
:thumbsup:
Pedro Vilaça
@pmvilaca
May 05 2016 15:19
problem solved.. just changed my nexus configuration to use spring milestones repo before atlassian repo
Spencer Gibb
@spencergibb
May 05 2016 15:19
great. We have plans to avoid these kinds of failures in the future.
Pedro Vilaça
@pmvilaca
May 05 2016 15:21
yeah.. that would be great but everyone that is in the world for a while know that sometimes shit happens :)