-
Notifications
You must be signed in to change notification settings - Fork 34
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.
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
Publish the CertLogic runnner as an artifact to Maven Central. #12
Comments
I believe Maven Central is unlikely at this point as the entire project uses Github Packages, but for Github Packages I can see the benefit, I'll forward it |
Do you have an estimate when the package might be available? |
I don't have an ETA yet - but we'll keep this issue updated once our dev's can get to it. |
pinging @mlenkeit , as I believe that could also help you - do you know some CWA devs who could do some magic here? |
@vaubaehn we are currently focusing on our fork, as the module contains network and persistence layers that conflict with settings in CWA. We are trying to keep the diff as little as necessary so facilitate updates from upstream. |
You mean that the network and persistence layers will be decoupled, so that certlogic can focus just on its primary task? Where is the fork? |
@wkornewald /FYI @SZoerner |
At the time of pinging you, I was assuming that "only" taking care of #17 could result in 1:1 upstream. After your last comment I found the fork, and it looks like a good idea 👍 |
Current Implementation
Verifiers that would like to integrate the CertLogic RuleEngine as a library currently need to reference the source code directly, or compile it locally and reference their own build.
Suggested Enhancement
By publishing the compiled artefact to a public repository (e.g. as a Github Action pushing the jar to Maven Central), consumers can include the latest version without manual effort.
Expected Benefits
By using a public maven repo, it's easy for downstream dependencies to keep up to date with new feature and bugfixes without manual intervention.
The text was updated successfully, but these errors were encountered: