njord:validate
Full name:
eu.maveniverse.maven.plugins:njord:0.7.0:validate
Description:
Validate given store against given publisher.
Attributes:
- Executes as an aggregator goal.
- The goal is thread-safe and supports parallel builds.
Required Parameters
Name | Type | Since | Description |
---|---|---|---|
<details> |
boolean |
- |
Show detailed validation report. Default: false User Property: details |
<full> |
boolean |
- |
If showing details, show full validation report (even valid checks too). Default: false User Property: full |
Optional Parameters
Name | Type | Since | Description |
---|---|---|---|
<publisher> |
String |
- |
The name of the publisher to publish to. If not given, Njord will try to figure it out: it will look in user properties, project properties (if available) and user Settings server configuration.
This "heuristic" will work only if there is current project. While invoking mojo is possible outside a project as well (validate and publish mojos does not require project), in such cases this parameter is mandatory, as there will be no contextual information to choose publisher from. User Property: publisher |
<skip> |
boolean |
- |
No description. Default: false User Property: skip |
<store> |
String |
- |
The name of the store to publish. If not given, Njord will try to figure it out: will look for existing stores created from staging this project and will choose latest (newest) out of them if multiple found.
This "heuristic" will work only if there is current project. While invoking mojo is possible outside a project as well (validate and publish mojos does not require project), in such cases this parameter is mandatory, as there will be no contextual information to choose store from. User Property: store |
Parameter Details
<details>
- Type:
boolean
- Required:
Yes
- User Property:
details
- Default:
false
<full>
- Type:
boolean
- Required:
Yes
- User Property:
full
- Default:
false
<publisher>
This "heuristic" will work only if there is current project. While invoking mojo is possible outside a project as well (validate and publish mojos does not require project), in such cases this parameter is mandatory, as there will be no contextual information to choose publisher from.
- Type:
java.lang.String
- Required:
No
- User Property:
publisher
<skip>
- Type:
boolean
- Required:
No
- User Property:
skip
- Default:
false
<store>
This "heuristic" will work only if there is current project. While invoking mojo is possible outside a project as well (validate and publish mojos does not require project), in such cases this parameter is mandatory, as there will be no contextual information to choose store from.
- Type:
java.lang.String
- Required:
No
- User Property:
store