xwiki-devs August 2012

xwiki-devs@xwiki.org

33 participants
69 discussions

[xwiki-devs] 4.2 Milestone 3 is planned for today

by Marius Dumitru Florea

Hi devs, Do you have unfinished work that needs to be included in this release? I know JV has to move the wiki components module from contrib to platform. Anything else? Also, are there any blocking issues? Otherwise, I'd like to start the maven release in the afternoon. I'll take care of the failing tests in the mean time. Thanks, Marius

12 years, 3 months

[xwiki-devs] [vote] Move wiki components module from contrib to platform

by Jean-Vincent Drean

Hi, I've been working on UI extensions lately and those extensions are implemented as components. To be able to have components both defined from java code and from wiki documents I've worked on the xwiki-platform-component-wiki module started by Jerome a while ago. The initial design is described here: http://dev.xwiki.org/xwiki/bin/view/Design/WikiComponents In addition the module allows other modules to easily synchronize java components with content coming from XObjects. To do so you need to implement WikiComponent [1] and WikiComponentBuilder [2]. Then a manager will automatically unregister/register your components whenever it's required: when the wiki starts, when a document is updated, deleted, etc. In order to commit the UI extension module I need xwiki-platform-component-wiki to be moved to platform. Here's my +1 [1] : https://github.com/xwiki-contrib/xwiki-platform-component-wiki/blob/master/… [2] : https://github.com/xwiki-contrib/xwiki-platform-component-wiki/blob/master/… -- Jean-Vincent Drean, XWiki.

12 years, 3 months

Re: [xwiki-devs] XEM xmlpc using a wiki farm

by Jones, Dan

Thank you Mr. Mortagne! Keep up the great work. I will go with the 2nd option and use the REST api. ________________________________ 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, 3 months

Re: [xwiki-devs] [GSoC] Pencils down, submit your evaluations to Google, and your status to the XWiki Community

by Jonathan Solichin

Hello Jerome, Vincent, friends Good idea. The extension page is here: http://extensions.xwiki.org/xwiki/bin/view/Extension/xorange wdyt? Thanks again, Jonathan Solichin > On Tue, Aug 21, 2012 at 11:43 AM, Jonathan Solichin <jssolichin(a)gmail.com>wrote: > >> Hello Sergiu, friends, >> >> First of all, thank you once again for this wonderful opportunity to work >> with the xwiki team. It has been a learning experience that will no doubt >> change my future in programming and open source. Like Sasinda said, all the >> support and help throughout the project have been enormous. I think all of >> us GSOC students will agree that it was one of the most interesting and >> useful summer we ever had. >> >> Thank you for the reminders to submit the code and evaluation. >> >> The XWiki team made a great impression, and in my opinion, a very good >> face for the open source community. I hope to be able to contribute more >> and continue support/development on the skin as it comes up. Like Sasinda I >> will definitely try to come back in my free time >> >> Status: >> The overall design and implementation goals of the skin is, in my >> opinion, achieved (note: as planned we did not use foundation as the base >> of our skin as the GSOC proposal stated). The skin works on a plethora of >> browsers (tested in ie7-9, opera, ffx, chrome, and safari. devices: g2x, >> nokia 710, nexus7, bb curve) and responds to size changes. Due to the >> limitation of some browser, there will be slight deviations, but none >> should impact the function of the skins. >> >> There are some minor differences than those of the design plan. For >> example the apps are not skinned as they were designed in the design plans. >> After working on the skin, I did not think that was priority since there >> are so many apps, that it wouldn't be the most fruitful use of the gsoc >> time to skin one. I'll try to work on these in my free time. The idea to >> create a 2nd configuration page for the skin was scraped since it was >> deemed to not be efficient. >> >> In general, the skin is usable and "complete". I think to truly complete >> the skin, we would need users to try and use the skins since I did not have >> the time, and I think XWiki is too expansive for me to test every use case >> scenario anyway. Future explorations would be how to make the skin >> functions more efficient. >> >> Thank you once again for the opportunity, do let me know of anything you >> would like me to do. Thanks Asiri for dropping by and dropping us the hint >> ahaha. >> Thank you for all those involved in making GSOC happen, from Caty, >> Eduard, Sergiu, Vincent, Thomas and anyone who I missed. Finally, last but >> not least, Thank you especially to Jerome, for mentoring me through out >> this time. >> >> Best, >> Jonathan Solichin >> > >

12 years, 3 months

Re: [xwiki-devs] [GSoC] Pencils down, submit your evaluations to Google, and your status to the XWiki Community

by Jonathan Solichin

Hello Sergiu, friends, First of all, thank you once again for this wonderful opportunity to work with the xwiki team. It has been a learning experience that will no doubt change my future in programming and open source. Like Sasinda said, all the support and help throughout the project have been enormous. I think all of us GSOC students will agree that it was one of the most interesting and useful summer we ever had. Thank you for the reminders to submit the code and evaluation. The XWiki team made a great impression, and in my opinion, a very good face for the open source community. I hope to be able to contribute more and continue support/development on the skin as it comes up. Like Sasinda I will definitely try to come back in my free time Status: The overall design and implementation goals of the skin is, in my opinion, achieved (note: as planned we did not use foundation as the base of our skin as the GSOC proposal stated). The skin works on a plethora of browsers (tested in ie7-9, opera, ffx, chrome, and safari. devices: g2x, nokia 710, nexus7, bb curve) and responds to size changes. Due to the limitation of some browser, there will be slight deviations, but none should impact the function of the skins. There are some minor differences than those of the design plan. For example the apps are not skinned as they were designed in the design plans. After working on the skin, I did not think that was priority since there are so many apps, that it wouldn't be the most fruitful use of the gsoc time to skin one. I'll try to work on these in my free time. The idea to create a 2nd configuration page for the skin was scraped since it was deemed to not be efficient. In general, the skin is usable and "complete". I think to truly complete the skin, we would need users to try and use the skins since I did not have the time, and I think XWiki is too expansive for me to test every use case scenario anyway. Future explorations would be how to make the skin functions more efficient. Thank you once again for the opportunity, do let me know of anything you would like me to do. Thanks Asiri for dropping by and dropping us the hint ahaha. Thank you for all those involved in making GSOC happen, from Caty, Eduard, Sergiu, Vincent, Thomas and anyone who I missed. Finally, last but not least, Thank you especially to Jerome, for mentoring me through out this time. Best, Jonathan Solichin

12 years, 4 months

[xwiki-devs] Maven Repository problem (org.restlet.ext.jaxrs)

by Fernando Ferreira

Hi all! I was trying to build XWiki from sources (xwiki-commons) with a fresh new Maven installation (empty local repository) and found a problem with the * org.restlet.ext.jaxrs* artifact (2.0.14). This was the build error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project xwiki-commons-extension-repository-xwiki: Compilation failure: Compilation failure: [ERROR] /data/Repository/XWiki/xwiki-commons/xwiki-commons-core/xwiki-commons-extension/xwiki-commons-extension-repositories/xwiki-commons-extension-repository-xwiki/src/main/java/org/xwiki/extension/repository/xwiki/internal/XWikiExtensionRepository.java:[38,23] package org.restlet.data does not exist [ERROR] /data/Repository/XWiki/xwiki-commons/xwiki-commons-core/xwiki-commons-extension/xwiki-commons-extension-repositories/xwiki-commons-extension-repository-xwiki/src/main/java/org/xwiki/extension/repository/xwiki/internal/XWikiExtensionRepository.java:[116,47] package MediaType does not exist A little above it i saw this: Downloading: http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest… [WARNING] Checksum validation failed, expected <!DOCTYPE but is 97d021087f5852baf8cc9deca20825b1bf42bbaf for http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest… [WARNING] Checksum validation failed, expected <!DOCTYPE but is 97d021087f5852baf8cc9deca20825b1bf42bbaf for http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest… Downloaded: http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest… KB at 1.6 KB/sec) [WARNING] The POM for org.restlet.jse:org.restlet.ext.jaxrs:jar:2.0.14 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details Downloading: http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest… Downloaded: http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest… KB at 47.0 KB/sec) It seems the org.restlet's repository was down for maintenance at the time Nexus fetched the files. The POM ( http://nexus.xwiki.org/nexus/content/groups/public/org/restlet/jse/org.rest…) has this inside: You caught us doing a little maintenance. We're sorry that you can't access your community right now. ... With a problem like this, would something like adding the org.restlet's repository to my settings.xml do the work? I'm in no hurry anyway, i can wait for the repository... ;) If there's anything else i can do, just drop me a message! Thanks, Fernando

12 years, 4 months

[xwiki-devs] [Proposal] Failing a module's build if under a given TPC threshold

by Vincent Massol

Hi devs, Each java module has a current TPC level (Test Percentage Coverage), be it 5% of 90%. As part of improving XWiki's quality, the idea is that future commits in this module shouldn't lower the module's quality. One easy way to ensure this is to measure the current TPC level and make the build fail whenever the build is under this TPC threshold. This means that if you commit code that has less tests average than what currently exists then the build will fail. Here's one way to implement it:  <profiles> <profile> <id>integration-tests</id> <build> <plugins> <plugin> <groupId>com.atlassian.maven.plugins</groupId> <artifactId>maven-clover2-plugin</artifactId> <configuration> <targetPercentage>86.9%</targetPercentage> </configuration> <executions> <execution> <id>clover-check</id> <phase>verify</phase> <goals> <goal>instrument-test</goal> <goal>check</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </profile> </profiles> So this proposal is about the following strategy: * Allow committers to modify module's pom.xml to fail the build when then TPC is under the current threshold * Since oldcore is really difficult to test, maybe we should not set build failing for oldcore. OTOH oldcore is an important module. WDYT? * If for some reason a committer wants to lower the TPC threshold for a module he needs to get the agreement from the other committers (vote). There might be valid reasons like fixing an important bug quickly for a release and writing a test is just too complex so the writing of the test is to be delayed for after the release, etc. * I'd like to consider this as an experiment and see how it goes Note: This is about unit test TPC which is different from the TPC that includes functional tests. WDYT? Here's my +1 to try this out and see how it goes. Thanks -Vincent

12 years, 4 months

[xwiki-devs] Unable to add new topics under Xwiki BulletinBoard plugin

by echocoder

I have the BulletinBoard plugin installed into Xwiki to use as a forum. The forum works fine if it is accessed directly. However, I have a page in the Xwiki that includes a menu and a particular section of the forum. I can see content, I am just unable to add new topics via the page that contains a menu. When accessing the forum directly under the same section I am able to add new topics. The problem is that the site navigational menu must be included so this "middle man" page is necessary. The page that includes references to the menu and the forum section is written as: (% style="margin-top: -2em;" %) ((( |(% style="vertical-align: top; position: relative; top: -1.0em; left: -0.4em; border:0;" %)((( {{include document="CTAs.Menu"/}} )))|(% style="width: 100%; border-width: medium; border-style: none; border-color: -moz-use-text-color; vertical-align: top;" %)((( (% style="margin-top: -0.7em; margin-left: -0.25em" %) ((( {{include document="BulletinBoard.CTAENS" context="new"/}} ))) ))) ))) Where CTAs.Menu is the menu I need to include and the BullentinBoard.CTAENS is the section of the forum I need to display. The page displays fine, however the link "Add new topic" is not functional. The error that seems to be generated due to this action is.... 012-08-21 12:32:33,548 [/xwiki/bin/view/CTAs/ens_forum] ERROR rnal.DefaultObservationManager - Fail to send event [org.xwiki.observation.event.ActionExecutionEvent@373aa5] to listener [com.xpn.xwiki.stats.impl.XWikiStatsServiceImpl@110bc5c] java.lang.NullPointerException at com.xpn.xwiki.stats.impl.XWikiStatsServiceImpl.onEvent(XWikiStatsServiceImpl.java:190) at org.xwiki.observation.internal.DefaultObservationManager.notify(DefaultObservationManager.java:278) at org.xwiki.observation.internal.DefaultObservationManager.notify(DefaultObservationManager.java:247) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:316) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:117) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:627) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:129) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:218) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:775) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:704) at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:897) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:662) -- View this message in context: http://xwiki.475771.n2.nabble.com/Unable-to-add-new-topics-under-Xwiki-Bull… Sent from the XWiki- Dev mailing list archive at Nabble.com.

12 years, 4 months

[xwiki-devs] [XWiki DEVS][GSOC]Solr Search Features and Set Up Documentation

by savitha sundaramurthy

Dear XWiki community, The Advanced Search features, Administration module is almost complete in Solr Search component. The link to the running instance is given below. http://savitha.hoplahup.net/xwiki/bin/view/Main/AdvancedSearch Link to the Set Up Documentation and the features Page Set Up Doc and Feature Page<http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SolrSearchApplication> Progress Page<http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SOLRsearchcomponent> Work remaining to be able to commit the component in platform : 1. Fix checkstyle errors 2. Auto Suggest feature 3. Admin UI 4. Minor bugs in Facet search to be fixed 5. Search calibration 6. Unit test cases and Functional test cases. Planning to do the following this week 1. Fix checkstyle errors 2. Auto Suggest feature 3. Fix the minor bugs. 4. Search calibration 5. Complete the documentation. -- Thanks, Savitha

12 years, 4 months

[xwiki-devs] [Proposal] Problem displaying localized document titles

by Sergiu Dumitriu

Hi devs, Trying to address http://jira.xwiki.org/browse/XWIKI-6228 I noticed today a big problem with the way translations work. $xwiki.getDocument('Main.Welcome').getTranslatedDocument('fr').plainTitle No matter what language I request, the title will always be displayed in English. This is caused by the fact that for all translations, the title is actually $msg.get("xe.dashboard.wiki.welcome"), and $msg uses the context language, not the document language. This means that getting the right title of the document is almost impossible. Given that we've separated the displayers from the oldcore and the main rendering engine, we could change their behavior so that document translations would work better. Whenever displaying some information from a document, we should temporarily change the context language to be the same as the document's language, if any. This would be a backwards-incompatible change, but IMO it's a change for the better. WDYT? -- Sergiu Dumitriu http://purl.org/net/sergiu/

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