From version < 9.1 >
edited by Krzysztof PÅ‚achno
on 2017/06/13 14:46
To version < 11.1 >
edited by Thomas Mortagne
on 2017/08/09 13:26
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.cristof_p
1 +xwiki:XWiki.ThomasMortagne
Tags
... ... @@ -1,0 +1,1 @@
1 +gsoc
Content
... ... @@ -105,7 +105,7 @@
105 105  **Searching:**
106 106  
107 107  This is the biggest deal. Possible it should work as it does currently with XWikiExtensionManager.
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>
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>>doc:extensions:Extension.Repository Module]]. 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  
110 110  
111 111  Artifactory provides multiple package search methods ([[https:~~/~~/www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-SEARCHES>>url:https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API#ArtifactoryRESTAPI-SEARCHES||style="background-color: rgb(255, 255, 255);"]]) - for the scope of project following are interesting :
... ... @@ -141,7 +141,6 @@
141 141  * 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
142 142  * 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.)
143 143  
144 -
145 145  == Update 13.06.2017 ==
146 146  
147 147  
... ... @@ -195,5 +195,13 @@
195 195   jcenter:bintray-maven:http:~/~/dl.bintray.com/bintray/jcenter
196 196   and the last two path segments will be parsed as :subject and :repo for usage in REST API calls
197 197  * accoring to this in my bintray-maven connector I will implement from scratch only searching and other stuff will be done using maven (aether) connector from xwiki-commons
198 -
199 199  )))
198 +
199 +== Update 14.06.2017 ==
200 +
201 +
202 +Discussion on riot summary
203 +
204 +* when DefaultExtensionRepositoryManager is initialized and ConfigurationExtensionRepositorySource is used to add ExtensionRepositories basing on configuration in xwiki.properties - components from extensions are not yet loaded. So BintrayMavenExtensionRepository currently cannot be configured in xwiki.properties the same way as other repositories e.g. **extension.repositories=maven:xwiki:http:~/~/nexus.xwiki.org/nexus/content/groups/public**
205 +* for the current moment configuration of connection to bintray maven repositories will be done by **custom** properties in xwiki.properties. How will they look like - it'll be announced
206 +* **bintray-repository** extension will contain JCenterBintrayRepositorySource which will be automatically processed on installment of extension (it'll be possible after fix of Thomas Mortagne in xwiki-commons - creating listener to ComponentAddEvent for role ExtensionRepositorySource). That means installment of bintray-repository extension by default will add JCenter Extension Repository. Probably it will be set up to specify special property in xwiki.properties to disable connection to JCenter
ProposalCode.ProposalClass[0]
Other URLs
... ... @@ -1,0 +1,1 @@
1 +[[http:~~/~~/extensions.xwiki.org/xwiki/bin/view/Extension/Extension%20Repository%20Connector%20-%20Bintray/>>doc:extensions:Extension.Extension Repository Connector - Bintray.WebHome]]
Status
... ... @@ -1,1 +1,1 @@
1 -s1
1 +s4

Get Connected