[
https://issues.apache.org/jira/browse/CLOUDSTACK-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492861#comment-14492861
]
ASF GitHub Bot commented on CLOUDSTACK-8335:
--------------------------------------------
Github user K0zka commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/163#discussion_r28268011
--- Diff: plugins/hypervisors/kvm/pom.xml ---
@@ -45,7 +38,7 @@
<version>${project.version}</version>
</dependency>
<dependency>
- <groupId>org.libvirt</groupId>
+ <groupId>com.github.K0zka</groupId>
--- End diff --
Hi Rohit,
I updated the group ID to that because I can publish with that group ID
only and not with org.libvirt, unfortunately the libvirt maintainers do not
seem to be interested in pushing their artifacts to central repo.
I agree that the groupId does not look good, but I haven't found another
way. I will try to keep an up to date version in central repo untl libvirt
maintainers accept the changes I have done on the pom.xml and publish to maven
central, but this may take quite some time.
> publish maven artifacts to central repo
> ---------------------------------------
>
> Key: CLOUDSTACK-8335
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8335
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Laszlo Hornyak
> Assignee: Laszlo Hornyak
> Labels: build, release
>
> Publish the cloudstack artifacts to the central maven repository.
> Blocking issues:
> * third party repositories:
> * ceph
> * libvirt
> [Mailing list
> thread|http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201503.mbox/browser]
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
