lsm/initializr
1
0
Fork 0
mirror of https://gitee.com/dcren/initializr.git synced 2025-09-19 18:22:26 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
Files
76ac171ada6c2476acf6f20c8ec07055f389f342
initializr/initializr-service/application.yml

266 lines
8.0 KiB
YAML
Raw Normal View History

Use reactor-spring idioms
2014-05-28 19:25:35 +01:00
info:
project:
name: Spring Start
Upgrade to Spring Boot 1.2.0
2014-12-13 11:13:39 +01:00
version: 0.3.1
Upgrade to Spring Boot 1.2.2.RELEASE
2015-03-10 15:29:18 +01:00
# remember to update static/install.sh as well:
Use reactor-spring idioms
2014-05-28 19:25:35 +01:00
spring-boot:
Upgrade to Spring Boot 1.2.3.RELEASE
2015-04-20 15:18:27 +02:00
version: 1.2.3.RELEASE
Use reactor-spring idioms
2014-05-28 19:25:35 +01:00
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
initializr:
Add Vaadin support Closes gh-102
2015-03-27 10:36:13 +01:00
env:
boms:
vaadin-bom:
groupId: com.vaadin
artifactId: vaadin-bom
Upgrade to Vaadin Spring Boot 1.0.0.beta3
2015-04-28 17:59:01 +02:00
version: 7.4.4
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
dependencies:
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Core
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
content:
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Security
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: security
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for spring-security
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: AOP
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: aop
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for aspect-oriented programming including spring-aop and AspectJ
Add version range support for dependencies Previously, it was not possible to define the Spring Boot version that a dependency requires. As a result, many new starters implemented as part of Spring Boot 1.2 are not available. Each dependency can now define a `versionRange` attribute that defines the Spring Boot version range that it supports. The range is defined either as a single version, in which case it defines that version and any later versions or using brackets. A square bracket (`[` or `]`) denotes an inclusive range while a round bracket (`(` or `)`) denotes an exclusive range. Bumped the current-metadata format to 2.1 to include this additional `versionRange` attribute, that is application/vnd.initializr.v2.1+json Existing clients requesting v2 will not get any dependency that defines a `versionRange` attribute. Closes gh-62
2015-01-27 17:54:30 +01:00
- name: Atomikos (JTA)
id: jta-atomikos
description: Support for JTA distributed transactions via Atomikos
versionRange: 1.2.0.M1
- name: Bitronix (JTA)
id: jta-bitronix
description: Support for JTA distributed transactions via Bitronix
versionRange: 1.2.0.M1
Use reactor-spring idioms
2014-05-28 19:25:35 +01:00
- name: Web
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
content:
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Web
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: web
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for full-stack web development, including Tomcat and spring-webmvc
Add support for dependency facet This commit allows any dependency to be tagged with a facet. A facet is a simple name that can be used to further tune the project request if necessary. Prior to this commit, the list of dependencies that were related to the web was hardcoded. This was used for special handling such as adding a dependency automatically if necessary of creating additional resources in the project. This logic was moved to a standard 'web' facet that any dependency can declare through configuration. Fixes gh-30
2014-08-19 13:28:27 +02:00
facets:
- web
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Websocket
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: websocket
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for websocket development with Tomcat
Dependency update This commit updates the spring boot version used by the install script and adds 3 new starters: ws, hornetq and elasticsearch
2014-08-21 13:17:39 +02:00
- name: WS
id: ws
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for Spring Web Services
Add version range support for dependencies Previously, it was not possible to define the Spring Boot version that a dependency requires. As a result, many new starters implemented as part of Spring Boot 1.2 are not available. Each dependency can now define a `versionRange` attribute that defines the Spring Boot version range that it supports. The range is defined either as a single version, in which case it defines that version and any later versions or using brackets. A square bracket (`[` or `]`) denotes an inclusive range while a round bracket (`(` or `)`) denotes an exclusive range. Bumped the current-metadata format to 2.1 to include this additional `versionRange` attribute, that is application/vnd.initializr.v2.1+json Existing clients requesting v2 will not get any dependency that defines a `versionRange` attribute. Closes gh-62
2015-01-27 17:54:30 +01:00
- name: Jersey (JAX-RS)
id: jersey
description: Support for the Jersey RESTful Web Services framework
versionRange: 1.2.0.RELEASE
Add Vaadin support Closes gh-102
2015-03-27 10:36:13 +01:00
- name: Vaadin
id: vaadin
facets:
- web
groupId: com.vaadin
artifactId: vaadin-spring-boot-starter
Upgrade to Vaadin Spring Boot 1.0.0.beta3
2015-04-28 17:59:01 +02:00
version: 1.0.0.beta3
Add Vaadin support Closes gh-102
2015-03-27 10:36:13 +01:00
description: Support for Vaadin
bom: vaadin-bom
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Rest Repositories
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: data-rest
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for exposing Spring Data repositories over REST via spring-data-rest-webmvc
Add version range support for dependencies Previously, it was not possible to define the Spring Boot version that a dependency requires. As a result, many new starters implemented as part of Spring Boot 1.2 are not available. Each dependency can now define a `versionRange` attribute that defines the Spring Boot version range that it supports. The range is defined either as a single version, in which case it defines that version and any later versions or using brackets. A square bracket (`[` or `]`) denotes an inclusive range while a round bracket (`(` or `)`) denotes an exclusive range. Bumped the current-metadata format to 2.1 to include this additional `versionRange` attribute, that is application/vnd.initializr.v2.1+json Existing clients requesting v2 will not get any dependency that defines a `versionRange` attribute. Closes gh-62
2015-01-27 17:54:30 +01:00
- name: HATEOAS
id: hateoas
description: Support for HATEOAS-based RESTful services
Upgrade to Spring Boot 1.2.2.RELEASE
2015-03-10 15:29:18 +01:00
versionRange: 1.2.2.RELEASE
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Mobile
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: mobile
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for spring-mobile
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Template Engines
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
content:
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Freemarker
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: freemarker
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for the FreeMarker templating engine
Add support for dependency facet This commit allows any dependency to be tagged with a facet. A facet is a simple name that can be used to further tune the project request if necessary. Prior to this commit, the list of dependencies that were related to the web was hardcoded. This was used for special handling such as adding a dependency automatically if necessary of creating additional resources in the project. This logic was moved to a standard 'web' facet that any dependency can declare through configuration. Fixes gh-30
2014-08-19 13:28:27 +02:00
facets:
- web
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Velocity
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: velocity
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for the Velocity templating engine
Add support for dependency facet This commit allows any dependency to be tagged with a facet. A facet is a simple name that can be used to further tune the project request if necessary. Prior to this commit, the list of dependencies that were related to the web was hardcoded. This was used for special handling such as adding a dependency automatically if necessary of creating additional resources in the project. This logic was moved to a standard 'web' facet that any dependency can declare through configuration. Fixes gh-30
2014-08-19 13:28:27 +02:00
facets:
- web
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Groovy Templates
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: groovy-templates
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for the Groovy templating engine
Add support for dependency facet This commit allows any dependency to be tagged with a facet. A facet is a simple name that can be used to further tune the project request if necessary. Prior to this commit, the list of dependencies that were related to the web was hardcoded. This was used for special handling such as adding a dependency automatically if necessary of creating additional resources in the project. This logic was moved to a standard 'web' facet that any dependency can declare through configuration. Fixes gh-30
2014-08-19 13:28:27 +02:00
facets:
- web
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Thymeleaf
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: thymeleaf
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for the Thymeleaf templating engine, including integration with Spring
Add support for dependency facet This commit allows any dependency to be tagged with a facet. A facet is a simple name that can be used to further tune the project request if necessary. Prior to this commit, the list of dependencies that were related to the web was hardcoded. This was used for special handling such as adding a dependency automatically if necessary of creating additional resources in the project. This logic was moved to a standard 'web' facet that any dependency can declare through configuration. Fixes gh-30
2014-08-19 13:28:27 +02:00
facets:
- web
Add version range support for dependencies Previously, it was not possible to define the Spring Boot version that a dependency requires. As a result, many new starters implemented as part of Spring Boot 1.2 are not available. Each dependency can now define a `versionRange` attribute that defines the Spring Boot version range that it supports. The range is defined either as a single version, in which case it defines that version and any later versions or using brackets. A square bracket (`[` or `]`) denotes an inclusive range while a round bracket (`(` or `)`) denotes an exclusive range. Bumped the current-metadata format to 2.1 to include this additional `versionRange` attribute, that is application/vnd.initializr.v2.1+json Existing clients requesting v2 will not get any dependency that defines a `versionRange` attribute. Closes gh-62
2015-01-27 17:54:30 +01:00
- name: Mustache
id: mustache
description: Support for the Mustache templating engine
Upgrade to Spring Boot 1.2.2.RELEASE
2015-03-10 15:29:18 +01:00
versionRange: 1.2.2.RELEASE
Add version range support for dependencies Previously, it was not possible to define the Spring Boot version that a dependency requires. As a result, many new starters implemented as part of Spring Boot 1.2 are not available. Each dependency can now define a `versionRange` attribute that defines the Spring Boot version range that it supports. The range is defined either as a single version, in which case it defines that version and any later versions or using brackets. A square bracket (`[` or `]`) denotes an inclusive range while a round bracket (`(` or `)`) denotes an exclusive range. Bumped the current-metadata format to 2.1 to include this additional `versionRange` attribute, that is application/vnd.initializr.v2.1+json Existing clients requesting v2 will not get any dependency that defines a `versionRange` attribute. Closes gh-62
2015-01-27 17:54:30 +01:00
facets:
- web
Add database group Add an extra group with the databases that Boot supports out-of-the-box. This is a first step of a better user experience when someone selects the `data-jpa` or `jdbc` starter as it requires a Database to operate and none is provided by default. Closes gh-84
2015-02-24 16:45:25 +01:00
- name: Data
content:
- name: JDBC
id: jdbc
description: Support for JDBC databases
- name: JPA
id: data-jpa
description: Support for the Java Persistence API including spring-data-jpa, spring-orm and Hibernate
aliases:
- jpa
- name: MongoDB
id: data-mongodb
description: Support for the MongoDB NoSQL Database, including spring-data-mongodb
- name: Redis
id: redis
description: Support for the REDIS key-value data store, including spring-redis
- name: Gemfire
id: data-gemfire
description: Support for the GemFire distributed data store including spring-data-gemfire
- name: Solr
id: data-solr
description: Support for the Apache Solr search platform, including spring-data-solr
- name: Elasticsearch
id: data-elasticsearch
description: Support for the Elasticsearch search and analytics engine including spring-data-elasticsearch
- name: Database
content:
- name: H2
id: h2
description: Support for the H2 database (with embedded support)
groupId: com.h2database
artifactId: h2
scope: runtime
- name: HSQLDB
id: hsql
description: Support for the HSQLDB database (with embedded support)
groupId: org.hsqldb
artifactId: hsqldb
scope: runtime
- name: Apache Derby
id: derby
description: Support for the Apache Derby database (with embedded support)
groupId: org.apache.derby
artifactId: derby
scope: runtime
Upgrade to Spring Boot 1.2.2.RELEASE
2015-03-10 15:29:18 +01:00
versionRange: 1.2.2.RELEASE
Add database group Add an extra group with the databases that Boot supports out-of-the-box. This is a first step of a better user experience when someone selects the `data-jpa` or `jdbc` starter as it requires a Database to operate and none is provided by default. Closes gh-84
2015-02-24 16:45:25 +01:00
- name: MySQL
id: mysql
description: Support for the MySQL jdbc driver
groupId: mysql
artifactId: mysql-connector-java
scope: runtime
Add postgreSQL option Fixes gh-95 - See gh-85,gh-86
2015-03-24 16:29:40 +01:00
- name: PostgreSQL
id: postgresql
description: Support for the PostgreSQL jdbc driver
groupId: org.postgresql
artifactId: postgresql
version: 9.4-1201-jdbc41
scope: runtime
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Social
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
content:
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Facebook
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: social-facebook
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for spring-social-facebook
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: LinkedIn
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: social-linkedin
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for spring-social-linkedin
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Twitter
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: social-twitter
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for spring-social-twitter
Add database group Add an extra group with the databases that Boot supports out-of-the-box. This is a first step of a better user experience when someone selects the `data-jpa` or `jdbc` starter as it requires a Database to operate and none is provided by default. Closes gh-84
2015-02-24 16:45:25 +01:00
- name: I/O
content:
- name: Batch
id: batch
description: Support for Spring Batch including HSQLDB database
- name: Integration
id: integration
description: Support for common spring-integration modules
- name: JMS
id: hornetq
description: Support for Java Message Service API via HornetQ
- name: AMQP
id: amqp
description: Support for the Advanced Message Queuing Protocol via spring-rabbit
- name: Mail
id: mail
description: Support for javax.mail
versionRange: 1.2.0.RC1
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Ops
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
content:
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Actuator
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: actuator
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Production ready features to help you monitor and manage your application
Add version range support for dependencies Previously, it was not possible to define the Spring Boot version that a dependency requires. As a result, many new starters implemented as part of Spring Boot 1.2 are not available. Each dependency can now define a `versionRange` attribute that defines the Spring Boot version range that it supports. The range is defined either as a single version, in which case it defines that version and any later versions or using brackets. A square bracket (`[` or `]`) denotes an inclusive range while a round bracket (`(` or `)`) denotes an exclusive range. Bumped the current-metadata format to 2.1 to include this additional `versionRange` attribute, that is application/vnd.initializr.v2.1+json Existing clients requesting v2 will not get any dependency that defines a `versionRange` attribute. Closes gh-62
2015-01-27 17:54:30 +01:00
- name: Cloud Connectors
id: cloud-connectors
description: Simplifies connecting to services in cloud platforms
versionRange: 1.2.0.RELEASE
Initializr UI update This commit fully revisits the main UI of the service: * upgrade to Twitter Bootstrap 3.2.x (CSS, theme, font, glyphs) * add specific CSS * add favicon Besides, starters are now regrouped by themes and those themes are nicely displayed in the UI Fixes gh-23, gh-11
2014-06-27 21:01:01 +02:00
- name: Remote Shell
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
id: remote-shell
Support for dependency description This commit updates the configuration format and JSON metadata output to support an additional description attribute. The description attribute is meant to further describe the purpose of the dependency. This is a minor update to the JSON format that is fully backward compatible. Fixes gh-40
2014-10-24 14:06:45 +02:00
description: Support for CRaSH
Use reactor-spring idioms
2014-05-28 19:25:35 +01:00
types:
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
- name: Maven POM
Fix type id This commit improves the structure of the type id as it may be used by third party clients. The id now defines the build system and the nature of the project. Because STS hardcodes those IDs, a new (deprecated) property on type has been introduced to keep track of them. When serving the legacy HTML page that STS parses, those ids are used instead. Fixes gh-39
2014-10-29 18:09:47 +01:00
id: maven-build
Explicit support for curl Add an explicit support for curl by returning a text description of the service instead of the raw meta-data. curl users can still discover the json metadata by setting the appropriate Accept header. Also support for explicit "text/plain" if the user requires it. In this case a generic text description is returned. Closes gh-67
2015-01-19 17:36:11 +01:00
description: Generate a Maven pom.xml
Fix type id This commit improves the structure of the type id as it may be used by third party clients. The id now defines the build system and the nature of the project. Because STS hardcodes those IDs, a new (deprecated) property on type has been introduced to keep track of them. When serving the legacy HTML page that STS parses, those ids are used instead. Fixes gh-39
2014-10-29 18:09:47 +01:00
sts-id: pom.xml
More metadata for types This commit adds a 'tags' attribute to each type. Two tags are currently available: 1. build defines the build system that should be included in the project (maven and gradle) 2. format defines the format of the project (build for the build file and project for a project archive) When a type id is specified, the build tag is used to figure out which build system should be used. If no type is specified we fallback to Maven as we were already doing. Fixes gh-43
2014-10-30 11:15:47 +01:00
tags:
build: maven
format: build
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
default: false
action: /pom.xml
- name: Maven Project
Fix type id This commit improves the structure of the type id as it may be used by third party clients. The id now defines the build system and the nature of the project. Because STS hardcodes those IDs, a new (deprecated) property on type has been introduced to keep track of them. When serving the legacy HTML page that STS parses, those ids are used instead. Fixes gh-39
2014-10-29 18:09:47 +01:00
id: maven-project
Explicit support for curl Add an explicit support for curl by returning a text description of the service instead of the raw meta-data. curl users can still discover the json metadata by setting the appropriate Accept header. Also support for explicit "text/plain" if the user requires it. In this case a generic text description is returned. Closes gh-67
2015-01-19 17:36:11 +01:00
description: Generate a Maven based project archive
Fix type id This commit improves the structure of the type id as it may be used by third party clients. The id now defines the build system and the nature of the project. Because STS hardcodes those IDs, a new (deprecated) property on type has been introduced to keep track of them. When serving the legacy HTML page that STS parses, those ids are used instead. Fixes gh-39
2014-10-29 18:09:47 +01:00
sts-id: starter.zip
More metadata for types This commit adds a 'tags' attribute to each type. Two tags are currently available: 1. build defines the build system that should be included in the project (maven and gradle) 2. format defines the format of the project (build for the build file and project for a project archive) When a type id is specified, the build tag is used to figure out which build system should be used. If no type is specified we fallback to Maven as we were already doing. Fixes gh-43
2014-10-30 11:15:47 +01:00
tags:
build: maven
format: project
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
default: true
action: /starter.zip
- name: Gradle Config
Fix type id This commit improves the structure of the type id as it may be used by third party clients. The id now defines the build system and the nature of the project. Because STS hardcodes those IDs, a new (deprecated) property on type has been introduced to keep track of them. When serving the legacy HTML page that STS parses, those ids are used instead. Fixes gh-39
2014-10-29 18:09:47 +01:00
id: gradle-build
Fix gradl project description
2015-02-19 22:22:11 +01:00
description: Generate a Gradle build file
Fix type id This commit improves the structure of the type id as it may be used by third party clients. The id now defines the build system and the nature of the project. Because STS hardcodes those IDs, a new (deprecated) property on type has been introduced to keep track of them. When serving the legacy HTML page that STS parses, those ids are used instead. Fixes gh-39
2014-10-29 18:09:47 +01:00
sts-id: build.gradle
More metadata for types This commit adds a 'tags' attribute to each type. Two tags are currently available: 1. build defines the build system that should be included in the project (maven and gradle) 2. format defines the format of the project (build for the build file and project for a project archive) When a type id is specified, the build tag is used to figure out which build system should be used. If no type is specified we fallback to Maven as we were already doing. Fixes gh-43
2014-10-30 11:15:47 +01:00
tags:
build: gradle
format: build
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
default: false
action: /build.gradle
- name: Gradle Project
Fix type id This commit improves the structure of the type id as it may be used by third party clients. The id now defines the build system and the nature of the project. Because STS hardcodes those IDs, a new (deprecated) property on type has been introduced to keep track of them. When serving the legacy HTML page that STS parses, those ids are used instead. Fixes gh-39
2014-10-29 18:09:47 +01:00
id: gradle-project
Fix gradl project description
2015-02-19 22:22:11 +01:00
description: Generate a Gradle based project archive
Fix type id This commit improves the structure of the type id as it may be used by third party clients. The id now defines the build system and the nature of the project. Because STS hardcodes those IDs, a new (deprecated) property on type has been introduced to keep track of them. When serving the legacy HTML page that STS parses, those ids are used instead. Fixes gh-39
2014-10-29 18:09:47 +01:00
sts-id: gradle.zip
More metadata for types This commit adds a 'tags' attribute to each type. Two tags are currently available: 1. build defines the build system that should be included in the project (maven and gradle) 2. format defines the format of the project (build for the build file and project for a project archive) When a type id is specified, the build tag is used to figure out which build system should be used. If no type is specified we fallback to Maven as we were already doing. Fixes gh-43
2014-10-30 11:15:47 +01:00
tags:
build: gradle
format: project
Add support for custom dependency Prior to this commit, only spring boot starters can be added as project dependency using a simple String denoting the suffix of the artifactId. The standard 'org.springframework.boot' and 'spring-boot-starter-' artifactId prefix were assumed. This commit allows to define arbitrary dependencies with arbitrary identifiers; the groupId, artifactId and version of the dependency can be specified. Internally, all dependencies are converted to that format even the ones defined as standard spring boot starters. To allow that, a ProjectRequest is now resolved against the initializr metadata. If a request defines an unknown dependency, a simple String will be still considered a spring-boot-starter but a more complex unknown id will lead to an exception (e.g. 'org.foo:bar'). Fixes gh-17
2014-08-19 04:07:13 +02:00
default: false
action: /starter.zip
Add support for WAR packaging
2014-05-29 16:26:47 +01:00
packagings:
- name: Jar
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
id: jar
default: true
Add support for WAR packaging
2014-05-29 16:26:47 +01:00
- name: War
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
id: war
default: false
Add JavaVersion feature
2014-05-30 06:18:33 +01:00
javaVersions:
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
- id: 1.6
default: false
- id: 1.7
default: true
- id: 1.8
default: false
Add .groovy lang support
2014-05-30 09:50:24 +01:00
languages:
- name: Groovy
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
id: groovy
default: false
Add .groovy lang support
2014-05-30 09:50:24 +01:00
- name: Java
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
id: java
default: true
Add bootVersion to home page
2014-06-24 09:42:54 +01:00
bootVersions:
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
- name : Latest SNAPSHOT
Upgrade to Spring Boot 1.2.3.RELEASE
2015-04-20 15:18:27 +02:00
id: 1.2.4.BUILD-SNAPSHOT
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
default: false
Upgrade to Spring Boot 1.2.3.RELEASE
2015-04-20 15:18:27 +02:00
- name: 1.2.3
id: 1.2.3.RELEASE
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
default: true
Upgrade to Spring Boot 1.2.3.RELEASE
2015-04-20 15:18:27 +02:00
- name: 1.1.12
id: 1.1.12.RELEASE
Initializr library This commit splits the single file script in a library that can be released and published to the central repository. This allows anyone to start its own initializr instance with a proper configuration file and the following simple script: package app @Grab('io.spring.initalizr:initializr:1.0.0.BUILD-SNAPSHOT') class InitializerService { } The integration tests have been migrated so that they run as part of the build. Additional tests have been added to extract the content of the generated archive and assert the directory structure as well as the content of key files. Fixes gh-20
2014-08-18 16:14:17 +02:00
default: false
Secure actuator endpoints
2014-08-27 14:09:01 +02:00
Reference in New Issue Copy Permalink