https://github.com/wildfly/prospero-metadata
https://github.com/wildfly/prospero-metadata
Last synced: 6 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/wildfly/prospero-metadata
- Owner: wildfly
- License: apache-2.0
- Created: 2023-12-05T18:13:01.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2025-10-06T15:22:50.000Z (10 months ago)
- Last Synced: 2025-10-20T12:29:26.486Z (9 months ago)
- Language: Java
- Size: 2.56 MB
- Stars: 0
- Watchers: 7
- Forks: 5
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
## Prospero metadata
This project is part of [Prospero project](https://github.com/wildfly/prospero/) and provides the API to create the installation metadata used by Prospero to manager and update WildFly servers.
## Building
* JDK 11 or newer - check `java -version`
* Maven 3.6.0 or newer - check `mvn -v`
To build with your own Maven installation:
mvn install
## Release Procedure
# Releasing Remoting JMX
Prior to releasing you should ensure you have your own GPG signing key set up, published to a key server and listed on [wildfly.org](https://www.wildfly.org/contributors/pgp/).
## Prepare the release
Execute:
```
mvn release:prepare -Pjboss-release
```
## Perform the release
Execute:
```
mvn release:perform -Pjboss-release
```
This will deploy the release to the `wildfly-staging` repository.
Wait for 10 minutes then visit the Validation task for the [`wildfly-staging` repository in Nexus](https://repository.jboss.org/nexus/#browse/browse:wildfly-staging). If this task ran at least 10 minutes after the release was deployed check the latest results on the Settings tab and verify that at least one component was processed and that there were no errors. If the task has not run it can be manually kicked off using the Run button.
e.g.
> Processed X components.
> - no errors were found.
> - the deployment was a dry run (no actual publishing).
If others are also deploying at the same time this count could be higher, the important check is that the scan was at least 10 minutes after it was deployed, 1 or more components were scanned and no errors specific to Remoting JMX are reported.
## Complete the release
If no issues are reported complete the release.
Move the component to the releases repository:
```
git checkout
mvn nxrm3:staging-move
```
Once this is done, the release will be pushed to the `releases` repository in Nexus and then to Maven Central.
## License
* [Apache License 2.0](http://www.apache.org/licenses/LICENSE-2.0)