I am checking the Quarkus guide for the flyway extension.
The default schema configuration is not listed and is not supported. I added in my application.properties
quarkus.flyway.default-schema=some_schema
quarkus.flyway.defaultSchema=some_schema
and tested, but it's not recognised. Is there a workaround or should an issue be created?
I have opened https://github.com/quarkusio/quarkus/pull/22957 to address this concern.
If all goes well, this will make it into version 2.7.0.Final.
got defaulted to
quarkus.flyway.default-schema=some_schema
just in case anyone is seeing this now
Related
With the new Intellij version (2022.3) Maven is no longer the default type (is has selected Bradle- Groovy) for a Java Project when using the spring boot initializr.
This is extremely annoying since Maven used to be the default option.
I have searched through all relevant settings I could come up with, without any luck.
Can anyone explain how to change the default settings for the spring intializr?
I also asked the question on IntelliJ support, and unfortunately this is not posible (yet)
As a consequence of my request, they have opened a feature request to allow for this:
https://youtrack.jetbrains.com/issue/IDEA-311387
If you, like me, are annoyed by this change please upvote the request
Since new SB configuration property spring.config.import in SB 2.4, I cannot get integration tests working. Previously, I had bootstrap-test.yml with spring.cloud.consul.enabled: false and it worked nicely. Since upgrade to 2.4.3, I have spring.config.import: "consul:" in application yml, and nothing seems to disable it in application-test.yml file. I have tried every possible combination of overriding spring.config.import: "optional:consul:" and setting spring.cloud.consul.enabled: false in application-test.yml. Yet I am still getting the same error
Config data resource ... via location 'consul:' does not exist
I don´t want to use optional import in application.yml, since main should not start without it. Only thing that seemed to help was setting use-legacy-processing: true but I don´t understand why.
This is likely just a workaround according to the comments on the question but it works for me for the moment. Your milage may vary.
Specifying the spring.config.import property as an environment variable allowed it to not be set for the tests but to work for the point where the application was deployed.
My full setup.
application.yml contains normal consul enabled config.
application-standalone.yml just disables all properties except spring.config.import
spring.config.import is only added to the launch parameters.
After updating the version of spring-cloud the value are not decrypted server side. It worked fine in the previous versions, and I did not find anything regarding this issue in the Edgeware release notes.
Am I missing something? Is there an undocumented change with this version?
My issue is related to this: https://github.com/spring-cloud/spring-cloud-config/issues/684
Basically - if I understand this correctly - in Edgeware decryption of environment variables (this is the key I think) works only in bootstrap.yml and not in application.yml
I am using the Spring Guide for the MongoDB-data-rest-complete example and I want it to use a specific mongodb database, rather than the default one ('test'). How do I do this?
Ok I got it running! The answer is that the application.properties file may go in the src/main/resources folder!
I am using Netbeans as my IDE, currently developing an Web app using:
Spring 3
Hibernate 3
MySQL
I'm relying on netbeans to build the project(in contrast to others using maven). On deployment, the console shows this error:
...noClassDefFoundError: com/mchange/v2/c3p0/DataSources
I've already added the jar file to the Hibernate library.
(And oh, this is my first time asking here. Needed 10 points to post the screenshot.)
So I'm confused why would it need THAT class. (whatever that class does.)
Ideas why did this happen?
I've finally manage to solve the problem. The c3p0 distribution has 3 .jar files on the lib directory. I initially added the "c3p0*.jar" only. Which in turn produces the error.
It needs the OTHER jar file, mchange-commons*.jar in the directory. Hope this helps to others stuck in here.
Download this jar mchange-commons-java-0.2.3.4.jar. This helps me to resolve the issue.
C3P0 is used to support connection pooling. See http://www.mchange.com/projects/c3p0/ for further information on C3P0 and https://community.jboss.org/wiki/HowToConfigureTheC3P0ConnectionPool for information on configuring C3P0 with Hibernate.
Add this jar file "c3p0-0.9.2.1.jar" to library
If you are still getting the error, you need to remove and add again Hibernate library because this "c3p0-0.9.2.1.jar" is conflict version with c3p0 in Hibernate library