Red Hat Bugzilla – Bug 1305206
Can't deploy droolsjbpm-integration in redhat nexus repository
Last modified: 2016-03-02 04:40:42 EST
Description of problem:
We can't deploy droolsjbpm-integration to redhat nexus repository.
After investigation and discussion with Petr, I think the reason could possible is:
droolsjbpm-integration/kie-maven-plugin used io.takari which will used takari-maven-plugin for deployment.
However we found that it can't read the authentication from altDeploymentRepository.
it should be able to reproduce via in droolsjbpm-integration/kie-maven-plugin modules:
mvn clean deploy -DskipTests -DaltDeploymentRepository=jboss-snapshots-repository::default::https://repository.jboss.org/nexus/content/repositories/snapshots/ -s my-settings.xml
This won't be a problem to community since the deployment configuration is writen in distributionManagement
But in product side, we have to deploy to :
It's not possible to simply override the repository url since the authentication is different.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Petr, It seems that takari plugin has problem with altDeploymentRepository.
I am wondering that if we can replace the takari with maven deploy pluin in kie-maven-plugin module.
I believe that the proper solution here is to fix this in the takari-lifecycle (https://github.com/takari/takari-lifecycle) so that everyone using the plugin can benefit from the fix. I will hopefully be able to look at that.
In the meantime, I will see if I can configure the kie-maven-plugin to use the maven-deploy-plugin for deploying only. This temporary workaround should work until we upgrade to the takari version that contains the fix.
(In reply to Petr Siroky from comment #3)
> I believe that the proper solution here is to fix this in the
> takari-lifecycle (https://github.com/takari/takari-lifecycle) so that
> everyone using the plugin can benefit from the fix. I will hopefully be able
> to look at that.
> In the meantime, I will see if I can configure the kie-maven-plugin to use
> the maven-deploy-plugin for deploying only. This temporary workaround should
> work until we upgrade to the takari version that contains the fix.
That sounds perfect to me.
Thanks Petr for taking this!
Petr, Can I ask that would the short term solution be availabe for DR2 release?
Sorry Ryan. Haven't yet looked at this. Will try to do that today.
I've fixed the bug directly in the takari-lifecycle-plugin and released temporary version 1.11.11.jbossorg-1 which we will use until proper 1.11.12 gets released.
For a future reference, we need this fix in https://github.com/takari/takari-lifecycle/pull/34 (it could also be that it won't make it into 1.11.12 in time).
I think there isn't really anything QE needs to look at for this one. Ryan can you confirm everything works as expected and then close the BZ?
Yes, you are right.
I should verify this during productization stage.
It worked as expected.