xwiki-devs August 2012

xwiki-devs@xwiki.org

33 participants
69 discussions

[xwiki-devs] [VOTE] Modification to groupid for contrib projects

by Vincent Massol

hi devs, I'd like to propose a small improvement for contrib project group ids. ATM our rule is: "A generic maven groupId : org.xwiki.contrib (until the project reaches a certain size and visibility, in which case it can have its own maven group id)" ( see http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome) I'd like to change that to: "A generic maven groupId : org.xwiki.contrib.<module name> (until the project reaches a certain size and visibility, in which case it can have its own maven group id)" So for example if I have a "Mail Archive Application" I'd use the groupid: org.xwiki.contrib.mailarchive Here's my +1 for the change Thanks -Vincent

12 years, 4 months

Re: [xwiki-devs] [GSoc] XWiki Android

by sasinda rukshan

Hi Thomas, >>I restarted it and it seems ok now. Thanks a lot. Instrumentation tests that check the activities are running ok. (XWiki Android Instrumentation Tests<http://ci.xwiki.org/job/xwiki-android-client/216/org.xwiki.android$xwiki-an…> ) I disabled the base rest api tests (xwiki-android-test-rest). I'll enable them in the next commit. There should be a local xwiki test instance in jenkins server as well. Can you tell me how to access it. Tried http://ci.xwiki.org:8080. Since the test properties are directing to a local server instance 10.0.2.2:8080 it should be there. We will be running tests bottom up. i.e. low lvl rest API --> Rest API in RAL --> application layer UI components. And RAL tests will use low lvl rest API to achieve its pre-conditions and do cleanup after tests. If low level fails testing highlvl ones are not meaningful if they depend on the components that failed. ;-). Best Regards. Sasinda. > > > On Mon, Aug 6, 2012 at 1:00 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com > > wrote: > >> On Mon, Aug 6, 2012 at 9:12 AM, Thomas Mortagne >> <thomas.mortagne(a)xwiki.com> wrote: >> > On Mon, Aug 6, 2012 at 9:10 AM, Thomas Mortagne >> > <thomas.mortagne(a)xwiki.com> wrote: >> >> On Mon, Aug 6, 2012 at 8:57 AM, Thomas Mortagne >> >> <thomas.mortagne(a)xwiki.com> wrote: >> >>> On Sun, Aug 5, 2012 at 5:42 PM, sasinda rukshan >> >>> <sasindarukshan(a)gmail.com> wrote: >> >>>> Hi Thomas, >> >>>> :-) >> >>>> Also still we cannot ignore failed tests in maven android plugin. If >> a test >> >>>> fails we get Build Failure as result. >> >>> >> >>> Well that's the whole point, not sure why you want to ignore failing >> tests. >> >>> >> >>>> http://code.google.com/p/robotium/issues/detail?id=130 >> >>>> >> >>>>> Need an AVD / Device connected to Jenkins to >> >>>> run the tests. >> >>>> I think you just have to download android sdk to the jenkins server >> and use >> >>>> avd-manager to start up an avd in it. >> >>>> Not urgent ;-). >> >> >> >> Well thing is there is an AVD running and always have (since it was >> >> required by previous tests) so I don't understand exactly what's >> >> wrong. >> > >> > Here is what I have in ps aux: >> > >> > emulator -avd test-2.1 -noaudio -no-window -wipe-data >> >> Looks like it was not in a very good state actually, I restarted it >> and it seems ok now. >> >> > >> >> >> >>>> >> >>>> Still writing tests for core module. >> >>>> >> >>>> Regards. >> >>>> Sasinda Rukshan. >> >>>> >> >>>> On Sun, Aug 5, 2012 at 8:49 PM, Thomas Mortagne < >> thomas.mortagne(a)xwiki.com> >> >>>> wrote: >> >>>>> >> >>>>> On Sun, Aug 5, 2012 at 4:46 PM, sasinda rukshan >> >>>>> <sasindarukshan(a)gmail.com> wrote: >> >>>>> > Hi Thomas, >> >>>>> > Thnx. >> >>>>> > >> >>>>> >>No, you need to start one (which is not very hard with >> jetty/hsqldb >> >>>>> >>distribution) >> >>>>> > Well what about the earlier project's test server. It should have >> had >> >>>>> > its >> >>>>> > test environment setup properly. Shouldn't it?. >> >>>>> >> >>>>> Yes it should have but Chamika did not had time to finish. >> >>>>> >> >>>>> > >> >>>>> > >> >>>>> >>(but then you have the risk that you don't >> >>>>> >>have the exact same behavior) when you start the tests. You can >> look >> >>>>> >>at how >> >>>>> >> >> >>>>> >> >> https://github.com/xwiki/xwiki-enterprise/tree/master/xwiki-enterprise-test… >> >>>>> >>does it for example. >> >>>>> > Thanks. I'll make the setup, tear down methods to achieve >> preconditions >> >>>>> > and >> >>>>> > cleanup. >> >>>>> > >> >>>>> > Best Regards. >> >>>>> > >> >>>>> > On Sun, Aug 5, 2012 at 7:14 PM, Thomas Mortagne >> >>>>> > <thomas.mortagne(a)xwiki.com> >> >>>>> > wrote: >> >>>>> >> >> >>>>> >> On Sun, Aug 5, 2012 at 11:42 AM, sasinda rukshan >> >>>>> >> <sasindarukshan(a)gmail.com> wrote: >> >>>>> >> > Hi Thomas, >> >>>>> >> > >> >>>>> >> > >> >>>>> >> > This is the latest result for >> xwiki-android-tests-instrumentation >> >>>>> >> > (The >> >>>>> >> > UI stress testing test module) >> >>>>> >> > >> >>>>> >> > >> >>>>> >> > >> >>>>> >> > [INFO] *Found 0 devices connected with the Android Debug >> Bridge* >> >>>>> >> > mojoFailed >> >>>>> >> > >> >>>>> >> > >> com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.3.0(default-internal-pre-integration-test) >> >>>>> >> > projectFailed >> >>>>> >> > >> org.xwiki.android:xwiki-android-tests-instrumentation:1.0-SNAPSHOT >> >>>>> >> > sessionEnded >> >>>>> >> > >> >>>>> >> > >> >>>>> >> > Need an AVD / Device connected to Jenkins to run the tests. >> >>>>> >> >> >>>>> >> Will look at it. >> >>>>> >> >> >>>>> >> > >> >>>>> >> > Also the ....test-rest will have failures if some >> preconditions are >> >>>>> >> > not >> >>>>> >> > met. (like having a page named Blog/test2 ) >> >>>>> >> > >> >>>>> >> > Is there a testing server instance running on the Jenkins >> server?. >> >>>>> >> >> >>>>> >> No, you need to start one (which is not very hard with >> jetty/hsqldb >> >>>>> >> distribution) or mock one (but then you have the risk that you >> don't >> >>>>> >> have the exact same behavior) when you start the tests. You can >> look >> >>>>> >> at how >> >>>>> >> >> >>>>> >> >> https://github.com/xwiki/xwiki-enterprise/tree/master/xwiki-enterprise-test… >> >>>>> >> does it for example. >> >

12 years, 4 months

[xwiki-devs] [vote] improvements for the REST api

by Ludovic Dubost

While working on a prototype on a HTML5 mobile and desktop application I've hit a few limitations of the REST APIs. This is why I propose some enhancements to the current REST APIs to give more flexibility, particularly: Support for start and order parameter in queries returning large list of pages Support order parameter in page list Adding page version, author information and data information when missing Hidden documents filter activation or deactivation in REST APIs Adding pretty display of title and author names Support queries using XWQL, HQL and Lucene The rendered content should be accessible from REST apis The details of the proposal is here: http://dev.xwiki.org/xwiki/bin/view/Design/RESTApiImprovements A pull request for a prototype implementation of these requirements is available here: https://github.com/xwiki/xwiki-platform/pull/56/files#r1040052 Not everything has an implementation (hidden docs and rendered content is not implemented yet). Other are not implementing according to this specification as some comments have already been made. Particularly the following votes are required: VOTE to accept supporting "start" and "order" parameters only on queries having only one unique scope VOTE in search queries for just adding the descendent date order or add more order possibilities using order and orderdir param VOTE in page list queries for just adding the descendent date order or add more order possibilities using order and orderdir param VOTE to add page version and author fields to page and other resources VOTE for adding the additional fields with or without a parameter "pagedetails=1" VOTE for adding a parameter to show/hide hidden documents independent of user setting VOTE to add the displayTitle field with or without the pagedetails=1 parameter or with it's own parameter displayTitle=1 VOTE to add the author display names with or without the displayPrettyNames parameter VOTE for supporting the searchQuery API at the wiki level with multi wiki support at the lucene level VOTE for adding rendered content using the withrenderedcontent=1 param VOTE for having absolute URLs in the rendered content using withabsoluteurls=1 param Thanks Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

12 years, 4 months

[xwiki-devs] Lucene - external indexing

by Jones, Dan

Would it be possible to add an external directory for lucene to crawl and index? I want to be able to search wiki content, including the attachments, and also incorporate external search results as well. I was taking a look at Solr, and might try to go that route, despite being intimidated a bit. It looks extremely cool and well suited. Gracias! ________________________________ This communication (including all attachments) is intended solely for the use of the person(s) to whom it is addressed and should be treated as a confidential AAA communication. If you are not the intended recipient, any use, distribution, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately delete it from your system and notify the originator. Your cooperation is appreciated.

12 years, 4 months

[xwiki-devs] [GSOC] SOLR status evaluation

by Vincent Massol

Hi Guys, I haven't been that closely the SOLR GSOC work and it would be great to see where we stand. I'd love to know the following: * What's the status of the code; is it following our best practices (code style/passing checkstyle, unit tests, functional tests)? * What's the level of the UI in term of readiness, compared to our current one? * Do we have all the features of the current Lucene plugin (including improvements already listed in JIRA, we should verify that they can be implemented with the current code if not already there) * Could we do drop-in replacement of the current search? In general, how much work remains to be able to commit this in platform and start bundling it and using it in XE? Thanks a lot -Vincent

12 years, 4 months

Re: [xwiki-devs] [GSoC] [Request] Responsive Skin - data for extensive testing/bug finds/feature requests

by Jonathan Solichin

Hello friends, Beside yesterday's addition, these have also been addressed. I apologize if you checked yesterday and the addition was not on github/live instance, I uploaded the unchanged folder. - Lots of sections in Administration are missing the styles + some portion > of settings are displayed after the administration menu ends (Chrome) (you > need to scroll in order to see all the options, see Administration -> > Applications -> WYSIWYG Editor settings ) - .xform style for .xHint are gone (you can observe this when creating > pages/spaces) I just uploaded some stylings that makes this more eye pleasing and responsive. - The page -> Share by email feature is style-less. Styled this as well Thank you, Jonathan Solichin

12 years, 4 months

[xwiki-devs] Developer Scripting Reference Documentation Prototype

by Ludovic Dubost

Hi Developers, With the help of Andrei (from the XWiki SAS support team), we have worked on a prototype to provide a reference documentation for XWiki scripting development. We have found that new XWiki developers have difficulties getting around everything that's available in XWiki and struggle a bit to find the appropriate documentation. Providing a reference documentation would go a long way to help the developers getting up to speed faster. This is the objective of this prototype. You'll find the design page here: http://dev.xwiki.org/xwiki/bin/view/Design/DeveloperReferenceDocumentation A first prototype is available here: http://incubator.myxwiki.org/xwiki/bin/view/ScriptingReferenceDocumentation… At this point it only provides documentation for the latest version (4.1.x), but it's already quite good as we have nothing really good currently. The first step would be to find a home on xwiki.org for this documentation. It could be: http://dev.xwiki.org/xwiki/bin/view/ScriptingReferenceDocumentation/ We also need a space to store all the builds of the full javadoc of the XWiki platform for each version (I don't think using ZipExplorer is a good idea given the size of the zip of the javadoc). I suggest making them available through Apache at: http://dev.xwiki.org/docs/${version} If that's ok I can proceed to publish the prototype on dev.xwiki.org and continue on the plan listed on the design wiki. Any comments and ideas are of course welcome. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

12 years, 4 months

[xwiki-devs] XEM xmlpc using a wiki farm

by Jones, Dan

How can you use the standard XWikiXMLRPCClient to add pages or spaces to a particular wiki, when you are running the XWiki Enterprise Manager application? I have installed everything, and I've made 2 new wikis. When I log in as localhost:8080/xwiki/xmlrpc/confluence, I can add a space or page, but I can't specify which wiki to use! The url localhost:8080/xwiki/wiki/NEW_WIKI/xmlrpc/confluence doesn't hit the xml rpc servlet filter. It initializes my context to the XWiki that is the main one, not a sub-wiki. String url = "http://localhost:8080/xwiki/xmlrpc/confluence"; XWikiXmlRpcClient rpc = new XWikiXmlRpcClient( url); rpc.login( user, pass); rpc.storePage(someNewPage); Thanks! Dan ________________________________ This communication (including all attachments) is intended solely for the use of the person(s) to whom it is addressed and should be treated as a confidential AAA communication. If you are not the intended recipient, any use, distribution, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately delete it from your system and notify the originator. Your cooperation is appreciated.

12 years, 4 months

[xwiki-devs] [XWiki Devs] [GSOC] [Solr] : Advance Search and Admin module

by savitha sundaramurthy

Dear XWiki Community, I have implemented the Advanced Search Features and Admin Module for Solr Search Component. The features include: *Querying over:* 1. Plain strings ( can filtered based on space and language ) 2. Objects [ object:XWiki.XWikiUsers ] 3. Properties [ XWiki.XWikiUsers.first_name : Sa* ] 4. Attachments [ filename:gsoc.pdf ] 5. Facets [ Space, Creator, Author, Creation Date, Modification Date, Language ...] 6. Advanced search using document fields like title, name, comments, space, language etc.. 7. Multilingual Support *Admin Gui:* 1. Index based on the wiki and the available spaces. 2. All the statistics - Indexing stats - Solr details, versions - Solr configuration files and their sizes. - Component details. 3. Indexing page. - Details of indexing process in progress. For more detailed information for Advanced search refer to the link below: http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Solr+Feature+Page The detailed information about the admin module, Progress of the project, API and the recent code is given in the progress page: http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SOLRsearchcomponent Running instance of the amazon ec2 server: http://ec2-50-19-181-163.compute-1.amazonaws.com:8080/xwiki/bin/admin/XWiki… http://ec2-50-19-181-163.compute-1.amazonaws.com:8080/xwiki/bin/view/Search… -- Thanks, Savitha

12 years, 4 months

[xwiki-devs] Spreadsheet JS component

by Vincent Massol

Hi, Might be interesting to integrate: https://github.com/mleibman/SlickGrid/wiki -Vincent

12 years, 4 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs August 2012