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

[xwiki-devs] Requesting rights on xwiki-contrib
by Sofiane Baloul 04 Mar '14

04 Mar '14

Sorry, I've forgot to put an email subject and to give my github ID. My github ID : sbaloul. Thank you in advance. On Tue, Mar 4, 2014 at 10:53 AM, Sofiane Baloul <sofiane.baloul(a)xwiki.com>wrote: > Hi dev community. > > I'm Sofiane Baloul, I have some experience in developing on XWiki > plateform, I would express my interest in contributing and bringing some > help on some XWiki projects especially on collaborative applications ( > https://github.com/xwiki-contrib ) at the begining. > > I've registered on jira.xwiki.org and I'm going to assigne to me some > tasks > related to XWiki Contributed Projects. > > Best regards. > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs >

2 2

[xwiki-devs] (no subject)
by Sofiane Baloul 04 Mar '14

04 Mar '14

Hi dev community. I'm Sofiane Baloul, I have some experience in developing on XWiki plateform, I would express my interest in contributing and bringing some help on some XWiki projects especially on collaborative applications ( https://github.com/xwiki-contrib ) at the begining. I've registered on jira.xwiki.org and I'm going to assigne to me some tasks related to XWiki Contributed Projects. Best regards.

1 0

[xwiki-devs] How can we add multiple values to a dbList property using velocity
by firmusoft.xwiki 03 Mar '14

03 Mar '14

Hi, I have used $obj.set to update a dbList property value. But it selected only the value I paased in the set method. All the previously selected values were unselected. Can you help me to add/update the dbList property retaining the previous selections. Thanks, Firmusoft

2 1

[xwiki-devs] Maven-based naming best practices
by coldserenity 03 Mar '14

03 Mar '14

Hello, Does XWiki have conventions documented regarding * directory layout and naming * groupId name * artifactId name * project name (briefly scanned http://dev.xwiki.org and did not find anything) Regards, Roman -- View this message in context: http://xwiki.475771.n2.nabble.com/Maven-based-naming-best-practices-tp75892… Sent from the XWiki- Dev mailing list archive at Nabble.com.

4 3

[xwiki-devs] Duplicate deps in build leading for failing build
by vincent＠massol.net 01 Mar '14

01 Mar '14

Hi guys, Several of you have been updating deps on master for the past days/weeks and this has lead to the enterprise build failing because we’re now packaging duplicate classes! See http://ci.xwiki.org/job/xwiki-enterprise/10740/consoleFull and search for "maven-duplicate-finder-plugin” Some dups: [WARNING] Found duplicate classes in [asm:asm:3.1,org.ow2.asm:asm:4.1] [WARNING] Found duplicate classes in [jdom:jdom:1.0,org.jdom:jdom:1.1.3] : [WARNING] Found duplicate classes in [org.bouncycastle:bcmail-jdk15:1.45,org.bouncycastle:bcmail-jdk15on:1.49] : [WARNING] Found duplicate classes in [org.bouncycastle:bcmail-jdk15:1.45,org.bouncycastle:bcpkix-jdk15on:1.49] : [WARNING] Found duplicate classes in [org.bouncycastle:bcpkix-jdk15on:1.49,org.bouncycastle:bcprov-jdk15:1.45] : [WARNING] Found duplicate classes in [org.bouncycastle:bcprov-jdk15:1.45,org.bouncycastle:bcprov-jdk15on:1.49] : [WARNING] Found duplicate classes in [org.codehaus.woodstox:stax2-api:3.1.1,org.codehaus.woodstox:wstx-asl:3.2.7] : [WARNING] Found duplicate classes in [org.codehaus.woodstox:woodstox-core-asl:4.1.4,org.codehaus.woodstox:wstx-asl:3.2.7] : [WARNING] Found duplicate classes in [org.restlet.jee:org.restlet:2.1.1,org.restlet.jse:org.restlet:2.0.14] : Thanks for helping fix this. -Vincent

2 1

[xwiki-devs] [Reminder] BFD#56
by vincent＠massol.net 28 Feb '14

28 Feb '14

Hi devs, Today is Bug Fixing Day #56. We're currently at -27 bugs for the 1600 days period (we were at -23 two weeks ago): http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Here's the BFD#56 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=12093 Happy BFD! -Vincent

1 1

[xwiki-devs] [Restrospective] Deprecation Fixing Day #2 issues...
by vincent＠massol.net 28 Feb '14

28 Feb '14

Guys, Last week we’ve had a deprecation-fixing day. I was worried about one thing and it seems it happened unfortunately. My worry was about breaking the build and introducing regressions. I’ve just started testing XE very quickly and I’ve noticed in the course of few minutes 2 regressions already :( * Regression 1: CSRF issue leading to a NPE when you execute XE. This wasn’t noticed for a full week! Correction was done today by GuillaumeD after I reported it (see https://github.com/xwiki/xwiki-platform/commit/bd007f28ee8c079d481c49455ceb…) Caused by https://github.com/xwiki/xwiki-platform/commit/77ebad8c6390dc4389d2de690ab5… * Regression 2: Incude macro doesn’t work anymore when using the “document” parameter. The problem is that we’re still using that.. For example in Panels.NewPage: {{include document="Panels.PanelSheet"/}}. I’ve just fixed it in https://github.com/xwiki/xwiki-platform/compare/09528b3e668a...4c2da3bf843b and https://github.com/xwiki/xwiki-enterprise/compare/96b63c62a637...7e8188d568… . Caused by https://github.com/xwiki/xwiki-platform/commit/ade4046 (caused by me!! yuck!). There are possibly more issues that we haven’t discovered yet. Thus IMO we have 2 problems here: * Fixing deprecation is something dangerous and if we don’t have automated tests for them we won’t notice regressions * We’re all not monitoring the build enough since this breakage has been lasting for 1 week. However this may be a consequence of the jenkins stability issue we’re currently experiencing. I’m not sure what we can to mitigate the risks but we need to think about something for the next time we’ll a Deprecation Fixing Day. Maybe we should only issue Pull Requests for that day and force that a committer doesn’t push the change himself and instead some other dev would need to review the code before pushing it? Any idea? Thanks -Vincent PS: Obviously the real solution is to have a stronger automated test suite but that doesn’t happen overnight and we currently don’t have a strategy for catching up with missing tests...

3 3

[xwiki-devs] [ANN] XWiki 5.4.2 released
by Guillaume "Louis-Marie" Delhumeau 27 Feb '14

27 Feb '14

The XWiki development team is proud to announce the availability of XWiki 5.4.2. This is a bugfix release. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki542 Thanks -The XWiki dev team

1 0

[xwiki-devs] [Vote] Deprecation of Prototype.js and the usage of JQuery as our default JS framework
by Ecaterina Moraru (Valica) 27 Feb '14

27 Feb '14

Hi devs, This has been brought into discussion several times so this thread is intended for this particular topic. Thanks, Caty

8 17

[xwiki-devs] A problem of secret with jobs
by Jeremie BOUSQUET 27 Feb '14

27 Feb '14

Hello, I use the Job Module [1] for an extension, and discovered something that could be a concern ... Logs of job execution are stored in permanent directory, which is good. But when using the "{}" notation for writing logs as recommended, the following is output in the "status.xml" file: <org.xwiki.logging.event.LogEvent> <level>DEBUG</level> <message>blablabla</message> <argumentArray> [[ dump of arguments ]] <argumentArray> Inside <ArgumentArray>, all attributes of the object passed as argument to the logger method seem to be dumped - not just a toString(). Currently, in my case sometimes the object I pass contain a password ... I thought I prevented this password from being output in logs by taking care of printing "***" in the related toString, but in fact this way it gets in clear in the status.xml ... I see those possibilities: a- store this password encrypted and decrypt it only when used b- have a possibility to filter what is output in this <argumentArray> (blacklist some attributes) c- only pass individual attributes as parameter and not my full object Obviously a- is the best solution in terms of security. Would xwiki bring me some helpful methods to implement it (server side) ? c- is the short term efficient workaround of course, but I would still be interested to know if there are some crypto tools provided by xwiki (well, most problematic would be to know where/how to store the secret needed for encryption/decryption in an extension, if I want to do more than some scrambling). WDYT ? Thanks, Jeremie [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Job+Module

3 6