xwiki-devs June 2012

xwiki-devs@xwiki.org

35 participants
107 discussions

[xwiki-devs] [Brainstorming] Colocated Functional Test (CFT)

by Vincent Massol

Hi devs, I've started an experiment to have colocated functional tests (CFT), which means having the functional tests located where the functional domain sources are located instead of in XE. For example for the linkchecker module we have the following directories: xwiki-platform-linkchecker/ |_ xwiki-platform-linkchecker-refresher (JAR) |_ xwiki-platform-linkchecker-ui (XAR) |_ xwiki-platform-linkchecker-tests (functional tests) The rationale for this was: * Have everything about a functional domain self-contained (source and all tests) * Making it easy to run only tests for a given functional domain * Move page objects to the functional domain too Here are some findings about this experiment: A - It takes about 30 seconds to generate the adhoc packaging and start XWiki. This would be done for each module having functional tests compared to only once if all tests were executed in XE B- The package mojo created to generate a full packaging is quite nice and I plan to reuse it in lots of other places in our build (distributions, database, places where we need XWiki configuration files) C- We will not be able to run platform builds in Maven multithreaded mode since it would mean that several XWiki instance could be started at the same time on the same port D- The colocated functional test module Solutions/ideas: * One idea to overcome A and C would to have the following setup: ** Keep functional test modules colocated but have them generate a test JAR ** Still allow running functional tests from the colocated module (this makes it easy to verify no regression was introduced when making changes to a given domain) ** Have functional tests in XE depend on the colocated functional test module JARs and configure Jenkins to run all functional tests from XE only * Another solution to overcome C is to auto-discover the port to use in our XWiki startup script (and save it in a file so that the stop script can use it). I think the first proposal is the best one and brings the best of the 2 worlds. WDYT? Thanks -Vincent

12 years, 1 month

Re: [xwiki-devs] [VOTE] Move history when moving stuff from repositories of "xwiki" organization

by Denis Gervalle

Le 9 mars 2012 16:59, "Vincent Massol" <vincent(a)massol.net> a écrit : > > > On Mar 2, 2012, at 10:06 AM, Denis Gervalle wrote: > > > On Wed, Feb 29, 2012 at 08:19, Vincent Massol <vincent(a)massol.net> wrote: > > > >> Hi, > >> > >> On Feb 28, 2012, at 12:17 PM, Thomas Mortagne wrote: > >> > >>> Hi devs, > >>> > >>> Since I plan to move some stuff from platform to commons I would like > >>> to know what you think of the history in this case. > >>> > >>> Pros including history: > >>> * can access easily the whole history of a moved file. > >> > > > > This is really an important matter, especially for those joining the > > project. When you follow XWiki from "outside", and not in a continuous > > manner, the history is of great value to understand why stuffs are like > > they are, and what you may do, or not when moving forward. > > The history is not lost. If you do a join (all active repos) you still have it. I do not know what you means by joining all repos, but I would be surprise to see the IDE find its way between them. I even wonder how it could be possible. > > >> But sometimes > >>> changing packages etc make too much difference for git to see it's > >>> actually the same file so you loose it anyway. > >> > > > > If you simply change the package name, and nothing else, it is really > > unlikely to happen. > > > > > >>> > >>> Cons including history: > >>> * double the history which make tools like ohloh indicate wrong > >> informations > >> > > > > Sure, the stats will be broken, but what is the matter. This is not > > cheating, just a misfeature in Ohloh, since the commit are just identical, > > something they may notice. IMO, this is the matter of the statistical tools > > to improve that. > > Can you tell me how to implement this because right now my GitHub tool doesn't do that and I don't know how to do it? If I had to implement it, I will probably use some hashing method to be able to recognize similar commits, since there effectively no link between them. But my main remarks that the statistics are broken, not the way we use git. > > >>> * it's a lot easier to move without history > >> > > > > There should be some tools to improve that point or we may write one, once > > for all. So this is not a real cons either. > > It's really hard to copy history in Git. It's almost impossible to do it right. You have to remember the full history and it's just too hard. I would be really disappointed to have to conclude that. There is probably some edge cases, but most of the time there is clever work around. You have to talk to Sergiu :-) > > >>> WDYT ? > >>> > >>> Even if it was looking a bit weird to me at first I'm actually +1 to > >>> not move the history in this case. > >> > >> +1, FTR I'd be -0, close to -1 to move it. If/when the source repository > >> is removed for one reason or another, then we might want to import its > >> history somewhere. > >> > > > > Seems we are really opposite on this one, since I am close to -1 to not > > move it. > > Sorry but that's the current practice :) It's also the easiest one. Until we have Git, there were no better way. This does not means that we should not improve our practice. By the way, it was not my thread, if Thomas has asked, it means that the current practice was not so current. > > > Statistics is really less valuable IMO, it is a small interest compare to > > code history, that I have use a lot, especially when I have join the > > project and follow sparingly. > > I can say exactly the same thing as you said above. It's just a question of tools since the history is not lost. It's still there in our active repos. There is absolutely no link between these histories. It is not only a question of tools. Moreover, requiring querying all active repositories to have a proper history completely defeat the purpose of having separate repositories. I do not see the comparison with my remark above. Git has been made for versionning, not for statistics, it is not my fault. > > > So the general rule for me is: Copy history when the source repository is > >> removed/deleted/not used anymore. > > How many times have you done this? I believe 0 times since I don't think you'd be so much in favor if you had tried it. I suggest you try it a few times on your own projects first :) It's really hard to do it right and very time consuming. When I have copied the security component from contrib, I have done so. I hope that I am not alone. And, frankly, it was not so hard, compare to the advantage you have. > > > You never know what will happen to a repository in the future, so this > > rules is somewhat a hope on the future, no more. And remembering that we > > may loose history if we do some change in the old repository, is for me > > like hoping you will remember my birthday ;) > > I don't agree with this at all. Again we're not loosing history. If a repo is removed then its history is copied I agree about that. I would like to know how you do that after the facts? > > >>> Eduard was proposing to include in the first commit of the new > >>> repository the id of the last commit containing the files (basically > >>> the id of the parent of the commit deleting the files) in the old > >>> repository so that it's easier to find it. I'm +1 for this. > >> > > > > But you loose all the benefits of the IDE tools that brings history of a > > selection automatically and that are really useful. > > A huge majority of xwiki's history is already lost to IDEs (when we moved from SVN) even though the SVN history was moved. Even Git itself doesn't follow the history when you move stuff around. Said differently it's alwasy possible to find the history but the IDE and "standard" tool don't follow it. It does so far better since we move to Git and it is really a valuable tool. Do you means that because in a few case, the history may be broken, that we should not try to have it as complete as possible? > > > Moreover, if the history is rewritten due to a change in structure later, > > the hash may be broken. > > Not sure I understand this one. In Git, nothing is fully permanent, that is all I say. > > You should really measure the cost of what you propose Denis. It's really hard to do. Prove me that is more cost than the one newcommers has to enter the project. Maybe you do not value history so much because you have by your own experience of the project a good knowledge of what happen in the past. When I dig in some code, I always found history valuable to understand why that piece of code is not written the way I may have expected and why I should not got that way. If Thomas conclude it is too hard to be done, and not just some developer's lazyness, I would understand; but I do not agree that it should not be done just because it breaks statistics or we think it is too hard. This is why I suggest a tools that do it once for all. I would be really disappointed of Git if we had to conclude this. Thanks, Denis > > Thanks > -Vincent > > > So having a broken history is hardening the task of those who want to > > participate. A great value compare to the statistics IMO. > > > > -- > > Denis Gervalle > > SOFTEC sa - CEO > > eGuilde sarl - CTO > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs

12 years, 1 month

[xwiki-devs] [Proposal] XWiki Days every month?

by Vincent Massol

Hi devs, We've had several special days in the past: * Deprecation day ** 26 April 2012: http://markmail.org/thread/c5oytyvgw6fcimqq * Bug fixing days: ** 11 june 2008: http://xwiki.markmail.org/thread/oyfxis3umqrvutxm ** 18 June 2008: http://xwiki.markmail.org/thread/brfx6gme37vgr3m5 ** 25 Jun 2008: http://markmail.org/message/nrobo3x4ppgssklk ** July 2008: http://xwiki.markmail.org/thread/mn5veblndbtgcsm5 ** 10 Feb 2011: http://xwiki.markmail.org/thread/rierrb2wk72dkpqy and result http://www.xwiki.org/xwiki/bin/view/Blog/BugFixingDayFebruary2011 * DocHour days: ** 5 March 2008: http://xwiki.markmail.org/thread/dyypju5dn23wkwr2 I think it's a good concept and I'd like to propose that we regularly (once every month?) have an XWiki Day. Ideas for such days: * Bug fixing day: Reduce bug count * Doc day: improve xwiki.org * Deprecation day: reduce # of deprecated calls. Around 1700: http://nemo.sonarsource.org/drilldown/violations/XWIKI?&rule=squid%3ACallTo… * Violation day: reduce # of violations. 10274 right now: http://nemo.sonarsource.org/drilldown/violations/XWIKI * Javadoc Day: Add missing javadocs in our code and remove checkstyle excludes * Code Coverage Day: Add as many tests as possible (unit and functional) * Broken Links Day: fix as many broken links as possible on xwiki.org. To find them is easy: we just need to enable the IRC Link Checker botlet and wait on IRC to get them! I propose that whenever a day is over, we send a mail with the Date and Topic for the next day and it has to be about 1 month from the date of the mail. To get this started I volunteer to be responsible for sending Day emails for now, unless someone else is interested to do this. WDYT? Thanks -Vincent

12 years, 3 months

[xwiki-devs] Backup of Xwiki via Command Line

by echocoder

Is it possible to backup the Xwiki via command line using the export feature? -- View this message in context: http://xwiki.475771.n2.nabble.com/Backup-of-Xwiki-via-Command-Line-tp757998… Sent from the XWiki- Dev mailing list archive at Nabble.com.

12 years, 3 months

[xwiki-devs] [UX][Proposal] Improvements on editing welcome block

by Ecaterina Moraru (Valica)

Hi, I have received numerous complains that simple users have problems in editing the content and title of the Welcome block ("Welcome to you wiki" gadget) from the homepage. There are multiple factors that influence the editing of that particular gadget and that make the job especially harder for beginners. One of these factors is that the gadget used to display the Welcome content is an "include" gadget. Without some custom actions for the gadget that would let the user navigate to the included page or without some auto-redirect mechanism, the simple users have difficulties in understanding where the welcome content is coming from and what actions they need to do in order to edit that content. Also the "include" macro has a lot of advanced properties that can be scary and confusing for users (context, reference, section, type, etc.). My proposal is to create a new "text" gadget. This gadget will be very-very simple and will contain just the gadget's title and the gadget's content. Its only purpose will be to let users add textual information inside a dashboard. http://incubator.myxwiki.org/xwiki/bin/view/Improvements/EditingWelcomeMess… Right now we have specialized gadgets for HTML content, velocity content, code in general, boxes, success messages, etc. but no way to put just a simple text inside the dashboard. Let me know what you think. Thanks, Caty

12 years, 3 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] XWiki WebDAV for MSOffice read-write mode

by bouderbala＠nearbee.com

Hello all, I would like to use XWiki WebDAV for editing MSOffice documents online To do this in read-write mode, we must configure XWiki WebDav on ROOT. Instead of opening the document from: http://myserver.test/xwiki/webdav/spaces/test/msoffice/Bonjour.docx we must open it from: http://myserver.test/spaces/test/msoffice/Bonjour.docx This is what I did: - I am running Tomcat 7 / XWiki Enterprise V2.6 - I renamed the ROOT context xwiki - I changed the servlet-mapping like this <servlet-mapping> <servlet-name>webdav</ servlet-name> <url-pattern>/*</ url-pattern> </ servlet-mapping> Now I can't even request the document http://myserver.test/spaces/test/msoffice/Bonjour.docx I have response: HTTP Status 400 - Bad Request Is there any solution XWiki WebDAV to open MSOffice in read-write mode ? Thanks in advance

12 years, 5 months

[xwiki-devs] Pretty Time library

by Vincent Massol

Could be useful: http://ocpsoft.com/prettytime/ Idea of usage: For ex we could use that to show the last modified document dates for dates in the past week (for ex): "Document created 2 days ago" It's in the maven central repo and it's under LGPL -Vincent

12 years, 5 months

[xwiki-devs] [GSOC] Basic Solr Implementation

by savitha sundaramurthy

Hi All, I have come up with the basic Solr Search Component. Have included features such as hit highlighting. You can find a running instance of the component here. http://ec2-50-19-181-163.compute-1.amazonaws.com:8080/xwiki/bin/view/Search… Below is the link to the documentation and the progress of the project. http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SOLRsearchcomponent API http://dev.xwiki.org/xwiki/bin/view/Design/SOLRSearchIntegration Basic multi lingual support, and basic facet search are in progress to be implemented for the coming week. Kindly give your suggestions. -- Thanks a lot, Savitha.s

12 years, 5 months

[xwiki-devs] [Proposal] Roadmap for XWiki 4.2

by Vincent Massol

Hi devs, It's Roadmap time again, this time for 4.2 :) We've brainstormed internally at XWiki SAS and here's below what we've come up with and that we are proposing for the 4.2 roadmap. Could all devs interested in participating please reply to the list below and mark what they're interesting in implementing (and assign themselves to jira issues). You can also propose other stuff from what is listed of course (what's listed is what is important from the POV of XWiki SAS). In this case please add them to this thread so that they can then be added to the Roadmap page. Dates ===== * 4.2M1: 9 July 2012 * 4.2M2: 6 Aug 2012 (Note: the whole XWiki SAS team goes to a 10 day seminar from 19 to 28 July and thus dev speed will be reduced during this period, this is why I've put 4 weeks instead of the usual 3). * 4.2RC1: 20 Aug 2012 * 4.2Final: 27 Aug 2012 Large features ============ * Continue the Extension Manager and finish implementing the following use case which was initially planned for 4.1: "be able to upgrade an xwiki farm in a few minutes" + bug fixes/polishing. Proposed devs: Thomas and Marius for the UI - TODO: Thomas to create the different jiras required to finish this task and list them here in the roadmap * Usability and more specifically home page experience improvement. Proposed devs: Caty and JV. - TODO: Caty to create the different jiras required to implement this task and list them here in the roadmap * AWM improvements: user fields, suggests, validation, automated naming of pages, doc title + doc content, app generation quality. Proposed devs: Marius + Sergiu for the autogeneration of page names (which was supposed to be done in 4.1 and slipped). - TODO: Marius to create the different jiras required to implement this task and list them here in the roadmap Specific JIRAs sorted by order of priority =============================== Most important jiras are listed first. * Be able to rename a space from the UI (also Rename Application) XWIKI-6722 * Add option to 'show more entries' on displaying the Activity Stream XE-748 * tag suggest feature does not work if Main.WebHome is not saved with programming rights XE-539 * PDF Export when CDATA section (generated by Livetable) XWIKI-7871 * Generate and register a document bundle for the application XWIKI-7371 (NOTE: This is the l10n module) * Improvements on Statistics * Improvements on Dashboard editing XWIKI-7681 * Auto-create Space.WebHome when creating a page in an underfined space XWIKI-5399 * The autosuggest widget should use the first_name and last_name instead of the user profile name XWIKI-7696 * Occasionally the livetable fails to load on index pages XE-844 * Add more/all configuration parameters in the wiki administration (activate Stats for a given wiki) XWIKI-7066 * Applications entry point XWIKI-7927 * Log-in automatically on registration XWIKI-6892 * Auto-suggest doesn't work for global users XWIKI-6207 * Import / export perf improvement * Wrong date should not be accepted (in poperties of type Date) XE-1103 * "When a ssx / jsx is included manually with prefixed full name and also * included with ""always on this wiki"" then it is actually included twice" XWIKI-7702 * Tracking Active Installs * Messages sent to global users from a subwiki are not displayed in the global user's profile but only in subwiki's activity stream. XWIKI-6668 * XWiki is not able to automatically start OpenOffice daemon on Windows Server XWIKI-7510 * Cannot filter using "/" on a Date column in the livetable XWIKI-5889 * Change stylesheet and javascript extension filename when a modification is done on those XWIKI-6073 * Problems displaying the correct attachment version when using a proxy XWIKI-6569 * Modifing attachments when viewing only attachments for a page with ?viewer=attachments redirects to the Document#Attachments url instead of the ?viewer=attachments XWIKI-7719 * PDF Export of document created with app within minutes only displays values of fields (no labels) XWIKI-7868 * Suggest improvements * New XWiki Syntax Guide XE-880 * Importing does not delete attachments from previous version XWIKI-7587 * Mobile Skin * Attachment storage, better handling XWIKI-7587 * Profile Improvements XWIKI-6307 * Add Required and Hint meta properties for class fields XWIKI-7373 * XWiki automatically connect to an external openoffice daemon XWIKI-7509 * Page creation date should be the date of the installation XWIKI-7058 * When using filesystem attachments with attachment versioning disabled, deleted attachments are duplicated on the hard disk. XWIKI-6951 * Deleted attachments duplication in recycle bin while File Storage is on XWIKI-6917 * Performance of blog category panel is still not enough XWIKI-6363 * Better placement of the documentation link XE-1031 Investigations =========== - Home Page Changes Proposals - Caty - 4.x Skin - Caty - Title Handling: Decide page name vs title, make title mandatory, make title readable when using scripting, etc - Caty/Vincent - More configuration options available from Administration - Caty/Vincent We also need a RM for 4.2. Volunteers welcome! :) Thanks -Vincent

12 years, 5 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs June 2012