Last modified by Vincent Massol on 2024/02/26 17:57

<
From version < 5.2 >
edited by Krzysztof Płachno
on 2017/06/09 15:08
To version < 6.1 >
edited by Krzysztof Płachno
on 2017/06/09 15:10
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -81,8 +81,9 @@
81 81  
82 82  ==== Implementation design with reference to Artifactory and Bintray API ====
83 83  
84 -Resolving extension
85 85  
85 +**Resolving extension**
86 +
86 86  * dedicated paths for downloads
87 87  * Artifactory\\
88 88  ** Path: GET /repo-key/path/to/artifact.ext
... ... @@ -91,8 +91,9 @@
91 91  ** Path: GET https:~/~/dl.bintray.com/:subject/:repo/:file_path
92 92  ** [[https:~~/~~/dl.bintray.com/cristof/xwiki-test/org/xwiki/contrib/application-office365/1.0.12345/:application-office365-1.0.12345.xar>>url:https://dl.bintray.com/cristof/xwiki-test/org/xwiki/contrib/application-office365/1.0.12345/:application-office365-1.0.12345.xar]]
93 93  
94 -Obtaining available versions of extension
95 95  
96 +**Obtaining available versions of extension**
97 +
96 96  * Artifactory\\
97 97  ** special path for obtaining versions
98 98  ** Path: GET /api/search/versions?[g=groupId][&a=artifactId][&v=version][&remote=0/1][&repos=x[,y]]
... ... @@ -102,8 +102,9 @@
102 102  ** Path: GET /search/packages/maven?g=:groupId&a=:artifactId&q=:query
103 103  ** Example: GET /search/packages/maven?g=org.xwiki.contrib&a=application-office365
104 104  
105 -Searching
106 106  
108 +**Searching:**
109 +
107 107  This is the biggest deal. Possible it should work as it does currently with XWikiExtensionManager.
108 108  How does searching in XWikiExtensionManager look like:XWikiExtensionManager utilizes Extension Repository Application API for searching: [[http:~~/~~/extensions.xwiki.org/xwiki/bin/view/Extension/Repository%20Module>>url:http://extensions.xwiki.org/xwiki/bin/view/Extension/Repository%20Module]]. Extension Repository Application doing search operation queries XWiki database (since during import of each extension to ERA - extension document page is created and extension's meta data is retrieved from pom and persisted in document xobjects in database). So the ERA search goes through extension metadata taken previously from pom properties like: <name> or <description>
109 109  
... ... @@ -125,7 +125,7 @@
125 125  * GET /search/packages[?name=:name&desc=:desc]
126 126  * but those name and description are not imported from uploaded pom, but are inserted manually whilst uploading each package to Bintray
127 127  
128 -Questions:
131 +=== Questions: ===
129 129  
130 130  * Is it important to provide searching in ArtifactoryRepositoryManager and BintrayRepositoryManager? If so how to design it's logic using described above Artifactory/Bintray api?
131 131  * How to cope with the fact, that artifactory/bintray repo may contain also other artifacts apart from Xwiki Extension. (In maven connection is not the problem - since maven does not expose searching feature and to download extension you need to specify its full id)\\

Get Connected