Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix documented output directory #192

Closed
wants to merge 1 commit into from
Closed

Fix documented output directory #192

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions src/site-docs/apt/index.apt.vm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ The <<<apache-release>>> Profile

The profile includes the following plugins:

* maven-assembly-plugin:
* <maven-assembly-plugin>:
{{{/apache-resource-bundles/source-release/}org.apache.apache.resources:apache-source-release-assembly-descriptor:$context.get("version.apache-resource-bundles")}}
is added as dependency, and an execution is configured with <<<source-release-assembly>>> id.\
The plugin is configured to take a <<<descriptorRef>>> name from the
Expand All @@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Released files are in target/checkout/target in target we have current project snapshot version.
So sentence was correct.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, this sentence refers only to releasing with m-r-p but not to the profile in general.

to be copied to projects' {{{http://www.apache.org/dev/release-distribution}Apache <<</dist/>>> release distribution}}
directory:

* <<<$\{artifactId\}-$\{version\}-source-release.[zip|tar.gz]>>>: the source release archive(s)

* <<<$\{artifactId\}-$\{version\}-source-release.[zip|tar.gz].sha512>>>: their checksum(s)
* <<<$\{artifactId\}-$\{version\}-source-release.[zip|tar.gz].sha512>>>: the checksum(s)

* <<<$\{artifactId\}-$\{version\}-source-release.[zip|tar.gz].asc>>>: their signature(s)
* <<<$\{artifactId\}-$\{version\}-source-release.[zip|tar.gz].asc>>>: the signature(s)

[]

Expand Down