xwiki-devs August 2011

xwiki-devs@xwiki.org

37 participants
81 discussions

by Maxime Sinclair

Hi, I propose to host the PlantUML Macro extension (http://extensions.xwiki.org/xwiki/bin/view/Extension/PlantUML+Macro) source files on the XWiki Contrib GitHub repository. Althought this macro is only groovy code included in wiki pages, it will be easier to keep track of the different changes. In my opinion, the other hosting tools (jira, continuous build) are not needed. Is there an existing contrib project of the same kind (ie wiki macro) that I can use as a template to build the directory tree ? Thanks for your answer. Maxime Sinclair

13 years, 4 months

[xwiki-devs] The plan of GSoC project "Auto-completion in content editors" (8.15 - 8.21)

by 许凌志(Jamesxu)

Hi, Last week I have done following things: 1.Implemented the relative references for link generation 2. implemented the default suggestions for sub-trigger "attach:", "." and "@" The default suggestion for trigger "attach:" is the attachments that belongs to recently modified pages. The default suggestion for trigger "." has two different situations: 1). when "." is after "attach:" the default suggestion is the attachments that belongs to recently modifed pages under the specific space 2). when "." is not after "attach:" the default suggestion is the wiki pages under specific space. The default suggestion for trigger "@" is the attachments that belongs to the specific wikipage. 3. Re-design the interface of the suggestion box according to Marius' suggestions, and it attracts some advantages from the suggestion box of confluence wiki. Till now the Major functions for link suggestion of wiki editor has been done, here is the video of the link suggestion for wiki editor. Please see the demo video: http://www.youtube.com/watch?v=2_be-3oqgzE In next week, I will do the following things； 1. Design the image suggestion functions and discuss with mentors. 2. Test the link suggestion functions in IE, chrome, to consider the compatibility of the functions. 3. Refine the functions accroding to the review of mentors. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

13 years, 4 months

[xwiki-devs] [ANN] Twitter channel for XWiki.org

by Vincent Massol

Hi everyone, This is to let you know that you can now follow XWiki.org news using our XWiki.org tweeter channel: http://twitter.com/xwikiorg Thanks -Vincent

13 years, 4 months

[xwiki-devs] [Announcement] XWiki Enterprise 3.2 Milestone 2 released

by Sergiu Dumitriu

The XWiki development team is proud to announce the availability of XWiki Enterprise 3.2 Milestone 2, the second milestone of the XWiki Enterprise 3.2 version (see the roadmap at http://enterprise.xwiki.org/xwiki/bin/Main/Roadmap ). Main new features include: * support for user-defined, personal dashboards, * improvements to the spotlight-like search suggestions, * improvements to the extension manager, * support for arbitrary named parameters in the event stream, * ... and a few dependency upgrades and bug fixes See the full release notes at http://purl.org/xwiki/rn/ReleaseNotesXWikiEnterprise32M2 for more details. -- Sergiu Dumitriu http://purl.org/net/sergiu/

13 years, 4 months

[xwiki-devs] JavaScript unit tests

by Jerome Velociter

Hello devs, I've pushed some javascript tests for the suggest widget to a branch of xwiki-platform. I've used screw-unit (https://github.com/nathansobo/screw-unit) as test framework. The system allow to write tests such as https://github.com/xwiki/xwiki-platform/blob/f684ca0671a354f1e7476cd788a2df… ; and to run them in a test suite (a simple HTML page that runs all tests). It is integrated with xwiki-platform-web build so that whenever a test fails, the build fails. To be completely honest, I didn't do a lengthy market research to see if there would be more appropriate alternatives. Screw unit got my attention for the following reasons : * Tests are elegant and simple * You can nest feature "descriptions" (specifications) down several levels, so it's easy to have a good organization * It has a working maven integration * The result page kind of look nice (yes, that count!) I'd like to integrate them in master WDYT ? My +1 Jerome.

13 years, 4 months

Re: [xwiki-devs] Build improvement actions

by Bogdan Flueras

Hi XWiki devs, >> Hi devs, >> >> We've had a meeting with Marius, Thomas and myself and we brainstormed about what to improve in our builds and we've come up with the following actions: >> >> 1- create twitter account for xwiki.org and tweet about releases (basically tweet links to blog posts). Category: Release Process improvement. Who: Vincent Massol >> 2- Refactor distribution for installers to share more. Who: Thomas Mortagne > Will look at this one once we start the 3.3 branch. > >> 3- Check latest version of izpack. Who: Marius I can recommend you to also consider another installer framework: http://sourceforge.net/projects/cminstall/files/cminstall/v1.3.0/ It's fully extensible, modular and at the time of writing it had more features than IzPack and we have successfully used it for internal projects. It has documentation and nice tutorials, so it worths a try. >> 4- Configure nexus to cache other repos ? speed improvement. Who: Vincent Massol >> 5- Add definition xwiki remote repo to top level repos in github. Who: Vincent Massol >> 6- Define a location for passwords. Who: Thomas Mortagne > If some of the security guys out there already have some good idea > don't hesitate ;) > > Will send a mail we I come back from holidays next week. > >> 7- Publish with commons and rendering on central repo. Who: ? >> >> I've started to work on items 4 and 5 and will do 1 soon. >> >> Also I've analyzed 7 and there's only 1 external reps not available in the Maven Central Repo: >> ? ? ?<groupId>org.reflections</groupId> >> ? ? ?<artifactId>reflections</artifactId> >> >> It should be pretty easy to submit it using https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+… >> To publish our artifacts to the central repo I propose to use Sonatype OSS service, see https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+… >> >> Thanks >> -Vincent >> >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> > > -- ing. Bogdan Flueras

13 years, 4 months

[xwiki-devs] [GSOC] XWiki Android Client

by Chamika Weerasinghe

Hi all, I almost finished developing Android Client with following modules and automated testing has to be done in next week. xwiki-android-client = working android client application xwiki-android-components = user interface components for XWiki Android Development xwiki-android-rest = XWiki RESTful library for Android **xwiki-android-test-rest = Android REST library unit test module (sample test added) **xwiki-android-tests-instrumentation = UI instrumentation tests module (sample test added) xwiki-rest-model-gson = XWiki REST model for GSON(Currently not necessary) xwiki-rest-model-simplexml = XWiki REST model for Simple-xml (As a replacement for JAXB) I did the documentation on Android Client in extensions section and some final touches have to be added to it. (http://extensions.xwiki.org/xwiki/bin/view/Extension/Google+Android+Client) Issues: Testing Android Android applications or libraries cannot be tested as normal builds since they have to be tested on a device or an emulator. So logically there is no tests in maven build for Android. When we add test cases and other test related classes, Android Debug Bridge(adb) will run the tests inside a valid device/simulator and gives the test reports. Due to this reason Jenkins failed to build the test related modules with the error [ERROR] error: device not found Other modules will be built successfully*. * Best Regards, Chamika Weerasinghe

13 years, 4 months

[xwiki-devs] Removal of Repository definitions from pom.xml files

by Vincent Massol

Hi devs, I've gone ahead with the removal of repository definitions from pom.xml files. Now the only remote repo that you need to have in your maven settings is the xwiki nexus one. In order to build master (3.2-SNAPSHOT) you'll now need to update your settings.xml with: <profiles> <profile> <id>xwiki</id> <repositories> <repository> <id>xwiki-releases</id> <name>XWiki Nexus Releases Repository Proxy</name> <url>http://nexus.xwiki.org/nexus/content/groups/public</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> <repository> <id>xwiki-snapshots</id> <name>XWiki Nexus Snapshot Repository Proxy</name> <url>http://nexus.xwiki.org/nexus/content/groups/public-snapshots</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>xwiki-plugins-releases</id> <name>XWiki Nexus Plugin Releases Repository Proxy</name> <url>http://nexus.xwiki.org/nexus/content/groups/public</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </pluginRepository> <pluginRepository> <id>xwiki-plugins-snapshots</id> <name>XWiki Nexus Plugin Snapshot Repository Proxy</name> <url>http://nexus.xwiki.org/nexus/content/groups/public-snapshots</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>xwiki</activeProfile> </activeProfiles> See http://dev.xwiki.org/xwiki/bin/view/Community/Building Thanks -Vincent

13 years, 4 months

[xwiki-devs] Trying to understand slowness at deletions

by Paul Libbrecht

Hello fellow developers, At curriki, still running xwiki 1.5, we're having slowness at several places, in particular user-delete which generally takes more than 5 minutes. One of the queries that seem to take very long, from "SHOW FULL PROCESSLIST" is: | 192157 | dev | 63.241.108.241:44327 | currikidev_180_c | Query | 69 | updating | delete from xwikiproperties where xwp_name like 'editbox_%' and xwp_classtype='com.xpn.xwiki.objects.LongProperty' | and indeed I see XWikiHibernateBaseStore to contain: "delete from xwikiproperties where xwp_name like 'editbox_%' and xwp_classtype='com.xpn.xwiki.objects.LongProperty'", and "delete from xwikilongs where xwl_name like 'editbox_%'" the two queries seem to take the longest. What is the reason of these deletions? The big problem is that they contain a like clause which seems to be more developer lazyness then actual need. thanks in advance Paul

13 years, 4 months

[xwiki-devs] [VOTE] Move debian package to platform

by Thomas Mortagne

Hi devs, I started with Guillaume Fenollar last week to do an experiment on an XWiki debian package. We got something pretty nice and I cleaned it up and added some features today. You can see it on https://github.com/xwiki-contrib/xwiki-debian. With my latest commit I think it's now clean enough to be moved on https://github.com/xwiki/xwiki-platform. WDYT ? Here is my +1 -- Thomas Mortagne

13 years, 4 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs August 2011