-
Notifications
You must be signed in to change notification settings - Fork 837
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
Needs build instructions #17
Comments
Updating spring-boot to 1.4.3.RELEASE seems to fix the exceptions. |
Hi JetForMe, where have you updated the Spring-Boot version. In the pom.xml ? |
I was using Gradle, so it would've been in the gradle build file. |
But I am trying to do from Eclipse IDE. |
You will need to modify the pom.xml to use a later version of the
spring-cloud parent. Try changing Brixton.RELEASEtoCamden.SR6.
…--
Alternatively look at the maven dependency XML on the Spring Cloud project
page: http://projects.spring.io/spring-cloud/
It takes a different approach, importing Spring Boot 1.4.5 as the parent
and using Spring Cloud as a BOM (the dependencyManagement section).
Either way you will need to run Maven -> Update Project in Eclipse once
you've updated the pom.xml.
On 21 March 2017 at 20:41, Amalraj7692 ***@***.***> wrote:
But I am trying to do from Eclipse IDE.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABkXgrc_ZtPCPd3tMp8IumkcsUQu-nkDks5rn5tDgaJpZM4LVLMa>
.
|
Hi Paul, I didnt notice your reply. But yes, I have modified the release as Camden.Release and it worked like a charm. Thanks a ton. |
Upgrading to Camden.RELEASE and updating the build.gradle as described in https://spring.io/blog/2016/09/26/spring-cloud-camden-release-and-brixton-sr6-are-available |
Have added note that |
I'm trying this demo on macOS. But you need some command-line build instructions. What gradle command do I invoke? I tried
gradle jar
, and that did something, but the results are inbuild/libs
, nottarget
.Anyway, trying to run that jar, I get:
gradle build
works better, but I get:The text was updated successfully, but these errors were encountered: