slawekjaranowski commented on code in PR #192:
URL:
https://github.com/apache/maven-apache-parent/pull/192#discussion_r1463175494
##########
src/site-docs/apt/index.apt.vm:
##########
@@ -136,27 +136,27 @@ The <<<apache-release>>> Profile
If you want to avoid this default assembly execution to provide your own
mechanism to produce the source release archive,
you can disable the execution by configuring <<<skipAssembly>>> parameter
for this <<<source-release-assembly>>> execution id
- * maven-source-plugin: configured to build and attach a source jar.
+ * <maven-source-plugin>: configured to build and attach a source jar.
- * maven-javadoc-plugin: configured to build and attach a javadoc jar.
+ * <maven-javadoc-plugin>: configured to build and attach a javadoc jar.
- * maven-gpg-plugin: configured to sign everything. It expects to find
+ * <maven-gpg-plugin>: configured to sign everything. It expects to find
a passphrase in <<<$\{gpg.passphrase\}>>>, presumably in your
<<<settings.xml>>>.
- * checksum-maven-plugin: configured to create a checksum file(s) for source
release as
+ * <checksum-maven-plugin>: configured to create a checksum file(s) for source
release as
required by
{{{http://www.apache.org/dev/release-distribution#sigs-and-sums}Apache release
distribution policy}}.
[]
- When doing a release with maven-release-plugin, this creates files in
<<<target/checkout/target>>> ready
+ When doing a release with <maven-release-plugin>, this creates files in
<<<target>>> ready
Review Comment:
Released files are in `target/checkout/target` in `target` we have current
project snapshot version.
So sentence was correct.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
