- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] Global solution for flickering tests (was Fwd: Re : Re: How to know if a page has been reloaded after some ajax refresh)

by Vincent Massol

Hi guys, I asked the following on the webdriver forum: https://groups.google.com/d/topic/webdriver/5WdDJsiyAzc/discussion Kristian mailed me the following below which I find interesting. WDYT? Since I'm not know a prototype expert could someone knowledgable tell me if this can be done? (I've found http://www.prototypejs.org/api/ajax/responders but not sure if it's enough for us). Thanks -Vincent Begin forwarded message: > From: krosenvold <kristian.rosenvold(a)gmail.com> > Date: June 9, 2011 8:56:20 PM GMT+02:00 > To: Vincent Massol <vmassol(a)gmail.com> > Subject: Re: Re : Re: How to know if a page has been reloaded after some ajax refresh > > I have generally solved this problem by instrumenting > the application javascript ever so slightly, by exploiting > the following known facts: > > Any immediate code executed by "onClick" handlers is > guaranteed to be finished before control is returned to > the client code. > > Most popular frameworks allow you to add a global hook > that allows you to increment a counter for every request > that is started. If you add one hook that increments on > start and one that increments on ajax request termination, > your test can basically wait for a given javascript variable > to become 0. > > The nice thing about this is that if you do fancy visuals > (sliding or fading stuff that you actually intend to click in your > tests), > you can intercept "onEffectStart" and "onEffectEnd" and > increment/decrement the same counter. > > And if you chain this properly, you can have a client-side added > "onComplete" ajax handler that starts a sliding visual effect and > the counter will be guaranteed to not reach 0 before the effect is > finished. > > So our page object base class has a waitForAllEffectsToFinish > method that we actually surround to all calls to click. Our tests > went to flaky to 100% rock solid after we did this. > > Btw, you must use a counter - this won't work well enough with > a boolean. > > Kristian > > > > >

14 years, 3 months

1
1
0 0

Re: [xwiki-devs] CAS Integration + new User creation

by js

hi macro: I also need your code,thanks! -- View this message in context: http://xwiki.475771.n2.nabble.com/CAS-Integration-new-User-creation-tp62069… Sent from the XWiki- Dev mailing list archive at Nabble.com.

14 years, 3 months

1
0
0 0

[xwiki-devs] Feature to embed XWiki in external sites

by Ludovic Dubost

Hi, I've wrote a simple embed.vm template allowing to insert and XWiki page with JSX and SSX in an external site. http://jira.xwiki.org/jira/browse/XWIKI-6696 It might require some improvements but it would be great to have it as an experimental feature in 3.1. Would they be a volunteer to commit it (i'm not yet setup in git) Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

14 years, 3 months

1
0
0 0

[xwiki-devs] Fwd: [VOTE] Build Manager duty

by Denis Gervalle

Hi committers, Even if I completely understand and agree with the goal pursued, I really dislike this way of solving it. It is the responsability of all of us to keep the build stable at all time. It should be the concerns of all recent committers to check if their recent commit breaks the CI, and to fix it ASAP when needed. If someone is not ready to do so in the upcomming hours following its commit, he should simply refrain to do that commit until he can follow it into the CI. I always follow these rules (even if most of the time, I commit only stuff that I have in production on my side), and I should admit that I would have commit more without them. But this is the necessary trade-off between evolutivity and stability. Having someone to enforce such rules is admitting that some of us needs another one to remind them the best practices. This is not for me the philosophy behind Open-Source project, where everyone should do their best for the wellness of the project. So I could not admit there is a real need for this, and I really hope that everyone of us will understand the needs to move their cursor towards the stability of the build. So please guys, takes your responsibility without a need for a build policeman. Sorry, but I am -1 to do the policeman (but if I need to, I will do my duty), and I vote -0, just because I do not consider myself active enough to veto. Denis On Thursday, June 9, 2011, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: > On Thu, Jun 9, 2011 at 09:20, Vincent Massol <vincent(a)massol.net> wrote: >> >> On Jun 9, 2011, at 9:08 AM, Thomas Mortagne wrote: >> >>> On Wed, Jun 8, 2011 at 19:40, Vincent Massol <vincent(a)massol.net> wrote: >>>> Hi committers, >>>> >>>> We're having a hard time stabilizing our build (especially the functional test part, see my previous mail entitled "[VOTE] Important: Strategy to fix failing tests and stability"). Now I believe that it's going to be hard to enforce it and thus I'd like to propose a variation: >>>> >>>> * The Build Manager has the *responsibility* to get the build fixed ASAP whenever it's failing. His priority #1 during the week becomes monitoring the Build >>>> * By "Build" we mean the CI Build on ci.xwiki.org and by "failing" we mean anything that makes the build fail: tests, compilation, clirr, etc. >>>> * Every week we have a different Build Manager chosen amongst the Committers >>> >>> A week seems a bit short but in the other hand it will seems pretty >>> long for the Build Manager itself I'm sure ;) >>> >>>> * In order to fix build issues the Build Manager has several possibilities: >>>> - find out who caused the build to break and ask that person to fix it. That person cannot refuse that and must consider it his/her priority to fix it (or rollback the change that caused the build to fail) >>>> - rollback the issue that caused the build to fail >>>> - fix it himself/herself >>>> - find someone knowledgable in the failing domain and get him/her to fix the build. >>>> * At the end of the Week the Build Manager hands over his duty to the next Build Manager by contacting him/her. >>>> * We create a Build Manager Roster page on dev.xwiki.org to log past Build Managers (and possibly future ones if some have expressed the wish to be the Build Manager for a specific week). >>>> * All committers must perform this duty and take turns >>>> >>>> Since I've started doing this this week, I propose to take this role for the current week. I'm also proposing to log Caleb has having been the Build Manager for the past week since he's done a lot to stabilize the build. >>>> >>>> If the vote is passed I'll log this on the Committership page as a Committer duty (I'll also cross reference it from the Build page). >>>> >>>> Here's my +1 >>> >>> +1 >>> >>> What don't you think about designed people who broke the build the >>> most for the following week ? >> >> An interesting idea... >> >> However: >> 1) it's hard for flickering tests to find out the culprit >> 2) it's not so much a problem of breaking the build often, it's more a problem of not fixing it immediately when broken > > Sure, my really proposal was actually "design the most painful people > for Build Manager as build manager" but I wanted to find a better > metric :) > >> >> However I agree that in the Roster we could log information for the past week about who broke the build, how many flicker fixed, etc >> >> Thanks >> -Vincent >> >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> > > > > -- > Thomas Mortagne > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

14 years, 3 months

2
2
0 0

[xwiki-devs] [Proposal][UX][Usability] Usability Surveys

by Ecaterina Moraru (Valica)

Hi, I've created a proposal for two usability surveys (the fields are not functional) * General Aspects http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UsabilitySurveyGen… * Page Features http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UsabilitySurveyPage I'd like to know what do you think of the surveys' questions. Like the Page Features survey we could create additional surveys that target specific problems we have or want to learn more about them. Thanks, Caty

14 years, 3 months

1
1
0 0

[xwiki-devs] [Proposal][UX] Application Within Minutes - Proposal 2

by Ecaterina Moraru (Valica)

Hi, According to the feedback received I've made another proposal for the Application Within Minutes http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinM… Changes: - Wizard style creation - Structure in a form editor style (drag&drop, refresh preview on change) Remarks: - "Create application" could be part of the action menu's "Add" submenu and act as a wizard for the creation process. As a result we will have a space for each application that will list on it's homepage the entries livetable. The structure will be changed by entering again the wizard. Thanks, Caty References: [Proposal][UX] Application Within Minutes - Proposal 1: http://xwiki.markmail.org/thread/tvxnoabhbwfcpwmk

14 years, 3 months

6
10
0 0

Re: [xwiki-devs] Status

by 许凌志(Jamesxu)

OK, Marius, I am working for finnal exam all these days after I finishing XWIK-5560, and till now, I have finnished most of exams except one in 10th June, But it is easy, so I am going on these days. Though I am busy with final exams, I still did some prepares for my projects, I have done the following things: 1. I read the some of the source codes of wysiwyg client, found that if I want to listen to the event when user input in wysiwyg editor, I should extend the onKeyUp function in WysiwygEditor.java<https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…>which is inherited from RichTextEditorController.java<https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…>. 2. I am thinking that I can implement the auto-suggestion features without working on the GWT code because there is some APIs for me to hook in the wysiwyg editors, I can use getRichTextArea() function to get the richtextarea object, then add some listeners to it. Here is the sample code, in the callback function of the listeners, we can use getSelectionRange to get the range object of rich text area, it is the base for add auto-suggestion widget to rich text area, what do you think? document.observe('xwiki:wysiwyg:loaded', function() { var editors = Wysiwyg.getAllInstances(); var IsIE=navigator.appName!="Netscape"; for(var hookId in editors){ var editor = editors[hookId]; var richEditor = editor.getRichTextArea(); var frm = richEditor.contentWindow if(IsIE){ frm.document.onkeyup = function(){ console.debug(editor.getSelectionRange()) } frm.document.onmousedown = function(){ console.debug(editor.getSelectionRange()) } frm.document.onmouseup = function(){ console.debug(editor.getSelectionRange()) } } else { frm.document.addEventListener("keyup", function(e) { console.debug(editor.getSelectionRange()) } ,false); frm.document.addEventListener("mousedown", function(e) { console.debug(editor.getSelectionRange()) } ,false); frm.document.addEventListener("mouseup", function(e) { console.debug(editor.getSelectionRange()) } ,false); } } }) 3. For wiki editor, I think there are two most important things I should notice: a. Get the position of the input cursor, and get the context, if the cursor is in the context of "[[ link or image ]]" or "{{ macros }}", then initialized the auto-suggestion under this context, and show up auto-suggestion widget according to user input. b. Listen to the user input, and trigger the auto-suggestion widget when "[[" or "{{" are typed. I am still doing some tests now, so if you have some tips for me, please tell me. On Fri, Jun 3, 2011 at 1:02 AM, Marius Dumitru Florea < mariusdumitru.florea(a)xwiki.com> wrote: > Hi James, > > How is the GSoC work going on? Hope everything is fine. Ping me if you need > help. > > Thanks, > Marius > -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 3 months

2
5
0 0

[xwiki-devs] [PROPOSAL] Introduce XClass property reference

by Thomas Mortagne

Hi dev, I would like to introduce class property entity type and related reference and syntax separator. For the separator syntax I propose to use the same thing as object separator since you can't have both in the same reference and it's always a pain to find a new separator. Note that I'm inly talking about class property and not class since class reference is exactly the same thing as document reference I don't think we really need to have a specific one. WDYT ? -- Thomas Mortagne

14 years, 3 months

5
12
0 0

[xwiki-devs] XWiki Enterprise 3.1 Milestone 2 Released.

by Caleb James DeLisle

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The XWiki development team is proud to announce the release of XWiki Enterprise 3.1 Milestone 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is the second and final milestone in the 3.1 development cycle, you can review the changes made and bugs fixed since 3.0 by going to: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… Thanks - -The XWiki development team If you would like to download the new release now, you can using these links: - ---- XWiki Enterprise for Servers ---- xwiki-enterprise-web-3.1-milestone-2.war SHA1: 1e903ab1bb230e6823597db2c6034ecd27a4275a http://forge.ow2.org/project/download.php?group_id=170&file_id=16712 xwiki-enterprise-wiki-3.1-milestone-2.xar SHA1: c82aa727bf6a81929d91c1e9182921eac9e0ea7e http://forge.ow2.org/project/download.php?group_id=170&file_id=16713 - ---- XWiki Enterprise Standalone ---- xwiki-enterprise-installer-windows-3.1-milestone-2.exe SHA1: 9f71d54eeff3b136454d15164e94b5484815ebf3 http://forge.ow2.org/project/download.php?group_id=170&file_id=16711 xwiki-enterprise-jetty-hsqldb-3.1-milestone-2.zip SHA1: fa04ee328387ab48bbf5a8f5b2fab22e4684858e http://forge.ow2.org/project/download.php?group_id=170&file_id=16719 xwiki-enterprise-installer-generic-3.1-milestone-2-standard.jar SHA1: b93969196e73e30ffc6a65cd6033b03ebdfc1a85 http://forge.ow2.org/project/download.php?group_id=170&file_id=16710 - ---- XWiki Manager for Servers ---- xwiki-manager-web-3.1-milestone-2.war SHA1: 12f514ddd2913378b07b8b43b5654dbb6ad33ed8 http://forge.ow2.org/project/download.php?group_id=170&file_id=16714 xwiki-manager-wiki-administrator-3.1-milestone-2.xar SHA1: 9183f4f069c388ff9963e2ce877b6d75799fe4fa http://forge.ow2.org/project/download.php?group_id=170&file_id=16716 - ---- XWiki Manager Standalone ---- xwiki-manager-jetty-mysql-3.1-milestone-2.zip SHA1: 63a7d30511931fb10569fb4a82c5c42f367f9467 http://forge.ow2.org/project/download.php?group_id=170&file_id=16718 - ---- XWiki Manager Extension for XWiki Enterprise Installations ---- xwiki-manager-application-xem-3.1-milestone-2.xar SHA1: d5381326b71057182256d6aa9eec777b647739aa http://forge.ow2.org/project/download.php?group_id=170&file_id=16717 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBAgAGBQJN3LFoAAoJECYAmptlsgnWjikP/2dVAZyyWcFzh9paefuqwAXm NDvW6VA/0nHVOhMhzlvyjjpBKW4tAujQqIT2eL9dn5SG2tCygQ6lLE7r6zwFJY0t LHkOtqtK4lRiFJfu7+h/f3/yYRi3mKwht0d8z0lc74w+ACB6VKSfIdcIwh1u7Klm UXNh43lbIJNABGYapGe/aLwr3q7qFZp+sKaO3aVW5cVVzup3KnQPHV9BqgRYfqDd fWip1zZCixJ/yOOQ8VNpNRvr8mVST9pettKmDb6HlLjqvrV+qrX306zIvhcPFoKk tkHZQJaFsf9Sg8pv+U+tBVgvJIcWbf+PeAJKhIU1MPz8wc54bvDGhqBpH1VwLGUD 8W8vhzPs4rnP/w5nKWz15R4KEPBHuzUMx6oEcwPx7G7L8f+tnlAifWJLzQJP1A1U JTADeQ7GnIZ/Jg6ycWeDIIgZLOl6TrzEaDYMTWF6sXElvYfUilrdhJZ1Upbv2aul R2bWqF7Ia//FQxMGNPhwTwF7fsPExJaFQ/OEeoSumusZIl/NGc4gjrytZA2VY2t0 c3zW2CAd8JryJujFuQtbj51rYvKMnDtp3+419pkfmbs5Vg33hFKrKB30xV7nrsm5 zN9itvj7APKy3tndUph2YXaNYlXkrAe2o1B6R8gXw0M8qV/0gVmL2G0DN5d3Vu6x BG460gFTusnCwQXW8TYG =XTgI -----END PGP SIGNATURE-----

14 years, 3 months

2
1
0 0

[xwiki-devs] XWiki Enterprise 3.1 Milestone 2 Released.

by Caleb James DeLisle

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The XWiki development team is proud to announce the release of XWiki Enterprise 3.1 Release Candidate 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download Unless a new bug is discovered, this will become the 3.1 final version. This release was a stability and bug-fix only release so there are no new features. You can read about bugs fixed and translation updates by going to: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… Thanks - -The XWiki development team If you would like to download the new release now, you can using these links: - ---- XWiki Enterprise for Servers ---- xwiki-enterprise-web-3.1-rc-1.war SHA1: 0afab6a2cf62cff56c2351ce5ee5916e3be3eb60 http://forge.ow2.org/project/download.php?group_id=170&file_id=16747 xwiki-enterprise-wiki-3.1-rc-1.xar SHA1: 7286b367c735b8a667a4cb00c7b8403001027821 http://forge.ow2.org/project/download.php?group_id=170&file_id=16745 - ---- XWiki Enterprise Standalone ---- xwiki-enterprise-installer-windows-3.1-rc-1.exe SHA1: 5f71b52c823fc92474a28caebf89af56b176c6a8 http://forge.ow2.org/project/download.php?group_id=170&file_id=16750 xwiki-enterprise-jetty-hsqldb-3.1-rc-1.zip SHA1: 870553bbac3f720135780ee0b89398e38e87797f http://forge.ow2.org/project/download.php?group_id=170&file_id=16748 xwiki-enterprise-installer-generic-3.1-rc-1-standard.jar SHA1: 123309d14972c2391b1824b33a2ce20b11464005 http://forge.ow2.org/project/download.php?group_id=170&file_id=16749 - ---- XWiki Manager for Servers ---- xwiki-manager-web-3.1-rc-1.war SHA1: 0313a8d54053a61e12f1651216c1b64d9989c184 http://forge.ow2.org/project/download.php?group_id=170&file_id=16754 xwiki-manager-wiki-administrator-3.1-rc-1.xar SHA1: 4551d78e9f7b66f6cae3f10982ac69284c05386f http://forge.ow2.org/project/download.php?group_id=170&file_id=16753 - ---- XWiki Manager Standalone ---- xwiki-manager-jetty-mysql-3.1-rc-1.zip SHA1: ec611704fd298774af956beeda1a3b302b0d4744 http://forge.ow2.org/project/download.php?group_id=170&file_id=16751 - ---- XWiki Manager Extension for XWiki Enterprise Installations ---- xwiki-manager-application-xem-3.1-rc-1.xar SHA1: 71659f787ab9c1e7700aee4a2f9b0316194fab9a http://forge.ow2.org/project/download.php?group_id=170&file_id=16752 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBAgAGBQJN7dwsAAoJECYAmptlsgnWJBIQAIyTSN6wqWfmS+3H4YIZLXOJ CefTZqHFJI38inSzXgbBG3wwtS/EA3ycRoyzuqVSlsuRJ+06KmlUz75WAk0hVsrU 84Ihpq2GXioL2jvwLKNNNvX97Jk93JzNaI5Ys0gh9hZy0/9XKT1jrrvTjxCxkoES eUFAHUF9uFuOGKcazTEYF/itbc0jSMZvbVqz0NQZY7w6EpZKEeds2Xv0fVzYIq6+ GP+AocHYJ7WADajMzYfcvEUdy0SPgAMpgx+vx0k3XczPTa+eT6MgANOYKbV5COaB v5VBLvjiJaLmwDMw/c8rjLPjJzY+EAVC1Wy/DEWMswwOnw1ubjX3vUK9x99mQwgF z0tnW7fgJS+mcY5LFQlWg2FH2+bg04CwoksuOI1JNMksbCC+jQ4rBDDzwPgLUBEL HaAgjLFsF8Eg/Y8V1PdJKFKi5tmfsodqHnJ7Xv9Qrem9D97JrFgbOLr6ULz7NDus 1KDLNoBvcJC74q1Wo+F6XVf2hY1HQjXw4IqIJlYYi1ZAhNS75LasvvWl7nC+XeAo 4BIHx2vskRuMbYtY4wfElPEl9yXCtwOR7DBpzV9JjzmiKHKVuW0+ZuJGnTn/a+G1 BkWB9ttwjFQ/V9MK61GXdSbGRhobccBRwHw+trIrkBK5dOD4bBoF5or/rX/RA9xb c4l27NeRfuPKHRjKZAG9 =QIBM -----END PGP SIGNATURE-----

14 years, 3 months

1
0
0 0

[xwiki-devs] Status of XWiki Android Client

by Chamika Weerasinghe

Hi, I'm currently working on building an Android library which gives RESTful features within android device. As the first step I managed to import jaxb libraries and now I'm trying to execute them within android so that xwiki-android client will not need complete new REST library. For importing jaxb I used following dependencies in maven configuration xwiki-core-rest xwiki-core-annotations-rest wiki-core-rest-model I planed to push to the repo as soon as I build something useful in purpose of code review. Thank you, Best Regards, Chamika Weerasinghe

14 years, 3 months

3
3
0 0

[xwiki-devs] [VOTE] Important: Strategy to fix failing tests and stability

by Vincent Massol

Hi devs, Here's the situation: * We've been having a hard time releasing on time and the main issue is test stability. We lag by at least a week and we even release with failing tests, causing regressions. * It's not the role of the release manager to fix tests before releasing * It's not normal that some people spend time fixing issues caused by others and that others continue to work on the next thing they are working on. Everyone needs to help. Here's what I propose as a drastic and temporary measure till we get better: 1) It's forbidden to commit anything till all tests are passing (unit AND functional tests), unless what is committed is about fixing tests. On the exceptional case when a committer absolutely needs to commit even though tests are failing he needs to ask the permission explicitly. 2) When tests are failing, everyone should stop what they're doing and help stabilize again. We synchronize on IRC. 3) Flickering tests can be marked as @Ignore and a jira issue created to stabilize the build. 4) Release Manager creates a release branch 1 week before the release to let everyone stabilize the build On a long term we need to work on improving our CI so that functional tests are built faster. One idea is: more agents and functional tests spread on several agents. Here's my +1 to apply this now for master (3.2-SNAPSHOT leading to 3.2M1), which means not committing anything more till we have all functional tests passing. Thanks -Vincent

14 years, 3 months

5
8
0 0

[xwiki-devs] [Proposal] REST module re-organization

by Jerome Velociter

Hi, I would like to propose a small re-organization of the rest module. Currently the module is organized as follow : xwiki-platform-rest/ \_xwiki-platform-rest-model/ \_xwiki-platform-rest-server/ Where xwiki-platform-rest-model contains the JAXB bindings and generates model classes ; and where xwiki-platform-rest-server contains "everything else", being the Restlet plumbing to expose a REST application, and the REST resources and representations that makes the XWiki REST API. I'm proposing a first re-organization going towards the following structure : xwiki-platform-rest/ \_xwiki-platform-rest-model/ \_xwiki-platform-rest-resources/ \_xwiki-platform-rest-server/ Where xwiki-platform-rest-model remains the same, and where everything that is not needed to expose a functional REST system is extracted out of xwiki-platform-rest-server and into xwiki-platform-rest-resources. With this, xwiki-platform-rest-resources would become the actual implementation of the XWiki Restful API, while xwiki-platform-rest-server will be the module needed to expose any REST API from XWiki. The rationale behind this is simply to ease implementation of alternate APIs while keeping benefits from the server module which is agnostic to any API exposed. My +1 for this. If we agree I can push it early in the 3.2 cycle (in a couple of days). WDYT ? ---- Note for the future : In the future we could want to split the REST module even more. Right now some parts of the module are tied to Restlet, but resources aren't (basically everything in org.xwiki.rest.resources), and we could extract them out in a generic module while introducing a restlet module for everything Restlet (server plumbing + representations). It could for example look like this : xwiki-platform-rest/ \_xwiki-platform-rest-model/ \_xwiki-platform-rest-restlet/ \_xwiki-platform-rest-restlet-server/ \_xwiki-platform-rest-restlet-representations/ \_xwiki-platform-rest-resources/ This would ease alternative implementations based on other JAX-RS implementations (CFX, Jersey, etc.) Jerome

14 years, 3 months

1
0
0 0

[xwiki-devs] Failing tests in XEM

by Caleb James DeLisle

Does anyone know why the CreateEmptyWiki selenium test is failing in XEM tests? http://ci.xwiki.org/job/xwiki-manager-tests/1164/org.xwiki.manager$xwiki-ma… It seems that it has been failing for quite some time although the failure looks serious enough to warrant attention. If this is a "normal" failure then I propose we @Ignore it and if nobody wants to get it functioning correctly then remove it entirely since it is not proving anything now and if there isn't a regression here then it is just creating unnecessary noise. Caleb

14 years, 3 months

2
2
0 0

[xwiki-devs] [GSoC] working plan for XWiki Eclipse (May 24 - June 3)

by Jun Han

Dear all, Down below is the working plan for this week and the next one. Time Period Tasks Deliverable May 24 -- May 28 use xwiki-platform-rest-model library and replace xwiki-core-xmlrpc-model-1.4; develop RemoteXWikiDataStorage.java which uses REST instead of XML-RPC complete all the current methods in IDataStorage.java interface May 30 -- June 3 extend IDataStorage.java with new functionality and resources provided in rest-model library complete all the functionalities in rest-model library, provide test case plugin (xwiki.eclipse.test) I have a question about restlet library, is there any plan to upgrade it to v2.0+? Or we will stick with v1.1? Best regards Jun Han

14 years, 3 months

4
5
0 0

[xwiki-devs] Status of the release

by Caleb James DeLisle

Hello, To keep schedule we would need to have a release today and I am ready to release but we have some outstanding issues which need to be addressed. 1. An blocker was discovered today: http://jira.xwiki.org/jira/browse/XWIKI-6654 Multiple backslash are not properly handled in reference resolvers tmortagne is assigned so he can report back when this is finished. 2. vmassol wanted to evaluate each test to make sure that all test failures were indeed test errors and not software bugs. Unfortunately this has been severely delayed because of: http://jira.xwiki.org/jira/browse/XE-928 broken tests because jmx control port is in use 3. sburjan discovered what seems to be a blocker in the watchlist functionality http://jira.xwiki.org/jira/browse/XWIKI-6656 Unable to watch a page/space/wiki We need someone to confirm this and find out what's happening. For release I would like somebody to help me with publicity management, I will handle Wikipedia where I have an account and the announcement mail where I will use my signature but I would like somebody to help with Freshmeat, Wikimatrix, XWiki.org blog, and OW2 news. By spreading out the effort we can put a little bit more time into adding some quality to the writeup. Can I get a volunteer? Caleb

14 years, 3 months

3
2
0 0

[xwiki-devs] [UX][Proposal][XWiki5Minutes] Welcome Wizard

by Ecaterina Moraru (Valica)

Hi, As part of "The first 5 minutes experience with XWiki" project I want to propose a layered help/introduction wizard: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/XWiki5MinutesPropo… Thanks, Caty

14 years, 3 months

4
6
0 0

[xwiki-devs] [VOTE] Release XE/XEM 3.0.1

by Sergiu Dumitriu

Hi devs, Since the 3.1 release is nearing, and the trunk is already on 3.2-SNAPSHOT, I'd like to release 3.0.1, since the 3.0 branch has several bugfixes, and no maintenance release so far. http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=p… http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=p… -- Sergiu Dumitriu http://purl.org/net/sergiu/

14 years, 3 months

6
5
0 0

[xwiki-devs] [proposal] Release 3.1-RC1 on scheduled release date.

by Caleb James DeLisle

I would like to propose releasing 3.1-RC1 on the scheduled date. We (I) have lagged very badly with the milestone release dates but now is the time to get this in order. I would like to do the following: 1. Freeze on new features effective immediately. Everybody start working on stability. 2. Any test which is observed to pass and then fail must be @Ignored and a bug reported for it. 3. Release happens on Monday regardless of the state of the tests. Since the release date is upon us, I need a quick response on this. WDYT? Caleb

14 years, 3 months

6
9
0 0

Re: [xwiki-devs] [xwiki-notifications] [xwiki/xwiki-commons] 1e6f68: [release] Moving trunk to 3.2-SNAPSHOT

by Vincent Massol

How can this be done under a "jenkins" user? Who is this Jenkins? (It's a bad idea not to use a committer's name IMO since we don't know who's done the action). Thanks -Vincent On May 29, 2011, at 7:13 PM, noreply(a)github.com wrote: > Branch: refs/heads/master > Home: https://github.com/xwiki/xwiki-commons > > Commit: 1e6f6891de0d727b48cdb30aba4488d5b222a117 > https://github.com/xwiki/xwiki-commons/commit/1e6f6891de0d727b48cdb30aba448… > Author: Jenkins <build-noreply(a)xwiki.org> > Date: 2011-05-29 (Sun, 29 May 2011) > > Changed paths: > M pom.xml > M xwiki-commons-core/pom.xml > M xwiki-commons-core/xwiki-commons-component/pom.xml > M xwiki-commons-core/xwiki-commons-component/xwiki-commons-component-api/pom.xml > M xwiki-commons-core/xwiki-commons-component/xwiki-commons-component-default/pom.xml > M xwiki-commons-core/xwiki-commons-component/xwiki-commons-component-observation/pom.xml > M xwiki-commons-core/xwiki-commons-configuration/pom.xml > M xwiki-commons-core/xwiki-commons-configuration/xwiki-commons-configuration-api/pom.xml > M xwiki-commons-core/xwiki-commons-context/pom.xml > M xwiki-commons-core/xwiki-commons-management/pom.xml > M xwiki-commons-core/xwiki-commons-observation/pom.xml > M xwiki-commons-core/xwiki-commons-observation/xwiki-commons-observation-api/pom.xml > M xwiki-commons-core/xwiki-commons-properties/pom.xml > M xwiki-commons-core/xwiki-commons-script/pom.xml > M xwiki-commons-core/xwiki-commons-test/pom.xml > M xwiki-commons-core/xwiki-commons-velocity/pom.xml > M xwiki-commons-core/xwiki-commons-xml/pom.xml > M xwiki-commons-pom/pom.xml > M xwiki-commons-tools/pom.xml > M xwiki-commons-tools/xwiki-commons-tool-license-resources/pom.xml > M xwiki-commons-tools/xwiki-commons-tool-validation-resources/pom.xml > M xwiki-commons-tools/xwiki-commons-tool-xar-handlers/pom.xml > M xwiki-commons-tools/xwiki-commons-tool-xar-plugin/pom.xml > > Log Message: > ----------- > [release] Moving trunk to 3.2-SNAPSHOT > > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

14 years, 3 months

2
3
0 0

[xwiki-devs] Google Android Client for XWiki - GSOC project

by Chamika Weerasinghe

Hi devs, Since GSOC students have to start coding from today (23rd May) onwards I like to gather requirements and decide scope of the mentioned project. A short description of the project is included here<http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Androidclient> (http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Androidclient) Simply I will try to access XWiki dataset using REST API and implement Android Library. Then by using that Android Library a sample application will be developed. Before starting I would like to know all of your ideas related to this such as what should be implemented, what will you expect from an Android Library etc. So that I can get a better understand about the XWiki Android. Thank you all, Best Regards, Chamika Weerasinghe

14 years, 3 months

3
9
0 0

[xwiki-devs] Fail to build XWiki from GitHub

by Bogdan Flueras

Hello devs, Today I've cloned the xwiki - {platform and commons} modules from GitHub. 1) When I tried to build the platform module it gives me a strange error. See it at http://pastebin.com/HMTLkc76. It's xwiki-commons-tool-xar-handlers.3.1-SNAPSHOT dependency that is not fetched correctly. In an attempt to fix it, I've cleaned my local repo and forced updates via mvn .. -U command line option. So after getting the same error message [see above], I've inspected my repo and the following files were found: resolver-status.properties xwiki-commons-tool-xar-handlers-3.1-SNAPSHOT.jar.lastUpdated xwiki-commons-tool-xar-handlers-3.1-SNAPSHOT.pom.lastUpdated All these files contain the same content: #NOTE: This is an internal implementation file, its format can be changed without prior notice. #Thu May 26 16:37:28 CEST 2011 maven-metadata-xwiki-plugins-snapshots.xml.error= maven-metadata-xwiki-plugins-snapshots.xml.lastUpdated=1306420648539 maven-metadata-xwiki-plugins-externals.xml.lastUpdated=1306420648539 maven-metadata-xwiki-plugins-externals.xml.error= 2) I've also tried to clone the xwiki-trunks module and to build it, but I think there is a little inconsitency with respect to directory layout( SVN layout). See the <parent> section where the relative path is "commons" instead of xwiki-commons. Of course that I can go to the problematic submodules and further pinpoint the problem (this is what I will do now), but personally I would like to do nothing more than a simple "mvn install" at the root of the main module. Thanks and looking forward hearing from you, -- ing. Bogdan Flueras

14 years, 3 months

2
6
0 0

[xwiki-devs] [proposal] Remove fix-for version from all issues fix-for 3.1-RC1.

by Caleb James DeLisle

We have 17 unresolved issues which are labeled as needed to be fixed for 3.1-RC1. http://jira.xwiki.org/jira/secure/IssueNavigator!executeAdvanced.jspa?jqlQu… Some of these issues are relatively new and others are quite old and have had their fix-for version advanced at each release. In my opinion setting a fix-for version is equivalent to making a promise to produce a fix by a certain date. To make a promise and fail to keep it is bad but making a habit of periodically breaking promises and making new ones is far worse. Since I have proposed a freeze on new features I would like to propose removing these fix for versions. WDYT? Caleb

14 years, 3 months

4
6
0 0

[xwiki-devs] questions about XWiki-5820

by Jun Han

Dear all, Regarding REST API for XWiki, Source codes are in xwiki-trunk/xwiki-platform/xwiki-platform-core/xwiki-platform-rest. Test codes are in xwiki-trunk/xwiki-enterprise/xwiki-enterprise-test/xwiki-enterprise-test-rest. I hope I am looking at the correct places. XWiki-5820 is related to adding an endpoint for providing a rendered version of the page. Does REST API need to invoke xwiki-rendering library in order to render the html content? The current implementation will return various resources, (e.g., pages, tags, attachments), and produce XML responses in most cases. In XWiki-5820, only page resources will be rendered, right? A straight-forward way may be to add additional end point (getPage and getPageInHTML), and they will be invoked according to different Accept http headers. It would be great that an example can be given to show the expected input and output. Best regards Jun Han

14 years, 3 months

3
9
0 0

[xwiki-devs] [Discussion] Dashboardification of the Main.WebHome

by Luca Anca

Hello devs, as suggested before, I would like to make the main page of the wiki a full dashboard, namely to relocate the welcome message in a gadget so that the type of page of the main page is more clear. See this two screenshots about how it could look (one is with default style, other is with panels style). http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/WikiDashbo… http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/WikiDashbo… (also http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/MainDashbo… ) if you want to import it in your own wiki and play with it. I want to discuss the following points now: 1/ is the title "Wiki Dashboard" ok for the main page of the wiki? 2/ Is the welcome message visible enough, is it accessible to users and explanatory about what the page is about and what they could do next? 3/ what would be the relation now with the old Main.Dashboard page, which, as you can see in the quick links panel, is a "Wiki Dashboard" itself? Should it be the same page? if so, is it ok that the welcome message appears on the wiki dashboard? if they're not the same page then it's a bit strange that they're called the same but 2 different pages... Should we rename one? Technically the welcome message is written in a new page, Main.Welcome, and then included in a gadget in the dashboard. This page can be translated for getting the message in different languages. WDYT? Thanks, Anca

14 years, 3 months

5
9
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs