gurkerl83 commented on a change in pull request #78:
URL: https://github.com/apache/jclouds/pull/78#discussion_r445691911



##########
File path: project/pom.xml
##########
@@ -86,6 +86,16 @@
   </scm>
 
   <repositories>
+    <repository>
+      <id>gitlab-maven</id>
+      <url>https://gitlab.com/api/v4/projects/19575612/packages/maven</url>

Review comment:
       True, in the long run, and to comply with Apache's terms, specifying a 
particular repository is not the best choice. Let's use GSON in the original, 
which is distributed through the standard distribution channel. 
   
   In any case, the consumer is responsible for whether the runtime environment 
requires a customized bundle or uses the one in the specified repository.
   
   In the context of OSGi, e.g. when creating Karaf assemblies or features, a 
specific repository can always be specified from where a critical and 
customized library is loaded.
   
   Translated with www.DeepL.com/Translator (free version)

##########
File path: project/pom.xml
##########
@@ -86,6 +86,16 @@
   </scm>
 
   <repositories>
+    <repository>
+      <id>gitlab-maven</id>
+      <url>https://gitlab.com/api/v4/projects/19575612/packages/maven</url>

Review comment:
       True, in the long run, and to comply with Apache's terms, specifying a 
particular repository is not the best choice. Let's use GSON in the original, 
which is distributed through the standard distribution channel. 
   
   In any case, the consumer is responsible for whether the runtime environment 
requires a customized bundle or uses the one in the specified repository.
   
   In the context of OSGi, e.g. when creating Karaf assemblies or features, a 
specific repository can always be specified from where a critical and 
customized library is loaded.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to