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

146 lines
11 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=\
Share MetadataReaderFactory Add SharedMetadataReaderFactoryContextInitializer to ensure that a shared caching MetadataReaderFactory is used between configuration classes and auto-configure sorting. Fixes gh-4993
2016-01-25 02:41:03 +08:00
org.springframework.boot.autoconfigure.SharedMetadataReaderFactoryContextInitializer,\
Rename AutoConfigurationReportLoggingInitializer to ConditionEvaluationReportLoggingListener Closes gh-2945
2017-11-10 23:20:13 +08:00
org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener
Fix package tangle with AutoConfigurationReport Rename AutoConfigurationReport to ConditionEvaluationReport and co-locate with conditions.
2014-02-04 09:21:00 +08:00
Improve performance with BackgroundPreinitializer Add a BackgroundPreinitializer to trigger early initialization in a background thread of time consuming tasks. By moving certain initialization tasks to background thread and triggering them early we can improve the critical path when the application starts. For example, Tomcat's MBeanFactory class parses several XML files when first loaded. If we trigger the load in a background thread it completes before Tomcat actually needs to use it. The initial set of initializers included with this commit are: - Tomcat MBeanFactory - javax.validation - Spring's AllEncompassingFormHttpMessageConverter See gh-4252
2015-11-05 15:12:26 +08:00
# Application Listeners
org.springframework.context.ApplicationListener=\
org.springframework.boot.autoconfigure.BackgroundPreinitializer
Remove dependency from `root` to `condition` Remove the slightly unusual dependency from the root autoconfigure pacakge to `condition`. Prior to this commit the link was required in ordere to populate the `ConditionEvaluationReport`. We now introduce a `AutoConfigurationImportListener` strategy that allows anyone to listen for AutoConfigurationImportEvents. The listener implementation is now used to update the ConditionEvaluationReport. Fixes gh-8073
2017-01-23 13:31:07 +08:00
# Auto Configuration Import Listeners
org.springframework.boot.autoconfigure.AutoConfigurationImportListener=\
org.springframework.boot.autoconfigure.condition.ConditionEvaluationReportAutoConfigurationImportListener
Make OnClassCondition an AutoConfigurationImportFilter Update OnClassCondition to implement AutoConfigurationImportFilter so that auto-configuration candidates can be filtered early. The optimization helps to improve application startup time by reducing the number of classes that are loaded. See gh-7573
2017-01-23 15:14:23 +08:00
# Auto Configuration Import Filters
org.springframework.boot.autoconfigure.AutoConfigurationImportFilter=\
org.springframework.boot.autoconfigure.condition.OnClassCondition
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=\
Rename SpringApplicationLifecycle => Admin Rename SpringApplicationLifecycle JMX beans to SpringApplicationAdmin and relocate to a dedicated package. Fixes gh-3124
2015-06-10 07:06:28 +08:00
org.springframework.boot.autoconfigure.admin.SpringApplicationAdminJmxAutoConfiguration,\
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.batch.BatchAutoConfiguration,\
Add cache manager auto-configuration Add support for cache manager auto-configuration that is triggered when the `EnableCaching` annotation is added to a Spring Boot application. A new "spring.cache" set of configuration keys is also provided. The "spring.cache.mode" allows the user to specify the cache provider that should be auto-configured. If no explicit configuration is provided, the environment is checked for the best suited cache implementation, that is: - Generic if at least one `Cache` bean is defined in the context. - Hazelcast if either a default configuration file is present or the `spring.cache.config` property is set. - JCache if one JSR-107 provider is present - Redis if a `RedisTemplate` is defined in the context - Guava - Simple as a fallback option, using concurrent maps - NoOp (that is, no cache) if the mode is set to "none" If the provider supports it, it is possible to specify the caches to create on startup via `spring.cache.cache-names`. If the provider relies on a configuration file and a custom one needs to be used `spring.cache.config` can be set to such custom resource. If more than one JSR-107 provider is present, it is possible to force the provider to use by setting the mode to `jcache` and specifying the fully qualified class name of the CachingProvider to use via `spring.cache.jcache.provider`. See gh-2633
2015-03-17 23:21:23 +08:00
org.springframework.boot.autoconfigure.cache.CacheAutoConfiguration,\
Add Cassandra support Add auto-configuration support and health checks for Cassandra and Spring Data Cassandra. Fixes gh-2064 Closes gh-2214
2014-12-22 18:06:37 +08:00
org.springframework.boot.autoconfigure.cassandra.CassandraAutoConfiguration,\
Add auto-configuration for Spring Cloud Enable if all of the following are true: - spring-cloud is on the classpath - There is no Cloud bean present (usually done by extending AbstractCloudConfig) - The "cloud" profile is active Fixes gh-1302 Autoconfigure spring-cloud
2014-08-01 02:34:10 +08:00
org.springframework.boot.autoconfigure.cloud.CloudAutoConfiguration,\
Auto-configure @EnableConfigurationProperties Add an auto-configuration that avoid a Spring Boot user to add `@EnableConfigurationProperties` to its configuration to benefit from that feature. As our own auto-configurations are tested independently, such annotation is still present to avoid a useless reference to this new auto-configuration. Closes gh-2457
2015-08-04 19:59:57 +08:00
org.springframework.boot.autoconfigure.context.ConfigurationPropertiesAutoConfiguration,\
Relocate AutoConfigurations from root package Move PropertyPlaceholder and MessageSource auto-configuration from the root package to the `context` subpackage. Fixes gh-8071
2017-01-20 06:00:40 +08:00
org.springframework.boot.autoconfigure.context.MessageSourceAutoConfiguration,\
org.springframework.boot.autoconfigure.context.PropertyPlaceholderAutoConfiguration,\
Add Couchbase support Closes gh-3498
2015-07-30 15:49:50 +08:00
org.springframework.boot.autoconfigure.couchbase.CouchbaseAutoConfiguration,\
Provide auto-configuration of persistence exception translation Closes gh-1435
2014-10-09 23:02:10 +08:00
org.springframework.boot.autoconfigure.dao.PersistenceExceptionTranslationAutoConfiguration,\
Add Cassandra support Add auto-configuration support and health checks for Cassandra and Spring Data Cassandra. Fixes gh-2064 Closes gh-2214
2014-12-22 18:06:37 +08:00
org.springframework.boot.autoconfigure.data.cassandra.CassandraDataAutoConfiguration,\
Harmonize reactive auto-configuration class names Closes gh-9086
2017-05-04 16:19:10 +08:00
org.springframework.boot.autoconfigure.data.cassandra.CassandraReactiveDataAutoConfiguration,\
org.springframework.boot.autoconfigure.data.cassandra.CassandraReactiveRepositoriesAutoConfiguration,\
Add Cassandra support Add auto-configuration support and health checks for Cassandra and Spring Data Cassandra. Fixes gh-2064 Closes gh-2214
2014-12-22 18:06:37 +08:00
org.springframework.boot.autoconfigure.data.cassandra.CassandraRepositoriesAutoConfiguration,\
Separate Couchbase setup from Spring Data This commit separates the basic setup of Couchbase from Spring Data so that a `Bucket` and `Cluster` bucket beans are exposed even if Spring Data is not available. A basic setup happens if `spring.couchbase.bootstrap-hosts` is specified, configuring the `default` bucket with no authentication unless specified otherwise. If Spring Data is available, those beans are re-used by default to configure the `CouchbaseTemplate` and other repository-related beans. Closes gh-5347
2016-03-07 20:02:43 +08:00
org.springframework.boot.autoconfigure.data.couchbase.CouchbaseDataAutoConfiguration,\
Add support for reactive Spring Data Couchbase See gh-10812
2017-10-29 22:47:06 +08:00
org.springframework.boot.autoconfigure.data.couchbase.CouchbaseReactiveDataAutoConfiguration,\
org.springframework.boot.autoconfigure.data.couchbase.CouchbaseReactiveRepositoriesAutoConfiguration,\
Add Couchbase support Closes gh-3498
2015-07-30 15:49:50 +08:00
org.springframework.boot.autoconfigure.data.couchbase.CouchbaseRepositoriesAutoConfiguration,\
Rationalize Spring Data auto-configurations Relocate several auto-configuration classes to `...autoconfigure.data` to make it clearer that they are Spring Data specific. Also moved `EntityManagerFactoryBuilder` to `spring-boot` since it is generally useful and doesn't need to be directly tied to the auto-configuration module. Fixes gh-4002
2015-09-22 07:30:05 +08:00
org.springframework.boot.autoconfigure.data.elasticsearch.ElasticsearchAutoConfiguration,\
org.springframework.boot.autoconfigure.data.elasticsearch.ElasticsearchDataAutoConfiguration,\
Introduce subpackages for Spring Data autoconfig (If we ever want to modularize this will make it less painful) Fixes gh-1015
2014-06-03 16:14:47 +08:00
org.springframework.boot.autoconfigure.data.elasticsearch.ElasticsearchRepositoriesAutoConfiguration,\
org.springframework.boot.autoconfigure.data.jpa.JpaRepositoriesAutoConfiguration,\
Add LDAP auto-configuration support Add auto-configuration support for spring-ldap and spring-data-ldap. See gh-2645 See gh-7733
2016-05-18 20:49:34 +08:00
org.springframework.boot.autoconfigure.data.ldap.LdapRepositoriesAutoConfiguration,\
Rationalize Spring Data auto-configurations Relocate several auto-configuration classes to `...autoconfigure.data` to make it clearer that they are Spring Data specific. Also moved `EntityManagerFactoryBuilder` to `spring-boot` since it is generally useful and doesn't need to be directly tied to the auto-configuration module. Fixes gh-4002
2015-09-22 07:30:05 +08:00
org.springframework.boot.autoconfigure.data.mongo.MongoDataAutoConfiguration,\
Harmonize reactive auto-configuration class names Closes gh-9086
2017-05-04 16:19:10 +08:00
org.springframework.boot.autoconfigure.data.mongo.MongoReactiveDataAutoConfiguration,\
org.springframework.boot.autoconfigure.data.mongo.MongoReactiveRepositoriesAutoConfiguration,\
Introduce subpackages for Spring Data autoconfig (If we ever want to modularize this will make it less painful) Fixes gh-1015
2014-06-03 16:14:47 +08:00
org.springframework.boot.autoconfigure.data.mongo.MongoRepositoriesAutoConfiguration,\
Relocate Neo4J auto-configuration Move Neo4J auto-configuration from `autoconfigure.neo4j` to `autoconfigure.data.neo4j` since it's intrinsically linked to Spring Data. See gh-5458 See gh-6142
2016-06-25 02:15:55 +08:00
org.springframework.boot.autoconfigure.data.neo4j.Neo4jDataAutoConfiguration,\
Add Neo4j support See gh-5458
2015-09-02 14:57:37 +08:00
org.springframework.boot.autoconfigure.data.neo4j.Neo4jRepositoriesAutoConfiguration,\
Introduce subpackages for Spring Data autoconfig (If we ever want to modularize this will make it less painful) Fixes gh-1015
2014-06-03 16:14:47 +08:00
org.springframework.boot.autoconfigure.data.solr.SolrRepositoriesAutoConfiguration,\
Rationalize Spring Data auto-configurations Relocate several auto-configuration classes to `...autoconfigure.data` to make it clearer that they are Spring Data specific. Also moved `EntityManagerFactoryBuilder` to `spring-boot` since it is generally useful and doesn't need to be directly tied to the auto-configuration module. Fixes gh-4002
2015-09-22 07:30:05 +08:00
org.springframework.boot.autoconfigure.data.redis.RedisAutoConfiguration,\
Add auto-configuration for reactive Redis This commit provides an auto-configuration for reactive Redis and a starter that provides Lettuce as Jedis doesn't support reactive operations. There are no support for reactive redis repositories at the moment so only a `ReactiveRedisTemplate` is auto-configured if necessary. Closes gh-8053
2017-05-04 15:25:36 +08:00
org.springframework.boot.autoconfigure.data.redis.RedisReactiveAutoConfiguration,\
Auto-configure Redis repositories Closes gh-5448
2016-03-20 20:34:37 +08:00
org.springframework.boot.autoconfigure.data.redis.RedisRepositoriesAutoConfiguration,\
Add RepositoryRestMvcAutoConfiguration Fixes gh-626
2014-04-03 23:35:27 +08:00
org.springframework.boot.autoconfigure.data.rest.RepositoryRestMvcAutoConfiguration,\
Separate out the auto-configuration of Spring Data’s web support Previously, Spring Data’s web support was auto-configured as part of the JPA repositories auto-configuration. However, Spring Data’s web support isn’t dependent on the use of Spring Data JPA or even repositories. This commit moves the auto-configuration into a standalone class, making it independent of the use of Spring Data JPA and Spring Data repositories. Closes gh-1097
2014-10-13 21:55:02 +08:00
org.springframework.boot.autoconfigure.data.web.SpringDataWebAutoConfiguration,\
Refactor Jest auto-configuration package space This commit moves the Jest auto-configuration from `spring.jest` to `spring.elasticsearch.jest` Closes gh-6032
2016-06-23 16:39:16 +08:00
org.springframework.boot.autoconfigure.elasticsearch.jest.JestAutoConfiguration,\
Auto-configure Elasticsearch REST clients This commit adds auto-configuration support for both `RestClient` and `RestHighLevelClient` which are provided by `elasticsearch-rest-client` and `elasticsearch-rest-high-level-client` dependencies respectively. `RestClient` is associated with configuration properties in the `spring.elasticsearch.rest.*` namespace, since this is the component taking care of HTTP communication with the actual Elasticsearch node. `RestHighLevelClient` wraps the first one and naturally inherits that configuration. Closes gh-12600
2018-05-07 23:57:09 +08:00
org.springframework.boot.autoconfigure.elasticsearch.rest.RestClientAutoConfiguration,\
Restructure web auto-configuration Restructure `org.springframework.boot.autoconfigure.web` to better align with the new package structure in `spring-boot`. Auto-configuration is now split into client, servlet and reactive sub-packages. In addition a new `http` package now handles common HTTP concerns. Fixes gh-8616
2017-03-15 09:06:53 +08:00
org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration,\
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,\
Turn (Jackson|Gson)AutoConfiguration into true auto-configuration Previously JacksonAutoConfiguration and GsonAutoConfiguration were not actually auto-configuration classes. They were only processed due to being imported by HttpMessageConvertersAutoConfiguration. In addition to being misleadingly named, this meant that they could not be included or excluded individually and were also tightly coupled to HTTP message conversion. This commit updates spring.factories to make both JacksonAutoConfiguration and GsonAutoConfiguration actual auto-configuration classes. As a result, they can now be enabled or disabled individually and are no longer coupled to HTTP message conversion. Closes gh-1562
2014-10-02 17:27:21 +08:00
org.springframework.boot.autoconfigure.gson.GsonAutoConfiguration,\
Add auto-configuration for H2’s web console Three conditions must be met for the console to be enabled: - H2 is on the classpath - The application is a web application - spring.h2.console.enabled is set to true If spring-boot-devtools is on the classpath, spring.h2.console.enabled will be set to true automatically. Without the dev tools, the enabled property will have to be set to true in application.properties. By default, the console is available at /h2-console. This can be configured via the spring.h2.console.path property. The value of this property must begin with a '/'. When Spring Security is on the classpath the console will be secured based on the user's security.* configuration. When the console is secured, CSRF protection is disabled and frame options is set to SAMEORIGIN for its path. Both settings are required in order for the console to function. Closes gh-766
2015-08-04 18:33:16 +08:00
org.springframework.boot.autoconfigure.h2.H2ConsoleAutoConfiguration,\
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.hateoas.HypermediaAutoConfiguration,\
Hazelcast auto-configuration Provide a general purpose Hazelcast integration (i.e. not tied to caching). Auto-configure a `HazelcastInstance` either based on the presence of a `Config` bean or a configuration file. Said configuration file can be specified explicitly or automatically found from default locations. The cache integration already supports Hazelcast so it has been reworked to automatically reuse an existing `HazelcastInstance` if available. Closes gh-2942
2015-08-26 23:44:50 +08:00
org.springframework.boot.autoconfigure.hazelcast.HazelcastAutoConfiguration,\
Register hazelcast post processor only when necessary Commit 8e0a94f introduced a post processor that adds an explicit link between the `HazelcastInstance` and the `EntityManagerFactory` so that Hazelcast is fully initialized before Hibernate actually kicks in. Unfortunately, the conditions that were implemented to register this post processor are wrong and any app that has both JPA and Hazelcast support blows up if no bean with name `hazelcastInstance` is defined. This commit fixes the situation and reworks the configuration in a separate auto-configuration that runs after the Hazelcast and JPA support and check both the presence of an `EntityManagerFactory` and a bean of name `hazelcastInstance`. If any of those conditions does not apply the post processor is no longer registered. Closes gh-4158
2015-11-06 19:01:59 +08:00
org.springframework.boot.autoconfigure.hazelcast.HazelcastJpaDependencyAutoConfiguration,\
Restructure web auto-configuration Restructure `org.springframework.boot.autoconfigure.web` to better align with the new package structure in `spring-boot`. Auto-configuration is now split into client, servlet and reactive sub-packages. In addition a new `http` package now handles common HTTP concerns. Fixes gh-8616
2017-03-15 09:06:53 +08:00
org.springframework.boot.autoconfigure.http.HttpMessageConvertersAutoConfiguration,\
Apply codecs auto-configuration to WebFlux This commit introduces `CodecCustomizer`, a new callback-based interface for customizing the codecs configuration for WebFlux server and client. Instances of those customizers are applied to the `WebClient.Builder` and to the `WebFluxAutoConfiguration` (which deals with both WebFlux and WebFlux.fn). For now, only Jackson codecs are auto-configured, by getting the `ObjectMapper` instance created by Spring Boot. Other codecs can be configured as soon as WebFlux supports those. Closes gh-9166
2017-06-20 20:56:18 +08:00
org.springframework.boot.autoconfigure.http.codec.CodecsAutoConfiguration,\
Polish "Add influxDB java client auto-configuration" Closes gh-9066
2017-06-02 16:45:24 +08:00
org.springframework.boot.autoconfigure.influx.InfluxDbAutoConfiguration,\
Missing entry for ProjectInfoAutoConfiguration
2016-03-04 20:26:15 +08:00
org.springframework.boot.autoconfigure.info.ProjectInfoAutoConfiguration,\
Upgrade to Spring Integration 4.0 Closes #751
2014-05-01 17:05:57 +08:00
org.springframework.boot.autoconfigure.integration.IntegrationAutoConfiguration,\
Turn (Jackson|Gson)AutoConfiguration into true auto-configuration Previously JacksonAutoConfiguration and GsonAutoConfiguration were not actually auto-configuration classes. They were only processed due to being imported by HttpMessageConvertersAutoConfiguration. In addition to being misleadingly named, this meant that they could not be included or excluded individually and were also tightly coupled to HTTP message conversion. This commit updates spring.factories to make both JacksonAutoConfiguration and GsonAutoConfiguration actual auto-configuration classes. As a result, they can now be enabled or disabled individually and are no longer coupled to HTTP message conversion. Closes gh-1562
2014-10-02 17:27:21 +08:00
org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration,\
Add JdbcTemplate only on single DataSource Update auto-configuration logic so that a `JdbcTemplate` is only added when there is a single candidate DataSource bean. Closes gh-6449
2016-07-26 07:55:07 +08:00
org.springframework.boot.autoconfigure.jdbc.JdbcTemplateAutoConfiguration,\
Add property for JNDI DataSource lookup Add `spring.datasource.jndi-name` property to allow a DataSource to be looked up from JNDI as an alternative to defining a URL connection. Fixes gh-989
2014-08-27 02:33:09 +08:00
org.springframework.boot.autoconfigure.jdbc.JndiDataSourceAutoConfiguration,\
Update DataSource auto-configuration to support XA Update DataSource and JPA auto-configuration to consider XA datasources. See gh-947
2014-08-23 03:10:58 +08:00
org.springframework.boot.autoconfigure.jdbc.XADataSourceAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.jdbc.DataSourceTransactionManagerAutoConfiguration,\
Polish
2014-05-30 07:31:11 +08:00
org.springframework.boot.autoconfigure.jms.JmsAutoConfiguration,\
Auto configuration support for JMX export
2013-12-12 04:30:56 +08:00
org.springframework.boot.autoconfigure.jmx.JmxAutoConfiguration,\
Support JNDI for JTA and JMS. Update auto-configuration for JMS and JTA to support a ConnectionFactory and TransactionManager exposed via JNDI. JTA configuration now attempts a simple JtaTransactionManager before attempting Bitronix or Atomikos configuration. The JMS auto-configuration also now attempts to find a ConnectionFactory from JNDI before falling back to the previous strategies. If JNDI is present a JndiDestinationResolver is also configured instead of the default DestinationResolver. See gh-947
2014-08-26 04:12:52 +08:00
org.springframework.boot.autoconfigure.jms.JndiConnectionFactoryAutoConfiguration,\
Create JMS sub-packages Reorganize the `jms` package into `hornetq` and `activemq` sub-pacakges. Fixes gh-1005
2014-06-01 20:49:41 +08:00
org.springframework.boot.autoconfigure.jms.activemq.ActiveMQAutoConfiguration,\
Add Apache Artemis support Add auto-configuration support for Apache Artemis which was formed when HornetQ was donated to the Apache Foundation. The majority of this code is based on the HornetQ auto-configuration. Fixes gh-3154 Closes gh-3246
2015-06-15 00:12:32 +08:00
org.springframework.boot.autoconfigure.jms.artemis.ArtemisAutoConfiguration,\
Add GroovyTemplates to autconfig
2014-05-16 01:42:44 +08:00
org.springframework.boot.autoconfigure.groovy.template.GroovyTemplateAutoConfiguration,\
Add autoconfig support for Jersey (2) Jersey 2 has some Spring support built in but it's a bit awkward to use in a Boot app, so autoconfiguration seems appropriate. The tests and sample show how to use it, but the short story is that any @Component can define JAX-RS endpoints via @GET etc. There's a sample for Jersey 1 as well (pay careful attention to the plugin configuration if you want to build an executable jar) Fixes gh-1651
2014-10-02 17:32:55 +08:00
org.springframework.boot.autoconfigure.jersey.JerseyAutoConfiguration,\
Add support for jOOQ Add auto-configuration and a starter POM for jOOQ. See gh-2804
2015-04-11 22:17:30 +08:00
org.springframework.boot.autoconfigure.jooq.JooqAutoConfiguration,\
Add Jsonb support Spring Framework 5 will support Jsonb as a HttpMessageConverter, this commit adds auto-configuration support. Also, support for Jsonb in the @JsonTest has been added. This implementation is running against Apache Johnzon See gh-9648
2017-04-11 10:01:13 +08:00
org.springframework.boot.autoconfigure.jsonb.JsonbAutoConfiguration,\
Add Apache Kafka support See gh-6961
2016-03-29 03:48:50 +08:00
org.springframework.boot.autoconfigure.kafka.KafkaAutoConfiguration,\
Add LDAP auto-configuration support Add auto-configuration support for spring-ldap and spring-data-ldap. See gh-2645 See gh-7733
2016-05-18 20:49:34 +08:00
org.springframework.boot.autoconfigure.ldap.embedded.EmbeddedLdapAutoConfiguration,\
org.springframework.boot.autoconfigure.ldap.LdapAutoConfiguration,\
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 email support This commit adds a new starter to auto-configure a MailSender when the necessary classes are present and when the property "spring.mail.host" is set. The auto-configuration also accepts any arbitrary properties that JavaMail might need using the "spring.mail.properties" prefix. Fixes gh-1760
2014-10-29 22:25:39 +08:00
org.springframework.boot.autoconfigure.mail.MailSenderAutoConfiguration,\
Fix ordering of mail auto-configuration It is not possible to put `@Order` on nested `@Configuration` classes and there is no ordering guarantee of them anyway. Previously, we relied on the declaration order to check if the `test-connection` flag should apply to an existing `JavaMailSenderImpl`. It turns out at the `JavaMailSenderImpl` bean was not created at that time and so the evaluation was wrongly failing. To make that more explicit, that code is now in its own auto-configuration with an explicit `@AutoConfigureAfter` declaration. Since the JNDI support could be affected by the exact same issue, it has been restored to its own package private configuration class that is processed before the `MailSenderAutoConfiguration` content is evaluated. Closes gh-3478
2015-07-14 17:23:49 +08:00
org.springframework.boot.autoconfigure.mail.MailSenderValidatorAutoConfiguration,\
Flesh out and polish Embedded MongoDB auto-configuration contribution Embedded MongoDB is now auto-configured when it is on the classpath. The Mongo instance will listen on the port specified by the spring.data.mongodb.port property. If this property has a value of zero and randomly allocated port will be used. In such an event, the MongoClient created by MongoAutoConfiguration will be automatically configured to use the port that was allocated. By default, MongoDB 2.6.10 will be used. This can be configured using the spring.embedded-mongodb.version property. Mongo's sync delay feature is enabled by default. This can be configured using the spring.embedded-mongobd.features property. Closes gh-2002
2014-11-26 19:40:31 +08:00
org.springframework.boot.autoconfigure.mongo.embedded.EmbeddedMongoAutoConfiguration,\
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,\
Harmonize reactive auto-configuration class names Closes gh-9086
2017-05-04 16:19:10 +08:00
org.springframework.boot.autoconfigure.mongo.MongoReactiveAutoConfiguration,\
Add jmustache support The package names changed a bit from the prototype project, but wuth vanilla autconfiguration usage that shouldn't matter. Follows closely the Groovy templates support. Templates live in classpath:/templates/*.html by default. Fixes gh-2242
2015-01-09 21:50:39 +08:00
org.springframework.boot.autoconfigure.mustache.MustacheAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.orm.jpa.HibernateJpaAutoConfiguration,\
Add Quartz Scheduler support See gh-4299
2015-10-26 08:29:56 +08:00
org.springframework.boot.autoconfigure.quartz.QuartzAutoConfiguration,\
Provide Reactor 3 auto-configuration This commit provides auto-configuration for the Reactor Core 3 library. A new configuration namespace, "spring.reactor" allows to configure hooks on operators, like "spring.reactor.stacktrace-mode.enabled". This property is enabled automatically by devtools, since it improves the developer experience and provides full stacktrace information when exceptions occur (but at a performance cost). Fixes gh-7302
2017-01-21 23:07:30 +08:00
org.springframework.boot.autoconfigure.reactor.core.ReactorCoreAutoConfiguration,\
Move servlet specific security auto-config
2018-01-17 19:42:58 +08:00
org.springframework.boot.autoconfigure.security.servlet.SecurityAutoConfiguration,\
Refactor Spring Security auto-configuration classes The auto-configuration for a `UserDetailsService` and the web bits has been split into two. Closes gh-11915 Fixes gh-11891
2018-02-08 08:12:46 +08:00
org.springframework.boot.autoconfigure.security.servlet.UserDetailsServiceAutoConfiguration,\
Move servlet specific security auto-config
2018-01-17 19:42:58 +08:00
org.springframework.boot.autoconfigure.security.servlet.SecurityFilterAutoConfiguration,\
Add auto-config and starter for reactive security Closes gh-9925
2017-09-27 03:40:39 +08:00
org.springframework.boot.autoconfigure.security.reactive.ReactiveSecurityAutoConfiguration,\
Refactor Spring Security auto-configuration classes The auto-configuration for a `UserDetailsService` and the web bits has been split into two. Closes gh-11915 Fixes gh-11891
2018-02-08 08:12:46 +08:00
org.springframework.boot.autoconfigure.security.reactive.ReactiveUserDetailsServiceAutoConfiguration,\
Rationalize some features and merge in customizers from Spring Cloud
2015-05-22 23:32:47 +08:00
org.springframework.boot.autoconfigure.sendgrid.SendGridAutoConfiguration,\
Add auto-configuration support for Spring Session This commit adds support for automatically configuring Spring Session. In a web application when both Spring Session and Spring Data Redis are on the classpath, Spring Session's Redis Http Session support will be auto-configured. The max inactive interval for Redis-backed sessions can be configured via the environment using the existing server.session-timeout property. Closes gh-2318
2015-05-21 00:06:53 +08:00
org.springframework.boot.autoconfigure.session.SessionAutoConfiguration,\
Add auto-config for WebFlux OAuth2 Login Closes gh-13142
2018-05-31 08:58:55 +08:00
org.springframework.boot.autoconfigure.security.oauth2.client.servlet.OAuth2ClientAutoConfiguration,\
org.springframework.boot.autoconfigure.security.oauth2.client.reactive.ReactiveOAuth2ClientAutoConfiguration,\
Add auto configuration support for Spring Data Solr Registers required components in application context if not available to set up environment for usage with Spring Data Solr. Will listen on SolrServer and SolrRepositories for configuration. By default an HttpSolrServer is registered unless a zkHost (zookeeper host) is defined. In that case an instance of CloudSolrServer will be created. By default multicore support is enabled, creating instances of SolrServer for each core defined via @SolrDocument.
2014-04-28 13:45:19 +08:00
org.springframework.boot.autoconfigure.solr.SolrAutoConfiguration,\
Renamed packages Issue: #54095231
2013-07-27 05:10:38 +08:00
org.springframework.boot.autoconfigure.thymeleaf.ThymeleafAutoConfiguration,\
Add TransactionTemplate auto-configuration Provide a TransactionTemplate if one PlatformTransactionManager is present. Relocated the jta support as a nested package of the new transaction package that hosts the transaction template auto-configuration. To avoid package tangles, links between auto-configurations have been reversed. Closes gh-2464 Closes gh-2809
2015-04-09 20:26:23 +08:00
org.springframework.boot.autoconfigure.transaction.TransactionAutoConfiguration,\
org.springframework.boot.autoconfigure.transaction.jta.JtaAutoConfiguration,\
Add ValidationAutoConfiguration to spring.factories Closes gh-7494
2016-11-28 10:50:43 +08:00
org.springframework.boot.autoconfigure.validation.ValidationAutoConfiguration,\
Restructure web auto-configuration Restructure `org.springframework.boot.autoconfigure.web` to better align with the new package structure in `spring-boot`. Auto-configuration is now split into client, servlet and reactive sub-packages. In addition a new `http` package now handles common HTTP concerns. Fixes gh-8616
2017-03-15 09:06:53 +08:00
org.springframework.boot.autoconfigure.web.client.RestTemplateAutoConfiguration,\
Rework common server customization Update the configurable embedded web server factory interfaces to extend `ConfigurableWebServerFactory` so that the can be used in a `WebServerFactoryCustomizer`. Extract server specific customization to their own auto-configuration and align reactive/servlet server auto-configuration. Closes gh-8573
2018-02-20 15:58:58 +08:00
org.springframework.boot.autoconfigure.web.embedded.EmbeddedWebServerFactoryCustomizerAutoConfiguration,\
Restructure web auto-configuration Restructure `org.springframework.boot.autoconfigure.web` to better align with the new package structure in `spring-boot`. Auto-configuration is now split into client, servlet and reactive sub-packages. In addition a new `http` package now handles common HTTP concerns. Fixes gh-8616
2017-03-15 09:06:53 +08:00
org.springframework.boot.autoconfigure.web.reactive.HttpHandlerAutoConfiguration,\
Rename ReactiveWebServerAutoConfiguration Closes gh-12086
2018-02-16 17:44:15 +08:00
org.springframework.boot.autoconfigure.web.reactive.ReactiveWebServerFactoryAutoConfiguration,\
Rename WebFluxAnnotationAutoConfiguration Rename WebFluxAnnotationAutoConfiguration to WebFluxAutoConfiguration to better align with Spring MVC.
2017-04-21 06:58:23 +08:00
org.springframework.boot.autoconfigure.web.reactive.WebFluxAutoConfiguration,\
Support error conventions in Spring WebFlux This commit adds support for Spring Boot error conventions with WebFlux. The Spring MVC support for that is based on an `Controller` that's mapped on a specific `"/error"` path and configured as an error page in the Servlet container. With WebFlux, this support leverages a `WebExceptionHandler`, which catches exceptions flowing through the reactive pipeline and handles them. The `DefaultErrorWebExceptionHandler` supports the following: * return a JSON error response to machine clients * return error HTML views (templates, static or default HTML view) One can customize the error information by contributing an `ErrorAttributes` bean to the application context. Spring Boot provides an `ErrorWebExceptionHandler` marker interface and a base implementation that provides high level constructs to handle errors, based on the Spring WebFlux functional flavor. The error handling logic can be completely changed by providing a custom `RouterFunction` there. Fixes gh-8625
2017-10-17 03:55:05 +08:00
org.springframework.boot.autoconfigure.web.reactive.error.ErrorWebFluxAutoConfiguration,\
Auto-configure WebClient.Builder This commit adds a new customizer interface for applying configuration changes to `WebClient.Builder` beans: `WebClientCustomizer`. The new WebClient auto-configuration will make available, as a prototype scoped bean, `WebClient.Builder` instances. Once injected, developers can use those to create `WebClient` instances to be used in their application. `WebClientCustomizer` beans are sorted according to their `Order` and then applied to the builder instances. Closes gh-9522
2017-06-19 16:03:53 +08:00
org.springframework.boot.autoconfigure.web.reactive.function.client.WebClientAutoConfiguration,\
Restructure web auto-configuration Restructure `org.springframework.boot.autoconfigure.web` to better align with the new package structure in `spring-boot`. Auto-configuration is now split into client, servlet and reactive sub-packages. In addition a new `http` package now handles common HTTP concerns. Fixes gh-8616
2017-03-15 09:06:53 +08:00
org.springframework.boot.autoconfigure.web.servlet.DispatcherServletAutoConfiguration,\
org.springframework.boot.autoconfigure.web.servlet.ServletWebServerFactoryAutoConfiguration,\
org.springframework.boot.autoconfigure.web.servlet.error.ErrorMvcAutoConfiguration,\
org.springframework.boot.autoconfigure.web.servlet.HttpEncodingAutoConfiguration,\
org.springframework.boot.autoconfigure.web.servlet.MultipartAutoConfiguration,\
org.springframework.boot.autoconfigure.web.servlet.WebMvcAutoConfiguration,\
Add reactive websocket auto-configuration for Tomcat This commit adds a `TomcatWebSocketReactiveWebServerCustomizer` that customizes the Tomcat context to accept WebSockets connections. Since reactive servers don't use the JSR 356 for that support, only Tomcat customization is required for now. This commit also reorders the server auto-configuration so that undertow has a chance to be auto-configured before reactor-netty, which should be a popular dependency thanks to its HTTP client library. The existing WebSocket infrastructure for Serlvet based containers has been moved to a dedicated package and renamed accordingly. Fixes gh-9113
2017-05-12 17:29:12 +08:00
org.springframework.boot.autoconfigure.websocket.reactive.WebSocketReactiveAutoConfiguration,\
org.springframework.boot.autoconfigure.websocket.servlet.WebSocketServletAutoConfiguration,\
org.springframework.boot.autoconfigure.websocket.servlet.WebSocketMessagingAutoConfiguration,\
Add auto-configuration for WebServiceTemplate See gh-12707
2018-03-31 20:07:42 +08:00
org.springframework.boot.autoconfigure.webservices.WebServicesAutoConfiguration,\
org.springframework.boot.autoconfigure.webservices.client.WebServiceTemplateAutoConfiguration
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
Perform analysis of failures caused by DataSourceBeanCreationException Closes gh-5351
2016-04-21 00:34:44 +08:00
# Failure analyzers
org.springframework.boot.diagnostics.FailureAnalyzer=\
Add NoSuchBeanDefinitionException failure analyzer Add a `FailureAnalyzer` that handles the case where the context does not start because no candidate bean was found for an `InjectionPoint`. The implementation inspects the auto-configuration report for beans that are candidate and output the condition(s) that lead to such beans to be discarded on startup. If a whole auto-configuration class is disabled (or excluded), its beans are inspected and candidates are extracted in a similar way. This works for both injection by type and by name. Closes gh-6612
2016-08-24 14:57:22 +08:00
org.springframework.boot.autoconfigure.diagnostics.analyzer.NoSuchBeanDefinitionFailureAnalyzer,\
Add FailureAnalyzer for Hikari Hikari can configure both an underlying Driver or DataSource. Spring Boot only supports the former so any attempt to trigger the creation of the latter will lead to an exception since the auto-configuration has set driver-specific field. This commit adds an analyzer that intercepts such faulty scenario and indicate that users should configure Hikari with an underlying DataSource themselves. Closes gh-6568
2016-08-26 17:31:46 +08:00
org.springframework.boot.autoconfigure.jdbc.DataSourceBeanCreationFailureAnalyzer,\
Relax use of spring.session.store-type This commit makes the "spring.session.store-type" property optional, adding an additional check when it is not present that validates only one supported implementation is available on the classpath. As Spring Session has been modularized, the chance that multiple implementations are available on the classpath are lower. When only one implementation is present, we attempt to auto-configure it. When more than one implementation is present and no session store is configured, a NonUniqueSessionRepositoryException is thrown. Closes gh-9863
2017-09-13 17:20:06 +08:00
org.springframework.boot.autoconfigure.jdbc.HikariDriverConfigurationFailureAnalyzer,\
org.springframework.boot.autoconfigure.session.NonUniqueSessionRepositoryFailureAnalyzer
Perform analysis of failures caused by DataSourceBeanCreationException Closes gh-5351
2016-04-21 00:34:44 +08:00
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,\
Add jmustache support The package names changed a bit from the prototype project, but wuth vanilla autconfiguration usage that shouldn't matter. Follows closely the Groovy templates support. Templates live in classpath:/templates/*.html by default. Fixes gh-2242
2015-01-09 21:50:39 +08:00
org.springframework.boot.autoconfigure.mustache.MustacheTemplateAvailabilityProvider,\
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,\
Restructure web auto-configuration Restructure `org.springframework.boot.autoconfigure.web` to better align with the new package structure in `spring-boot`. Auto-configuration is now split into client, servlet and reactive sub-packages. In addition a new `http` package now handles common HTTP concerns. Fixes gh-8616
2017-03-15 09:06:53 +08:00
org.springframework.boot.autoconfigure.web.servlet.JspTemplateAvailabilityProvider