From version < 7.1 >
edited by Krzysztof Płachno
on 2017/06/09 15:11
To version < 8.1 >
edited by Krzysztof Płachno
on 2017/06/12 10:20
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -120,15 +120,30 @@
120 120  ** GET /api/search/prop?[p1=v1,v2][&p2=v3][&repos=x[,y]]
121 121  ** to each uploaded package (to specific version or generally package as set of all versions) - you can specify in artifactory custom properties in form of Name:value and so you can later search packages according to those properties
122 122  
123 -
124 124  Bintray provides searching facilities only by name and/or description
125 125  
126 126  * GET /search/packages[?name=:name&desc=:desc]
127 127  * but those name and description are not imported from uploaded pom, but are inserted manually whilst uploading each package to Bintray
128 128  
129 -
130 130  === Questions: ===
131 131  
132 132  * Is it important to provide searching in ArtifactoryRepositoryManager and BintrayRepositoryManager? If so how to design it's logic using described above Artifactory/Bintray api?
133 133  * 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)\\
134 134  ** Possible solution is that: on Artifactory/Bintray you may have plenty different, logically different maven repos. So prerequisite for connecting Artifactory/Bintray will be providing url to repo containing only xwiki valid extensions.
133 +
134 +(((
135 +
136 +
137 +== Update 12.06.2017 ==
138 +
139 +=== Summary of mail discussion 2 ===
140 +
141 +* at the moment we don't bother about Artifactory integration - it's less needed
142 +* I implement Bintray Connector as RepositoryManager and as Serchable (using this simply but sufficient searching options)
143 +* term Extension does not refer only to typical XWiki extensions that contain [email protected] or XWiki pages but generally all JARs, that can be later used e.g. in groovy script. Typical XWiki extension usually depend on some external JAR that need to be downloaded from Maven Central or JCenter
144 +* for the future I would be definitely useful to extend Extension Repository UI with an option to choose the repository from which we want to search extensions (e.g. search in Bintray JCenter, search in Extensions.org ect.)
145 +
146 +
147 +
148 +
149 +)))

Get Connected