Open GregDThomas opened 4 years ago
All of the automation around pushing artifacts into Archiva is depends on Travis. Every other plugin uses a set of customized maven commands. For reference, have a look at the Travis configuration file for the Monitoring plugin; https://github.com/igniterealtime/openfire-monitoring-plugin/blob/master/.travis.yml
Every plugin uses that exact same configuration (with the notable exception of the encrypted credentials being different.
This plugin uses Gradle, which makes re-using this functionality difficult. Although Gradle will have lots of benefits, the occasional "we must update the Travis config for every plugins" already is a cumbersome task even with every plugin using the exact same config. I dread having to support different variants.
The obvious way to prevent issues is to migrate this project to Maven, but maybe there are alternatives?
Understood! I'll experiment (possibly not soon) with how to do it with Gradle unless something changes before then.
I didn't attempt to migrate this plugin to our standardized github workflow for openfire plugins.
Currently, the artifacts are only kept (for a short time) on Gitlab. They should be uploaded to the Ignite Realtime Maven repo.