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

[JEP-229] Noting stock block-MRP profile #18

Merged
merged 1 commit into from
Nov 9, 2020
Merged

[JEP-229] Noting stock block-MRP profile #18

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
19 changes: 4 additions & 15 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -372,22 +372,11 @@ To ensure that the two copies of that third-party version stay in synch, you can
```

Since inadvertently running MRP on such a project would result in a mess,
it is best to explicitly prevent that:
it is best to explicitly prevent that.
This is done automatically by the plugin and general component parent POMs
when you define the `changelist.format` property.

```xml
<build>
<plugins>
<plugin>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<preparationGoals>not-set-up-for-MRP</preparationGoals>
</configuration>
</plugin>
</plugins>
</build>
```

Pending [JEP-221](https://jenkins.io/jep/221) or similar,
Pending [JEP-229](https://jenkins.io/jep/229),
there is no automatic publishing of such artifacts.
However, you can release manually if you have
[personal deployment credentials](https://github.com/jenkins-infra/repository-permissions-updater).
Expand Down