Command line tools are invited to discover the HAL-compliant links
defined in the meta-data while Spring Boot CLI is a working client
application and requires a description of the capabilities in a more
high-level format.
Capabilities are now customized for those use cases.
Closes gh-77
Provide a polished version of the command-line service capabilities
with tables and support for the new version range.
Also support SpringBootCli explicitly so that the service capabilities
are rendered directly by the server instead of having the client parsing
the meta-data manually.
Closes gh-76
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
This commit introduces zepto.js as a minimal front-end library to
manipulate the DOM and a lightweight library `Versions` to parse and
compare version ranges (OSGI style).
With this change, only Boot starter dependencies that are compatible
with the selected Boot version should be displayed in the UI.
Partial fix for #62
Since Htmlunit does not provide a complete support for Javascript, smoke
tests are migrated to Gab (i.e. using Selenium and an actual browser).
This present a major challenge: it is not easy to assert the content of
a file that the browser downloads when it submits a form. First, the
browser should be configured to download the file directly instead of
opening a (native) pop-up asking the users where to download it. Then,
the tests should be aware of the location of the file in order to assert
it.
Hopefully, Firefox can be configured to achieve this goal.
Closes gh-75
A groovy-based project on Maven provides a better developer experience
if the sources are located in src/main/java and src/test/java.
This commit updates the generator to use this new location while keeping
the existing src/main/groovy project for Gradle builds.
Fixes gh-71
Remove `type` as a template variable since each action actually defines
the related type. This commit however does not address all the concerns
raised in gh-69; since the configuration is generic, there is no way to
know that a particular action handles one and only one type so removing
the type because it is redundant is not really possible.
Besides, the zip and tgz endpoints aren't exposed via configuration
either so offering such choice via the HAL-urls is not possible either.
Partially fixes gh-69
This commit improves the page layout:
* use lighter fonts for the curl command line
* align download buttons
* dependency choices are now using "col-xs-*" classes for mobile devices
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
Previously the generated archive wasn't self contained and the user had
to create a dedicated directory before extracting it in case the archive
utility does not handle that use case (MacOS supports that by default).
A baseDir request attribute has been added and generate a base directory
in the archive when set. It is enabled by default in the web UI and takes
the same value as the artifactId. Other clients are unaffected by this
change (and shouldn't probably).
Note that the legacy HTML form isn't impacted by this change either as
older STS versions expect the archive to have a very specific format.
curl-based tools can use that new baseDir request parameter to specify
that a base directory is required, something like
curl https://start.spring.io/starter.tgz -d baseDir=my-project
Closes gh-65
If Spring Boot 1.2 or later is used, the generated project uses the new
SpringBootApplication annotation as a replacement for what used to be
configured by Configuration, ComponentScan and EnableAutoConfiguration.
Also add an infrastructure to parse and compare versions.
Closes gh-46
Previously, the Assert helpers were located in the support package that
is also used by some support classes in the production code. Having both
test helpers and tests in the same package is a bit confusing.
Those test helpers are now relocated to a dedicated test package.
The 'name' field can now be used to customize the name of the generated
application (and its test counterpart). A default application name is
used If no suitable identifier can be inferred from the specified name.
Concretely, this means that the default application name is no longer
`Application` but `DemoApplication` since the default name is `demo`.
Closes gh-60
Previously if a project was generated with no defined dependency; a
metric with id 'counter.initializr.dependency.' was published. We now
make sure to properly identify that default use case and no metrics gets
published in such a case.
Fixes gh-57
Instead of doing a strict equality between the expected media type
and the one received in the response, we use isCompatibleWith that
ensure that at least the expected capabilities are present.
Style is the only parameter that deviates from the default names in the
metadata. As 'dependencies' is the name used in the metadata, it can be
used as an alias of style. This simplifies the HAL-generated URLs
Fixes gh-50
Update the metadata format in a non backward compatible way to ease
the use of the service from 3rd party clients. The updated metadata
format is now more descriptive and HAL-compliant and can be used with
Spring HATEOAS to build a client.
Metadata v1 is still served to preserve backward compatibility with
Spring Boot 1.2.0.RC1.
Closes gh-49
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
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
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
Prior to this commit, the browser was "guessing" the file name to use for
Maven and Gradle build files. This commit harmonizes the endpoints so
that they provide a Content-Disposition header with a preferred file
name.
