Skip to content

Commit bc1a8c9

Browse files
authored
Fixes in adoc format (#10037)
1 parent 376ec8b commit bc1a8c9

File tree

3 files changed

+18
-17
lines changed

3 files changed

+18
-17
lines changed

RELEASE.adoc

+14-14
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
1-
# Micronaut Core Release Process
1+
= Micronaut Core Release Process
22

3-
1. Ensure all changes from previous branches are merged up
4-
1. Ensure there are no snapshot dependencies
5-
1. Set the version to a release version in `gradle.properties`
6-
1. Commit the release `git commit -a -m "Release Micronaut XXX"`
7-
1. Tag the release `git tag vXXX` (Don't forget the `v` prefix!)
8-
1. Push the tag `git push --tags` and waiting for Travis to complete the tagged release https://travis-ci.org/micronaut-projects/micronaut-core/
9-
1. Login to the Bintray repo at https://bintray.com/micronaut/core-releases-local and click the button to publish the staged release.
10-
1. Update the release notes at https://github.com/micronaut-projects/micronaut-core/releases/tag/vXXX
11-
1. Run the Maven Central sync locally `./gradlew sWMC` (may take over an hour, repeat if fails at any point)
12-
1. Verify the release worked
3+
. Ensure all changes from previous branches are merged up
4+
. Ensure there are no snapshot dependencies
5+
. Set the version to a release version in `gradle.properties`
6+
. Commit the release `git commit -a -m "Release Micronaut XXX"`
7+
. Tag the release `git tag vXXX` (Don't forget the `v` prefix!)
8+
. Push the tag `git push --tags` and waiting for Travis to complete the tagged release https://travis-ci.org/micronaut-projects/micronaut-core/
9+
. Login to the Bintray repo at https://bintray.com/micronaut/core-releases-local and click the button to publish the staged release.
10+
. Update the release notes at https://github.com/micronaut-projects/micronaut-core/releases/tag/vXXX
11+
. Run the Maven Central sync locally `./gradlew sWMC` (may take over an hour, repeat if fails at any point)
12+
. Verify the release worked
1313
* Run `sdk install micronaut XXX` and perform smoke tests or creating an application etc.
1414
* Check the documentation published to docs.micronaut.io/XXX
15-
1. Change the version in `gradle.properties` back to a snapshot of next release
16-
1. Push the code `git push`
17-
1. Announce the Release
15+
. Change the version in `gradle.properties` back to a snapshot of next release
16+
. Push the code `git push`
17+
. Announce the Release

ROADMAP.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
# Micronaut ROADMAP
1+
= Micronaut ROADMAP
22

33
See https://github.com/micronaut-projects/micronaut-core/projects/5[Micronaut ROADMAP] for Roadmap project planning.

src/main/docs/guide/ioc/types.adoc

+3-2
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,8 @@ NOTE: There are 3 different provider types supported, however the `BeanProvider`
3939
[NOTE]
4040
====
4141
When injecting a `java.lang.Collection`, or `java.util.stream.Stream`, `Array` of beans into a bean matching the injection type, then the owning bean will not be a member of the injected collection. A common pattern demonstrating this is aggregation. For example:
42-
```java
42+
[source,java]
43+
----
4344
@Singleton
4445
class AggregateEngine implements Engine {
4546
@Inject
@@ -52,7 +53,7 @@ class AggregateEngine implements Engine {
5253
5354
...
5455
}
55-
```
56+
----
5657
In this example, the injected member variable `engines` will not contain an instance of `AggregateEngine`
5758
====
5859

0 commit comments

Comments
 (0)