jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (Jira)" <j...@apache.org>
Subject [jira] [Closed] (JCLOUDS-77) whether needing to modify all ManagedServiceFactory's SERVICE_PID in order to allign with jclouds group id's change
Date Sat, 26 Sep 2020 02:32:00 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Gaul closed JCLOUDS-77.
------------------------------
    Resolution: Won't Fix

The Karaf project now maintains the jclouds bindings; please open an issue there.

> whether needing to modify all ManagedServiceFactory's SERVICE_PID in order to allign
with jclouds group id's change
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-77
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-77
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-karaf
>    Affects Versions: 1.7.0
>            Reporter: TangYong
>            Priority: Trivial
>
> This is a very trivial issue, eg. jclouds-karaf\services\src\main\java\org\jclouds\karaf\services\internal\Activator.java,
>  properties.put(Constants.SERVICE_PID, "org.jclouds.compute");
> Whether should also modify "org.jclouds.compute" ---> "org.apache.jclouds.compute"?
> Although not modifying it does not cause any issue.
> In addition, a suggestion is that we'd better not use hardcoding("org.jclouds.compute")
scattering in different source file. Instead, placing and grouping them into a file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message