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

[xwiki-devs] [Proposal] Splitting xwiki-core-url into 2 modules
by Vincent Massol 28 Feb '09

28 Feb '09

Hi, In order to implement http://jira.xwiki.org/jira/browse/ XTSHAREDTESTS-12 I need to solve a cyclic dependency it creates: org.xwiki.platform:xwiki-core-url --> com.xpn.xwiki.platform.tools:xwiki-shared-tests --> org.xwiki.platform:xwiki-core-container-api --> org.xwiki.platform:xwiki-core-url I don't see a good solution other than spliting xwiki-core-url into 2 modules (in order to solve the cyclic dep) assumptions: - we need Container in shared tests as otherwise it's going to be a pain for all tests - using reflection in shared tests would mean making sure to have deps on container api in all tests modules - modifying url module to not use shared tests is a bit of a pain and not right IMO - moving XWikiURL to Container API doens't seem right either- - removing Request.getURL() is not right either and it's used in xwiki- action anyway It could be a good idea anyway to separate all modules into 2: api + implementation. However for practical reasons I don't think we'll do that, it's too much of a pain and will result in too many jars. So it's a bit strange to do it for xwiki-url and not for others but again I don't see solutions right now.... If nobody shouts I'd like to commit the url module split quickly (since I have it done and it's blocking me on some other issue). Thanks -Vincent http://xwiki.com http://xwiki.org http://massol.net

3 2

[xwiki-devs] [Proposal] JIRA Fix for strategy
by Vincent Massol 28 Feb '09

28 Feb '09

Hi, I'd like to clarify the strategy I'd like to propose that we use for JIRA fix for values since we haven't been very consistent about this in the past. Proposed rules: * We put all "fix for" for all places the commits have been done. If the commit has been done on 3 locations then we need 3 fix for values. For ex right now if you commit on trunk + in 1.8 branch you need fix for for *both* 1.8RC2 and 1.9M1. * In the release notes on xwiki.org we only put issues that haven't been already released in past versions. So when 1.9 M1 release notes are written you should exclude 1.8RC2 issues since they would have been released already (1.8RC2 is planned before 1.9M1). WDYT? If we agree can everyone check his jira issues and correct the fix for values? Thanks -Vincent http://xwiki.com http://xwiki.org http://massol.net

6 7

[xwiki-devs] [Idea] Switch to annotations for plexus component configuration?
by Vincent Massol 27 Feb '09

27 Feb '09

Hi, Here's an idea: use annotations to remove the need for components.xml files. Example: http://svn.apache.org/repos/asf/maven/components/trunk/maven-project/src/ma… Pros: * always correct * simpler maintenance Cons: * small tie with plexus. However the annotations are in small jar file by themselves and are only required at build time and not runtime. I'm not sure yet. WDYT? Thanks -Vincent http://xwiki.com http://xwiki.org http://massol.net

2 1

[xwiki-devs] Adding a feedback survey on XWiki.org
by Emilie Ogez 27 Feb '09

27 Feb '09

Good suggestions Ecaterina. Thanks. Date: Fri, 27 Feb 2009 13:23:43 +0200 From: Ecaterina Valica <valicac(a)gmail.com> Subject: Re: [xwiki-devs] [Proposal] Adding a feedback survey on XWiki.org To: XWiki Developers <devs(a)xwiki.org> Message-ID: <a7bce70e0902270323v4956de1dvf84cb777590a4810(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 hi. I have some suggestions: 1. You need numbering - you don't have a clear separation between questions. (1, 2, ... ) 2. 5 - "exceptional" - the word is a bit to much. Also the word "dazzled". 3. You need to decide if you want to write everywhere in the survey "Web site" or "website" - I'd recommend website ( http://en.wikipedia.org/wiki/Website) 4. "Are you satisfied with the quantity/quality of *information*?" - what information? Is too general. you could specify -> "the information on our site regarding ... " 5. I'd suggest replacing "*the* website" with "*our *website" to show that is not an ordinary website, that you care :) for the website Emilie - great work - I really want to see the results for the survey

1 0

[xwiki-devs] [Proposal] Adding a feedback survey on XWiki products
by Emilie Ogez 27 Feb '09

27 Feb '09

Arf... Thanks Vincent. Here is the new link: http://dev.xwiki.org/xwiki/bin/view/Drafts/SatisfactionSurveyProducts Date: Fri, 27 Feb 2009 13:19:48 +0100 > From: Vincent Massol <vincent(a)massol.net> > Subject: Re: [xwiki-devs] [Proposal] Adding a feedback survey on XWiki > products > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: <026485EA-AFD9-49E5-90F3-98475D5E1A05(a)massol.net> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > > On Feb 27, 2009, at 12:33 PM, Emilie Ogez wrote: > > >> Hello, >> >> I have started to list questions that could be part of the >> satisfaction >> survey about the XWiki products : >> http://intranet.xpertnet.biz/xwiki/bin/view/XWikiOrgWebsite/XWikiOrgWebsite >> > > People don't have access to that web site... > You can use the draft space on dev.xwiki.org > http://dev.xwiki.org/xwiki/bin/view/Drafts/ > > >> I propose to get first feedback about XWiki Enterprise and XWiki >> Enterprise Manager. So, I have made two different forms. But: >> 1) maybe, one form can be sufficient. >> 2) the questions in each form can be different. >> >> Again, I'd like your feedback about it/them. >> >> Thanks in advance for your help and your time. >> >> Emilie >> > > Thanks > -Vincent > http://xwiki.com > http://xwiki.org > http://massol.net > > > > > > > > > ------------------------------ > > Message: 5 > Date: Fri, 27 Feb 2009 13:35:52 +0100 > From: Vincent Massol <vincent(a)massol.net> > Subject: [xwiki-devs] [VOTE] New XE 1.8 Release dates > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: <AE34089C-A97B-47A3-A8E4-91909B33DED4(a)massol.net> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > Hi, > > New proposed dates that take into account the lag in the WYSIWYG dev > for the 1.8 final release. > > * 1.8 RC2 - Stays on 2nd of March > * 1.8 RC3 - 12th of March > * 1.8 final - 16th March > > It would be time boxed, ie we release on the 12th whatever we have > finished on the 11th night. This should allow us to finish most of the > new WYSIWYG stuff. Let us know on the wysiwyg side if anything is at > risk as you progress. > > Here's my +1 > > Thanks > -Vincent > http://xwiki.com > http://xwiki.org > http://massol.net > > > > > > > > > ------------------------------ > > Message: 6 > Date: Fri, 27 Feb 2009 14:59:09 +0200 > From: Marius Dumitru Florea <mariusdumitru.florea(a)xwiki.com> > Subject: Re: [xwiki-devs] [VOTE] New XE 1.8 Release dates > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: <49A7E39D.2010702(a)xwiki.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > +1. I'm almost done with macro editing. Macro insertion (browsing > available macros mainly) is next. I'm confident we'll have macro support > ready by 11th March. I might even have time to fix some bugs (there are > 10 assigned to me right now). > > Thanks, > Marius > > Vincent Massol wrote: > >> Hi, >> >> New proposed dates that take into account the lag in the WYSIWYG dev >> for the 1.8 final release. >> >> * 1.8 RC2 - Stays on 2nd of March >> * 1.8 RC3 - 12th of March >> * 1.8 final - 16th March >> >> It would be time boxed, ie we release on the 12th whatever we have >> finished on the 11th night. This should allow us to finish most of the >> new WYSIWYG stuff. Let us know on the wysiwyg side if anything is at >> risk as you progress. >> >> Here's my +1 >> >> Thanks >> -Vincent >> http://xwiki.com >> http://xwiki.org >> http://massol.net

1 0

[xwiki-devs] [VOTE] New XE 1.8 Release dates
by Vincent Massol 27 Feb '09

27 Feb '09

Hi, New proposed dates that take into account the lag in the WYSIWYG dev for the 1.8 final release. * 1.8 RC2 - Stays on 2nd of March * 1.8 RC3 - 12th of March * 1.8 final - 16th March It would be time boxed, ie we release on the 12th whatever we have finished on the 11th night. This should allow us to finish most of the new WYSIWYG stuff. Let us know on the wysiwyg side if anything is at risk as you progress. Here's my +1 Thanks -Vincent http://xwiki.com http://xwiki.org http://massol.net

2 1

[xwiki-devs] [Proposal] Adding a feedback survey on XWiki products
by Emilie Ogez 27 Feb '09

27 Feb '09

Hello, I have started to list questions that could be part of the satisfaction survey about the XWiki products : http://intranet.xpertnet.biz/xwiki/bin/view/XWikiOrgWebsite/XWikiOrgWebsite I propose to get first feedback about XWiki Enterprise and XWiki Enterprise Manager. So, I have made two different forms. But: 1) maybe, one form can be sufficient. 2) the questions in each form can be different. Again, I'd like your feedback about it/them. Thanks in advance for your help and your time. Emilie

2 1

Re: [xwiki-devs] [Proposal] Adding a feedback survey on XWiki.org
by Emilie Ogez 27 Feb '09

27 Feb '09

Hello, Thanks for your feedback and your suggestions. I have made modifications in the survey. Here is the last version: http://www.xwiki.org/xwiki/bin/view/Main/Survey What do you think about it? Thanks. Emilie On Feb 26, 2009, at 10:43 PM, Marius Dumitru Florea wrote: >/ Hi Emilie, />/ />/ Sergiu Dumitriu wrote: />>/ Emilie Ogez wrote: />>>/ Hello, />>>/ />>>/ My name is Émilie Ogez. I am the marketing and communication />>>/ manager at />>>/ XWiki SAS (the company supporting the XWiki.org Open-Source />>>/ project). />>>/ />>>/ I've given a look at the current XWiki.org website and I think />>>/ there's />>>/ room for improvement. I'd be glad to: />>>/ />>>/ * help improving the design and content of the XWiki.org website />>>/ * suggest animation ideas for the XWiki Developers community />>>/ * help improving XWiki products by gathering user feedback />>>/ />>>/ In order to do this, I would like to publish 2 online surveys on />>>/ XWiki.org: />>>/ />>>/ * a survey asking users about what they think of the current />>>/ XWiki.org website (do they find content easily, is it />>>/ intuitive to />>>/ use) />>>/ * a survey asking users about how they're using XWiki products />>>/ and />>>/ how we could improve our product range />>>/ />>>/ I started with the survey about XWiki.org. I'd like to send it to />>>/ people />>>/ from the Devs & Users list and to make it available to XWiki.org />>>/ visitors. Survey answers would help us improve the website and />>>/ make it />>>/ more effective and attractive for the XWiki.org community. />>>/ />>>/ Here's the survey contents I suggest: />>>/ http://www.xwiki.org/xwiki/bin/view/Main/Survey. I'd be glad to />>>/ get your />>>/ feedback about it about it before putting it online. />>/ />>/ The yes/no options should not be checkboxes, but radio buttons. />>/ />>/ Apart from quantity and quality, we should also ask about the />>/ information organization, ease of use, ease of access. />/ />/ I agree with Sergiu. I too think the survey should have more questions />/ and maybe we should let users give marks (from 1-bad to 5-exceptional, />/ or something similar) and not just yes/no answers. I'm not a survey />/ expert though. / I agree with Marius you should never ask for yes/no (you won't know what to do with the result) but a scale of 1-5 instead. Thanks -Vincent http://xwiki.com http://xwiki.org http://massol.net

2 1

[xwiki-devs] erreur lors de l'export pdf
by natoine 27 Feb '09

27 Feb '09

Hi When i try to export a page in pdf , i have this error : (i use XWiki Enterprise 1.6.1.13621 ) Error number 11015 in 11: Exception while exporting Wrapped Exception: Error number 12003 in 12: XSL Transformation Failed Wrapped Exception: Premature end of file. com.xpn.xwiki.XWikiException: Error number 11015 in 11: Exception while exporting Wrapped Exception: Error number 12003 in 12: XSL Transformation Failed Wrapped Exception: Premature end of file. at com.xpn.xwiki.web.ExportAction.render(ExportAction.java:64) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:216) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115) 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:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:94) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:287) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.web.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.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:619) -- Antoine SEILLES Doctorant (phd student) LIRMM CNRS Président de l'association imagiLAB LIRMM CNRS: UMR 5506 - 161 rue Ada 34392 Montpellier Cedex 5 FRANCE www.lirmm.fr Association imagiLAB apt D22 Mas du Cavalier, 365 quai louis le vau 34080 Celleneuve www.imagilab.fr Tel: +33 (0)6 10 192 055 antoine(a)imagilab.fr antoineseilles(a)gmail.com Antoine.seilles(a)lirmm.fr

3 3

[xwiki-devs] [Proposal] Adding a feedback survey on XWiki.org
by Emilie Ogez 26 Feb '09

26 Feb '09

Hello, My name is Émilie Ogez. I am the marketing and communication manager at XWiki SAS (the company supporting the XWiki.org Open-Source project). I've given a look at the current XWiki.org website and I think there's room for improvement. I'd be glad to: * help improving the design and content of the XWiki.org website * suggest animation ideas for the XWiki Developers community * help improving XWiki products by gathering user feedback In order to do this, I would like to publish 2 online surveys on XWiki.org: * a survey asking users about what they think of the current XWiki.org website (do they find content easily, is it intuitive to use) * a survey asking users about how they're using XWiki products and how we could improve our product range I started with the survey about XWiki.org. I'd like to send it to people from the Devs & Users list and to make it available to XWiki.org visitors. Survey answers would help us improve the website and make it more effective and attractive for the XWiki.org community. Here's the survey contents I suggest: http://www.xwiki.org/xwiki/bin/view/Main/Survey. I'd be glad to get your feedback about it about it before putting it online. Thanks, Émilie

6 6