root
/
spring-boot
mirror of https://github.com/spring-projects/spring-boot.git
1
0
Fork 0
Code Issues Actions 12 Packages Projects Releases Wiki Activity
spring-boot/spring-boot-autoconfigure/src/main/resources/META-INF/spring.factories

52 lines
3.5 KiB
Plaintext
Raw Normal View History

Fix package tangle with AutoConfigurationReport Rename AutoConfigurationReport to ConditionEvaluationReport and co-locate with conditions.
2014-02-04 09:21:00 +08:00
# Initializers
org.springframework.context.ApplicationContextInitializer=\
org.springframework.boot.autoconfigure.logging.AutoConfigurationReportLoggingInitializer
Change package names zero->boot * actuator -> boot-ops * cli -> boot-cli * launcher -> boot-load * autoconfig -> boot-config * bootstrap -> boot-strap * starters -> boot-up [#54095231] [bs-253] Refactor Zero->Boot
2013-07-26 18:50:02 +08:00
# Auto Configure
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.EnableAutoConfiguration=\
Add AopAutoConfiguration (also starter and sample) A side effect is that spring-boot-starter-data-jpa needs to include an aspectjweaver depdendency. Hope that doesn't hurt anything else. [Fixes #56780004]
2013-09-11 20:14:49 +08:00
org.springframework.boot.autoconfigure.aop.AopAutoConfiguration,\
Add renamed Rabbit config to factories
2013-10-24 23:27:00 +08:00
org.springframework.boot.autoconfigure.amqp.RabbitAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.MessageSourceAutoConfiguration,\
org.springframework.boot.autoconfigure.PropertyPlaceholderAutoConfiguration,\
org.springframework.boot.autoconfigure.batch.BatchAutoConfiguration,\
org.springframework.boot.autoconfigure.data.JpaRepositoriesAutoConfiguration,\
Add Mongo auto configuration Spring Data Mongo is the only dependency so it doesn't really need a new starter. Added a sample though.
2013-09-11 22:48:59 +08:00
org.springframework.boot.autoconfigure.data.MongoRepositoriesAutoConfiguration,\
Add RepositoryRestMvcAutoConfiguration Fixes gh-626
2014-04-03 23:35:27 +08:00
org.springframework.boot.autoconfigure.data.rest.RepositoryRestMvcAutoConfiguration,\
Add FreeMarker support This commit adds auto-configuration and a starter, spring-boot-starter-freemarker, for using FreeMarker view templates in a web application. A new abstraction, TemplateAvailabilityProvider, has been introduced. This decouples ErrorMvcAutoConfiguration from the various view technologies that Spring Boot now supports, allowing it to determine when a custom error template is provided without knowing the details of each view technology. Closes #679
2014-04-30 00:46:55 +08:00
org.springframework.boot.autoconfigure.freemarker.FreeMarkerAutoConfiguration,\
org.springframework.boot.autoconfigure.hateoas.HypermediaAutoConfiguration,\
Upgrade to Spring Integration 4.0 Closes #751
2014-05-01 17:05:57 +08:00
org.springframework.boot.autoconfigure.integration.IntegrationAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration,\
org.springframework.boot.autoconfigure.jdbc.DataSourceTransactionManagerAutoConfiguration,\
Revisit JMS support Since ActiveMQ 5.8.0, the modules structure has been revisited and activemq-core no longer exists. The activemq-broker is required to create an embedded broker. Since Boot creates such broker by default if ConnectionFactory is present, a condition has been added to do so only when the necessary classes are present in the classpath. The default embedded broker is now configured to disable message persistence altogether as this requires an extra jar since 5.8.0, i.e. activemq-kahadb-store. Split the ActiveMQ auto configuration from the JmsTemplate auto configuration so these are totally independent. ActiveMQAutoConfiguration has been created to detect and configure the ActiveMQ broker if necessary. The brokerUrl parameter was ignored as long as the inMemory parameter was true. The actual brokerUrl to use is now determined by the user defined values of those parameters: if the brokerUrl is set, it is always used. If no brokerUrl is set, the value of inMemory determines if an embedded broker should be used (true) or a tcp connection to an existing local broker (false). JmsTemplateAutoConfiguration now creates a JmsTemplate only if a ConnectionFactory is available. Fixes gh-872, gh-882, gh-883
2014-05-15 22:18:16 +08:00
org.springframework.boot.autoconfigure.jms.ActiveMQAutoConfiguration,\
[BS-48] Add autoconfigured JMS support * Add ability to detect spring-jms on the path and create a JmsTemplate with ActiveMQConnectionFactory * Create tests showing autoconfigured JmsTemplate with ActiveMQ, but prove it backs off if a separate ConnectionFactory exists. * Add support to spring-boot-cli to that it detects JmsTemplate, DefaultMessageListenerContainer, or SimpleMessageListenerContainer, and turns on autoconfiguration as well as add proper @Grab's and import statements. * Write a jms.groovy test showing proper CLI support Simplify ActiveMQ configuration Update ActiveMQ to 5.7.0
2013-09-16 23:11:56 +08:00
org.springframework.boot.autoconfigure.jms.JmsTemplateAutoConfiguration,\
Auto configuration support for JMX export
2013-12-12 04:30:56 +08:00
org.springframework.boot.autoconfigure.jmx.JmxAutoConfiguration,\
Add autoconfig support for Flyway migrations Flyway starts up with its default settings if it is on the classpath. You can also ask Boot to barf if the migration scripts are missing. Fixes gh-730
2014-05-02 02:37:25 +08:00
org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration,\
Add GroovyTemplates to autconfig
2014-05-16 01:42:44 +08:00
org.springframework.boot.autoconfigure.groovy.template.GroovyTemplateAutoConfiguration,\
Added liquibase autoconfiguration for database migrations If Liquibase is on the classpath it will fire up on startup. Various config options are available (as well as the option to disable it). Liquibase uses a YAML format for changes (in classpath:db/changelog).
2014-04-18 05:59:36 +08:00
org.springframework.boot.autoconfigure.liquibase.LiquibaseAutoConfiguration,\
Add Spring Mobile Device Resolver autoconfiguration
2013-09-26 22:26:45 +08:00
org.springframework.boot.autoconfigure.mobile.DeviceResolverAutoConfiguration,\
Extract Mongo auto-configuration from Spring Data Extract Mongo auto-configuration classes from Spring Data specific auto-configuration, allowing Mongo to be used without Spring Data if require.
2014-02-06 09:52:25 +08:00
org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration,\
Rename MongoTemplateAutoConfiguration Rename MongoTemplateAutoConfiguration to MongoDataAutoConfiguration since it now configures more than just the template.
2014-04-25 22:49:34 +08:00
org.springframework.boot.autoconfigure.mongo.MongoDataAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.orm.jpa.HibernateJpaAutoConfiguration,\
org.springframework.boot.autoconfigure.reactor.ReactorAutoConfiguration,\
Add FreeMarker support This commit adds auto-configuration and a starter, spring-boot-starter-freemarker, for using FreeMarker view templates in a web application. A new abstraction, TemplateAvailabilityProvider, has been introduced. This decouples ErrorMvcAutoConfiguration from the various view technologies that Spring Boot now supports, allowing it to determine when a custom error template is provided without knowing the details of each view technology. Closes #679
2014-04-30 00:46:55 +08:00
org.springframework.boot.autoconfigure.redis.RedisAutoConfiguration,\
Extract actuator security into separate classes So spring-security + a web app is secure by default (you don't need the actuator).
2013-11-21 01:54:59 +08:00
org.springframework.boot.autoconfigure.security.SecurityAutoConfiguration,\
Re-order security auto configuration so the fallback can be applied The management security autoconfiguration wanted to come last in the chain but that won't suit the fallback that was already in place for gh-568. This change re-orders the autoconfig so that @EnableWebSecurity is still added if the user sets security.basic.enabled=false and includes the actuator endpoints. Fixes gh-568
2014-03-26 01:03:10 +08:00
org.springframework.boot.autoconfigure.security.FallbackWebSecurityAutoConfiguration,\
Add support for using Velocity templates
2014-05-08 00:34:24 +08:00
org.springframework.boot.autoconfigure.velocity.VelocityAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.thymeleaf.ThymeleafAutoConfiguration,\
org.springframework.boot.autoconfigure.web.EmbeddedServletContainerAutoConfiguration,\
Extract DispatcherServletAutoConfiguration so it can be used independently
2013-09-19 17:27:54 +08:00
org.springframework.boot.autoconfigure.web.DispatcherServletAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.web.ServerPropertiesAutoConfiguration,\
org.springframework.boot.autoconfigure.web.MultipartAutoConfiguration,\
Split MessageConverters auto config out into separate class
2013-12-16 23:28:26 +08:00
org.springframework.boot.autoconfigure.web.HttpMessageConvertersAutoConfiguration,\
Add WebSocketAutoConfiguration Opinionated defaults for WebSockets: * If spring-websocket is on the classpath and so is the Tomcat WSci initializer then it is added to the context * A DefaultSockJsService is added if none is present * User has only to define @Beans of type WebSocketHandler with name starting "/" * Each one is converted to a SockJsHttpRequestHandler and mapped to "/<beanName>/**"
2013-08-21 22:40:47 +08:00
org.springframework.boot.autoconfigure.web.WebMvcAutoConfiguration,\
Move ErrorController to autoconfig
2014-04-28 17:26:54 +08:00
org.springframework.boot.autoconfigure.web.ErrorMvcAutoConfiguration,\
Add WebSocketAutoConfiguration Opinionated defaults for WebSockets: * If spring-websocket is on the classpath and so is the Tomcat WSci initializer then it is added to the context * A DefaultSockJsService is added if none is present * User has only to define @Beans of type WebSocketHandler with name starting "/" * Each one is converted to a SockJsHttpRequestHandler and mapped to "/<beanName>/**"
2013-08-21 22:40:47 +08:00
org.springframework.boot.autoconfigure.websocket.WebSocketAutoConfiguration
Add FreeMarker support This commit adds auto-configuration and a starter, spring-boot-starter-freemarker, for using FreeMarker view templates in a web application. A new abstraction, TemplateAvailabilityProvider, has been introduced. This decouples ErrorMvcAutoConfiguration from the various view technologies that Spring Boot now supports, allowing it to determine when a custom error template is provided without knowing the details of each view technology. Closes #679
2014-04-30 00:46:55 +08:00
# Template availability providers
Move TemplateAvailabilityProvider Move TemplateAvailabilityProvider from the spring-boot project to spring-boot-autoconfigure
2014-05-01 04:38:17 +08:00
org.springframework.boot.autoconfigure.template.TemplateAvailabilityProvider=\
Add FreeMarker support This commit adds auto-configuration and a starter, spring-boot-starter-freemarker, for using FreeMarker view templates in a web application. A new abstraction, TemplateAvailabilityProvider, has been introduced. This decouples ErrorMvcAutoConfiguration from the various view technologies that Spring Boot now supports, allowing it to determine when a custom error template is provided without knowing the details of each view technology. Closes #679
2014-04-30 00:46:55 +08:00
org.springframework.boot.autoconfigure.freemarker.FreeMarkerTemplateAvailabilityProvider,\
Relax requirement for groovy template directory to exist Since groovy-templates is included with groovy-all it is unreasonable to expect anyone who has it on their classpath to have resolvable templates. We may need to revisit this decision, but since the origain feature that drove this was thymeleaf and idaiotic users having it on their classpath but not using it, maybe we don't need to.
2014-05-16 05:12:27 +08:00
org.springframework.boot.autoconfigure.groovy.template.GroovyTemplateAvailabilityProvider,\
Add FreeMarker support This commit adds auto-configuration and a starter, spring-boot-starter-freemarker, for using FreeMarker view templates in a web application. A new abstraction, TemplateAvailabilityProvider, has been introduced. This decouples ErrorMvcAutoConfiguration from the various view technologies that Spring Boot now supports, allowing it to determine when a custom error template is provided without knowing the details of each view technology. Closes #679
2014-04-30 00:46:55 +08:00
org.springframework.boot.autoconfigure.thymeleaf.ThymeleafTemplateAvailabilityProvider,\
Add support for using Velocity templates
2014-05-08 00:34:24 +08:00
org.springframework.boot.autoconfigure.velocity.VelocityTemplateAvailabilityProvider,\
Add FreeMarker support This commit adds auto-configuration and a starter, spring-boot-starter-freemarker, for using FreeMarker view templates in a web application. A new abstraction, TemplateAvailabilityProvider, has been introduced. This decouples ErrorMvcAutoConfiguration from the various view technologies that Spring Boot now supports, allowing it to determine when a custom error template is provided without knowing the details of each view technology. Closes #679
2014-04-30 00:46:55 +08:00
org.springframework.boot.autoconfigure.web.JspTemplateAvailabilityProvider