tchekai704
/
src-spring-framework
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Spring Framework
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
19874 Commits
19 Branches
274 Tags
318 MiB
Tree: 1a13700f8b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1a13700f8b'
${ noResults }
src-spring-framework/settings.gradle

40 lines
970 B
Raw Normal View History Unescape

Move Gradle plugin repos declaration to settings See gh-23282
5 years ago
pluginManagement {
repositories {
gradlePluginPortal()
maven { url 'https://repo.spring.io/plugins-release' }
}
}
Polish contribution See gh-23869
5 years ago
apply from: "$rootDir/gradle/build-cache-settings.gradle"
Enable local build cache for buildSrc and main project
5 years ago
Polish quote styles in gradle files Replace singe quote-marks with double quote-marks when possible for a more consistent style.
12 years ago
include "spring-aop"
include "spring-aspects"
include "spring-beans"
include "spring-context"
include "spring-context-support"
Support for candidate components index This commit adds a "spring-context-indexer" module that can be added to any project in order to generate an index of candidate components defined in the project. `CandidateComponentsIndexer` is a standard annotation processor that looks for source files with target annotations (typically `@Component`) and references them in a `META-INF/spring.components` generated file. Each entry in the index is the fully qualified name of a candidate component and the comma-separated list of stereotypes that apply to that candidate. A typical example of a stereotype is `@Component`. If a project has a `com.example.FooService` annotated with `@Component` the following `META-INF/spring.components` file is generated at compile time: ``` com.example.FooService=org.springframework.stereotype.Component ``` A new `@Indexed` annotation can be added on any annotation to instructs the scanner to include a source file that contains that annotation. For instance, `@Component` is meta-annotated with `@Indexed` now and adding `@Indexed` to more annotation types will transparently improve the index with additional information. This also works for interaces or parent classes: adding `@Indexed` on a `Repository` base interface means that the indexed can be queried for its implementation by using the fully qualified name of the `Repository` interface. The indexer also adds any class or interface that has a type-level annotation from the `javax` package. This includes obviously JPA (`@Entity` and related) but also CDI (`@Named`, `@ManagedBean`) and servlet annotations (i.e. `@WebFilter`). These are meant to handle cases where a component needs to identify candidates and use classpath scanning currently. If a `package-info.java` file exists, the package is registered using a "package-info" stereotype. Such files can later be reused by the `ApplicationContext` to avoid using component scan. A global `CandidateComponentsIndex` can be easily loaded from the current classpath using `CandidateComponentsIndexLoader`. The core framework uses such infrastructure in two areas: to retrieve the candidate `@Component`s and to build a default `PersistenceUnitInfo`. Rather than scanning the classpath and using ASM to identify candidates, the index is used if present. As long as the include filters refer to an annotation that is directly annotated with `@Indexed` or an assignable type that is directly annotated with `@Indexed`, the index can be used since a dedicated entry wil be present for that type. If any other unsupported include filter is specified, we fallback on classpath scanning. In case the index is incomplete or cannot be used, The `spring.index.ignore` system property can be set to `true` or, alternatively, in a "spring.properties" at the root of the classpath. Issue: SPR-11890
8 years ago
include "spring-context-indexer"
Polish quote styles in gradle files Replace singe quote-marks with double quote-marks when possible for a more consistent style.
12 years ago
include "spring-core"
Rename non-Framework project modules Prior to this commit, the Spring Framework build would mix proper framework modules (spring-* modules published to maven central) and internal modules such as: * "spring-framework-bom" (which publishes the Framework BOM with all modules) * "spring-core-coroutines" which is an internal modules for Kotlin compilation only This commit renames these modules so that they don't start with "spring-*"; we're also moving the "kotlin-coroutines" module under "spring-core", since it's merged in the resulting JAR. See gh-23282
5 years ago
include "kotlin-coroutines"
project(':kotlin-coroutines').projectDir = file('spring-core/kotlin-coroutines')
Polish quote styles in gradle files Replace singe quote-marks with double quote-marks when possible for a more consistent style.
12 years ago
include "spring-expression"
include "spring-instrument"
Overridable Commons Logging bridge in separate spring-jcl jar Issue: SPR-14512
8 years ago
include "spring-jcl"
Polish quote styles in gradle files Replace singe quote-marks with double quote-marks when possible for a more consistent style.
12 years ago
include "spring-jdbc"
include "spring-jms"
Create spring-messaging module Consolidates new, messaging-related classes from spring-context and spring-websocket into one module.
12 years ago
include "spring-messaging"
Polish quote styles in gradle files Replace singe quote-marks with double quote-marks when possible for a more consistent style.
12 years ago
include "spring-orm"
include "spring-oxm"
include "spring-test"
include "spring-tx"
include "spring-web"
include "spring-webmvc"
Rename spring-web-reactive to spring-webflux Issue: SPR-15190
8 years ago
include "spring-webflux"
Add spring-websocket module
12 years ago
include "spring-websocket"
Rename non-Framework project modules Prior to this commit, the Spring Framework build would mix proper framework modules (spring-* modules published to maven central) and internal modules such as: * "spring-framework-bom" (which publishes the Framework BOM with all modules) * "spring-core-coroutines" which is an internal modules for Kotlin compilation only This commit renames these modules so that they don't start with "spring-*"; we're also moving the "kotlin-coroutines" module under "spring-core", since it's merged in the resulting JAR. See gh-23282
5 years ago
include "framework-bom"
Move integration tests to dedicated module This commit moves the dependency management and test source files related to integration tests to a dedicated module. This allows us to focus the root project on building the Spring Framework. See gh-23282
5 years ago
include "integration-tests"
Expose Gradle buildSrc for IDE support Create 'spring-build-src' Gradle module that exposes the buildSrc folder as an IDE project.
12 years ago
Consistently use double quotes (even if no interpolation needed) Includes upgrade to Hibernate ORM 5.3.5, EclipseLink 2.7.3, Selenium HtmlUnit Driver 2.32.1, Jetty 9.4.12 RC2.
6 years ago
rootProject.name = "spring"
Allow dedicated build files for subprojects With this change, each subproject can configure its build in a dedicated file like: ``` spring-core/spring-core.gradle spring-web/spring-web.gradle ``` Issue: SPR-15885
7 years ago
rootProject.children.each {project ->
project.buildFileName = "${project.name}.gradle"
Latest dependency updates (POI 3.17, Rome 1.8, EhCache 3.4, Caffeine 2.5.6, RxJava 2.1.4, Tomcat 8.5.21, JRuby 9.1.13, Rhino 1.7.7.2)
7 years ago
}