Converting a docker POC to a kubernetes project and based on Spring documentation (https://spring.io/projects/spring-cloud-kubernetes), I tried to add a spring-cloud-starter-kubernetes-all maven dependency and keep getting version not defined though I added spring-cloud dependency pom. Upon checking, found the "all" starter dependency is applicable for kubernetes client (spring-cloud-starter-kubernetes-client-all) and not to include entire spring cloud kubernetes starter dependencies (spring-cloud-starter-kubernetes-all). The spring cloud I am using is 2021.0.3. Am I missing anything or there are some other gap in the documentation?
Related
I can port spring authorisation server into Eclipse via the gradle project, but I am stumped on how to also add spring security config as a code dependency so that I can update the config classes.
I am unsure how to link the 2 projects as in Eclipse it is using a library classpath built from gradle config.
I have tried adding spring security as a implementation project and adding a projectdir but it fails as it cannot classes and plugins to build the classpath.
Any ideas? Tried contacting the development team but no response so far.
Tried contacting the developers
adding project dependency
I upgrade the spring cloud to 2020.0.3 right now, shows error Could not find org.springframework.cloud:spring-cloud-starter-netflix-ribbon when compile the project. Should I manage the component independent? why this component did not follow the spring cloud version?
I'm not sure if I'm on the right track, but I can't find similar question on google or stackoverflow.
I'm using eclipse (luna), and I have this plugin from amazon, aws toolkit. When I create a project by clicking 'new aws web project', a new project will be created, and inside the aws sdk for java, some of the jar files have a version which is not I want, for example, spring-core-3.0.7.jar.
I tried convert this project to maven project and include dependency with latest spring-webmvc 4.x, but is seems two packages have conflict with each other. ref:
why .NoSuchMethodError: org.springframework.core.convert.converter.ConverterRegistry.addConverter
Two Maven Dependency for latest and old version conflicts
Spring MVC - Why the NoSuchMethodError exception when deploying context?
I tried to delete or upgrade the jar from aws sdk for java, but I can't find a way to delete it or upgrade it.
Then, I tried to create a normal java web project, convert to maven project and include the aws-java-sdk-core from maven repository, but after that I can't use the deploy to elastic beanstalk function.
Actually, I just want to create a project which let me use the latest spring framework, and also able to deploy to aws elastic beanstalk.
Follow steps:
create aws java web project
convert to maven project
delete aws java sdk package
add necessary jar using maven pom.xml
upload to aws elastic beanstalk
it works.
i am trying to deploy to Fuse Fabric. The application is built using Spring, Camel, CXF, WS-security, drools and Guvnor.
i was able to deploy the application to Karaf container, but when i deploy the same in Fabric using the FAB deployment. it is throwing the below error stack.
java.lang.Exception: Can not resolve feature:
Unsatisfied requirement(s):
---------------------------
package:(&(package=org.ops4j.pax.exam.options)(version>=1.2.0)(!(version>=2.0.0)))
Apache Aries Unit Test Support
package:(&(package=org.apache.aries.mocks)(version>=0.3.0))
com.eissDemo.ServiceV2
package:(&(package=org.ops4j.pax.exam)(version>=1.2.0)(!(version>=2.0.0)))
Apache Aries Unit Test Support
package:(&(package=javax.xml.namespace)(version>=5.0.0.2)(version<=5.0.0.2))
com.eissDemo.ServiceV2
package:(&(package=org.apache.aries.unittest.fixture)(version>=0.4.0))
com.eissDemo.ServiceV2
package:(&(package=org.apache.aries.unittest.mocks.annotations)(version>=0.3.0))
com.eissDemo.ServiceV2
package:(&(package=org.apache.aries.itest)(version>=0.4.0))
com.eissDemo.ServiceV2
package:(&(package=javax.xml.soap)(version>=5.0.0.2)(version<=5.0.0.2))
com.eissDemo.ServiceV2
package:(&(package=org.junit))
Apache Aries Unit Test Support
package:(&(package=org.apache.aries.unittest.mocks)(version>=0.3.0))
com.eissDemo.ServiceV2
package:(&(package=org.apache.aries.unittest.junit)(version>=0.3.0))
com.eissDemo.ServiceV2
package:(&(package=javax.persistence)(version>=5.0.0.2)(version<=5.0.0.2))
com.eissDemo.ServiceV2
package:(&(package=junit.framework))
Apache Aries Unit Test Support
package:(&(package=org.objectweb.asm)(version>=3.3.1)(version<=3.3.1))
com.eissDemo.ServiceV2
Firstly, The above error is asking me to include the Junit and mock related frameworks in the Fabric container, which is not required!? these frameworks are added with the "test" scope in the maven.
Secondly, the dependency "aries" is not being used in the project directly. It is used by the camel-cxf framework. But still it is asking the "aries" jars to be mentioned in the dependency. The FAB deployment should take care of these 3rd party dependencies or it defeats the purpose of using it!!
Third, the soap and namespace dependency are present in the maven dependency with the request version. still it is complaining!
i have the following features installed in the fabric
cxf
camel-xstream
camel-jaxb
camel-spring
camel-jms
camel-blueprint
spring
camel-core
fabric-camel
camel-spring-javaconfig
war
and the following maven features URLS
mvn:org.apache.servicemix.nmr/apache-servicemix-nmr/1.6.0.redhat-60024/xml/features
mvn:org.apache.cxf.karaf/apache-cxf/2.6.0.redhat-60024/xml/features
mvn:org.jboss.fuse/jboss-fuse/6.0.0.redhat-024/xml/features
mvn:org.apache.camel.karaf/apache-camel/2.10.0.redhat-60024/xml/features
and the application is used as the fab
mvn:com.xxxx/ServiceV2/1.0.0-SNAPSHOT
can anyone tell me if i am using enough features or i need more, if so what all needs to be included? why do i need to include the testing frameworks in the fabric? or how do i avoid them being deployed in the fuse fabric?
I developed a sdk that integrates the consul and actuator dependencies of the microservices, but there is a problem. If the actuator dependency exists, it always reports an error, the consul injection configuration fails. and the actuator is removed it will be ok.
some code :
https://github.com/lixinglin213/spring-cloud-sdk