Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Sign in / Register
Toggle navigation
S
spring-boot
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
DEMO
spring-boot
Commits
0f88f743
Commit
0f88f743
authored
Apr 10, 2014
by
Lukasz Kryger
Committed by
Dave Syer
Apr 11, 2014
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor fixes in the docs
parent
41cdb7b4
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
10 additions
and
10 deletions
+10
-10
spring-boot-features.adoc
spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
+7
-7
using-spring-boot.adoc
spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
+3
-3
No files found.
spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
View file @
0f88f743
...
...
@@ -149,7 +149,7 @@ within a JUnit test.
=== Using the CommandLineRunner
If you want access to the raw command line arguments, or you need to run some specific code
once the `SpringApplication` has started you can implement the `CommandLineRunner`
interface. The `run(String... args)` method will be called on all
s
pring beans
interface. The `run(String... args)` method will be called on all
S
pring beans
implementing this interface.
[source,java,indent=0]
...
...
@@ -187,7 +187,7 @@ interface if they wish to return a specific exit code when the application ends.
[[boot-features-external-config]]
== Externalized Configuration
Spring Boot
like
s you to externalize your configuration so you can work with the same
Spring Boot
allow
s you to externalize your configuration so you can work with the same
application code in different environments. You can use properties files, YAML files,
environment variables and command-line arguments to externalize configuration. Property
values can be injected directly into your beans using the `@Value` annotation, accessed
...
...
@@ -227,14 +227,14 @@ To provide a concrete example, suppose you develop a `@Component` that uses a
You can bundle an `application.properties` inside your jar that provides a sensible
default `name`. When running in production, an `application.properties` can be provided
outside of your jar that overrides `name`; and for one
off testing, you can launch with
outside of your jar that overrides `name`; and for one
-
off testing, you can launch with
a specific command line switch (e.g. `java -jar app.jar --name="Spring"`).
[[boot-features-external-config-command-line-args]]
=== Accessing command line properties
By default
SpringApplication
will convert any command line option arguments (starting
By default
`SpringApplication`
will convert any command line option arguments (starting
with ``--'', e.g. `--server.port=9000`) to a `property` and add it to the Spring
`Environment`. As mentioned above, command line properties always take precedence over
other property sources.
...
...
@@ -261,8 +261,8 @@ an alternative to '.properties'.
If you don't like `application.properties` as the configuration file name you can switch
to another by specifying a `spring.config.name` environment property. You can also refer
to an explicit location using the `spring.config.location` environment property
(comma-
separated list of directory locations, or file paths).
to an explicit location using the `spring.config.location` environment property
(comma-
separated list of directory locations, or file paths).
[indent=0]
----
...
...
@@ -506,7 +506,7 @@ property editors (via a `CustomEditorConfigurer` bean).
[[boot-features-external-config-validation]]
==== @ConfigurationProperties Validation
Spring Boot will attempt to validate external configuration, by default using JSR-303
(if it is on the classpath). You can simply add JSR-303 `javax.valid
id
ation` constraint
(if it is on the classpath). You can simply add JSR-303 `javax.validation` constraint
annotations to your `@ConfigurationProperties` class:
[source,java,indent=0]
...
...
spring-boot-docs/src/main/asciidoc/using-spring-boot.adoc
View file @
0f88f743
...
...
@@ -6,7 +6,7 @@
This
section
goes
into
more
detail
about
how
you
should
use
Spring
Boot
.
It
covers
topics
such
as
build
systems
,
auto
-
configuration
and
run
/
deployment
options
.
We
also
cover
some
Spring
Boot
best
practices
.
Although
there
is
nothing
particularly
special
about
Spring
Boot
(
it
is
just
another
library
that
you
can
consume
)
.
T
here
are
a
few
Spring
Boot
(
it
is
just
another
library
that
you
can
consume
)
,
t
here
are
a
few
recommendations
that
,
when
followed
,
will
make
your
development
process
just
a
little
easier
.
...
...
@@ -63,7 +63,7 @@ the `parent`:
----
NOTE: You should only need to specify the Spring Boot version number on this dependency.
i
f you import additional starters, you can safely omit the version number.
I
f you import additional starters, you can safely omit the version number.
...
...
@@ -571,7 +571,7 @@ the `spring-boot-plugin`
[[using-boot-hot-swapping]]
=== Hot swapping
Since Spring Boot applications are just plain Java application, JVM hot-swapping should
Since Spring Boot applications are just plain Java application
s
, JVM hot-swapping should
work out of the box. JVM hot swapping is somewhat limited with the bytecode that it can
replace, for a more complete solution the
https://github.com/spring-projects/spring-loaded[Spring Loaded] project, or
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment