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

[xwiki-devs] XWiki Enterprise 4.3.1 Issues
by Manuel Smeria 19 Dec '12

19 Dec '12

Hello everyone, Today Sorin and I went through the *full issue list*<http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki431#HFull…> for XWiki Enterprise 4.3.1. We managed to test a part of them, but it would help if some of you could test the remaining items (they're either too technical or don't have enough steps to reproduce) and complete this report<http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportXWiki431> . Thank you, Manuel

2 1

Re: [xwiki-devs] [xwiki-users] [ANN] XWiki Enterprise and XWiki Enterprise Manager 4.3.1 released.
by Eduard Moraru 19 Dec '12

19 Dec '12

Hi, Yes, I am aware of that. I was hoping that the downloads become available on our hosting platform (ObjectWeb), but it seems that something has gone wrong. While we investigate the problem, you can download the release from our maven repository: http://maven.xwiki.org/releases/ More specifically, for 4.3.1: = XWiki Enterprise = EXE: http://maven.xwiki.org/releases/org/xwiki/enterprise/xwiki-enterprise-insta… JAR: http://maven.xwiki.org/releases/org/xwiki/enterprise/xwiki-enterprise-insta… ZIP: http://maven.xwiki.org/releases/org/xwiki/enterprise/xwiki-enterprise-jetty… WAR: http://maven.xwiki.org/releases/org/xwiki/enterprise/xwiki-enterprise-web/4… XAR: http://maven.xwiki.org/releases/org/xwiki/enterprise/xwiki-enterprise-ui-al… = XWiki Enterprise Manager = ZIP: http://maven.xwiki.org/releases/org/xwiki/manager/xwiki-manager-jetty-mysql… WAR: http://maven.xwiki.org/releases/org/xwiki/manager/xwiki-manager-web/4.3.1/x… XAR: http://maven.xwiki.org/releases/org/xwiki/manager/xwiki-manager-ui-all/4.3.… XAR: http://maven.xwiki.org/releases/org/xwiki/manager/xwiki-manager-ui/4.3.1/xw… dependencies) Sorry for the inconvenience, Eduard On Wed, Dec 19, 2012 at 9:44 AM, Haru <haru_mamburu(a)mail.ru> wrote: > Direct link > > http://download.forge.objectweb.org/xwiki/xwiki-enterprise-web-4.3.1.war > > gives 404 > > > Вторник, 18 декабря 2012, 20:25 от Eduard Moraru <enygma2002(a)gmail.com>: > >The XWiki development team is proud to announce the availability of XWiki > >Enterprise 4.3.1. > > > >This is a bugfix and stabilization version that brings fixes for various > >areas of XWiki's features like Workspaces, Extension Manager, Search and > >others. > > > >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/ReleaseNotesXWiki431 > > > >Thanks > >-The XWiki dev team > >_______________________________________________ > >users mailing list > >users(a)xwiki.org > >http://lists.xwiki.org/mailman/listinfo/users > > > Kind regards, > > Dmitry > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users >

1 0

[xwiki-devs] [ANN] XWiki Enterprise and XWiki Enterprise Manager 4.3.1 released.
by Eduard Moraru 18 Dec '12

18 Dec '12

The XWiki development team is proud to announce the availability of XWiki Enterprise 4.3.1. This is a bugfix and stabilization version that brings fixes for various areas of XWiki's features like Workspaces, Extension Manager, Search and others. 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/ReleaseNotesXWiki431 Thanks -The XWiki dev team

1 0

Re: [xwiki-devs] How to Include a page without velocity code into another page
by Geo Du 17 Dec '12

17 Dec '12

Hi Marius, This works, but my problem is that I have a xwiki page, I have a link on this page, when I click on this link, a javascript function is called, with the call, I want to include a new xwiki page at the bottom of the current page without reloading the current old content (like appending a new page to the current page without change of the old content), the new appended content could be in edit or view mode. My question is the approach you have here is to use display macro, how to trigger this macro inside javascript code? also how to avoid reloading the old content when appending new content? since in the old page I have some search results listed, I do not want to lose it and make users have to search again. Thanks for your help. David On Mon, Nov 5, 2012 at 3:33 AM, Marius Dumitru Florea < mariusdumitru.florea(a)xwiki.com> wrote: > The display macro works for me as you would expect. For instance, if I > create a page with this content: > > ----------8<---------- > {{velocity}} > Current action: $xcontext.action > {{/velocity}} > > {{display reference="Blog.BlogIntroduction"/}} > ---------->8---------- > > in view mode I can see the blog post preceded by "Current action: > view" and in "Inline Form" edit mode I can edit the blog post, which > is preceded by "Current action: edit". > > Hope this helps, > Marius > > On Fri, Nov 2, 2012 at 10:18 PM, Geo Du <dddu88(a)gmail.com> wrote: > > Hi Marius, > > > > Thanks for your response, it works when I use display macro to include > the > > testpage into the other page, but I need also to include (display) the > page > > with inline mode inside the other page, since user can click the edit > pencil > > button on the right corner of the testpage to edit it, right now the edit > > button will lead to the testpage in inline mode but the testpage is not > > inside the other page which originally include(display) the testpage. > > > > So how to include or display a page with inline mode into another page? > > > > Thanks for your help. > > > > David > > > > On Fri, Nov 2, 2012 at 3:06 AM, Marius Dumitru Florea > > <mariusdumitru.florea(a)xwiki.com> wrote: > >> > >> On Thu, Nov 1, 2012 at 10:51 PM, Geo Du <dddu88(a)gmail.com> wrote: > >> > > >> > Hi All, > >> > > >> > I want to include one page into another page in terms of content > instead > >> > of > >> > velocity code, for example, the Blog.WebHome is a page without > velocity > >> > code if you choose Edit->Wiki, but it has Blog.BlogClass if you select > >> > Edit->Objects, from Blog.WebHome page, I can create a new post with > tile > >> > testpage, now the Blog.testpage is the new page created that I need to > >> > include into another page, this testpage has no velocity code from > >> > Edit_>Wiki. so how to include that page into a different page? > >> > > >> > >> > I tried: include Macro, includeInContext Macro, includeTopic Macro, > none > >> > of > >> > them displays the testpage for me, any idea? > >> > >> "display" is the key. You want to display not to include. See > >> http://extensions.xwiki.org/xwiki/bin/view/Extension/Display+Macro . > >> > >> Hope this helps, > >> Marius > >> > >> > > >> > Thanks very much for your help. > >> > > >> > David > >> > _______________________________________________ > >> > devs mailing list > >> > devs(a)xwiki.org > >> > http://lists.xwiki.org/mailman/listinfo/devs > >> _______________________________________________ > >> devs mailing list > >> devs(a)xwiki.org > >> http://lists.xwiki.org/mailman/listinfo/devs > > > > >

2 1

[xwiki-devs] Fwd: YourKit Java Profiler 12 released
by Vincent Massol 14 Dec '12

14 Dec '12

fyi. Reminder: we have a license for the xwiki project. Thanks -Vincent Begin forwarded message: > From: YourKit Information Service <info(a)yourkit.com> > Subject: YourKit Java Profiler 12 released > Date: December 14, 2012 11:50:49 AM GMT+01:00 > To: vincent(a)massol.net > > Greetings, > > We are glad to announce immediate availability of YourKit Java Profiler 12 > released on December 3, 2012. > > It can be downloaded at http://www.yourkit.com/download/ > > MOST NOTABLE CHANGES AND NEW FEATURES: > ====================================== > > NEW PLATFORMS SUPPORTED: > > - Linux on ARM > > - Linux on PPC > > CPU PROFILING: > > - Tracing overhead significantly reduced: profiled applications run > up to 10%-50% faster than with the previous profiler version, due to > new adaptive tracing mode and optimizations > > - Tracing accuracy increased > > - Reworked tracing and sampling settings > > MEMORY PROFILING: > > - New feature: "Class tree" view which is similar to "Class list", but shows classes > grouped by package > > - New feature: memory views such as Class list allow selection of multiple rows > > - "Duplicate strings" inspection: the results are shown under a new grouping root node > which presents the total waste in all the duplicate strings > > - Optimization: snapshots with big primitive arrays are opened faster > > - Optimization: performance of "Incoming References" view has been dramatically improved > > - Improved calculation of exact retained size in "Class list" and similar views: > more items are processed per click if calculation speed allows > > - Improvement: available CPU cores are used for parallel computations in: > - Class list > - Class tree > - Generations > - Reachability scopes > - Class loaders > - Web applications > - Object ages > > - Improvement: "Calculate exact retained sizes" action uses available CPU cores > to perform calculation in parallel > > - Optimization: allocation recording overhead has been reduced for multithreaded > applications: code being profiled runs up to 30% faster when each 10th object > is recorded (the default setting), and up to 70% faster when each 100th object > is recorded, comparing with the previous version > > - Improvement: web application context path (URL) is now shown in addition to the name > > - Web applications: added support of Jetty (versions 6, 7, 8) > > - Class instance count telemetry: scalability improved > > TELEMETRY: > > - CPU usage telemetry: kernel CPU time is shown as a separate curve, > in addition to the main user + kernel CPU time graph > > - Graph rendering has been optimized, making UI much more responsive, especially > when using bigger scales > > PROBES: > > - New feature: ability to clear tables. > Get rid of older events you are not interested in anymore, > or give space for new events if the table capacity limit has been reached. > > - "Probes" tab layout has been changed to gives more vertical space for browsing > event lists, and make the UI more consistent > > - Class loading probe can be optionally disabled > > IDE INTEGRATION: > > - Eclipse, IntelliJ IDEA, NetBeans 7.0 and newer plugin > automatically detects 32-bit and 64-bit JVMs, instead of relying on user input > > - Eclipse: Maven run configurations supported in Eclipse 3.7 and newer > > - IntelliJ IDEA 12 supported > > - NetBeans 7.3 supported > > J2EE INTEGRATION: > > - J2EE integration wizard: added Jetty 6 and newer support > > USER INTERFACE: > > - Improvement: the left vertical tab group avoids scroller if many tabs are opened > > - Added an quick way to switch between applying and not applying filters in UI > > - Added support of high-contrast color schemes > > - Call tree and back traces views: added popup menu item to expand selected node > down to 5 levels, as a supplement to the existing item which expands the node fully > > MISCELLANEOUS: > > - Export with command line: class list is exported for performance snapshots too > (as seen in Memory tab | Class list) > > - Agent: log file name now contains the session name to better separate logs from > different applications > > - Agent: added an option to store logs from several runs of the same application > in a series of log files named <session name>.<running number>.log > This mode can be useful when profiling applications such as servers, > when having a united log is better than having a separate log for each server start. > > - Agent: Groovy 2.0 supported > > - Other bug fixes and improvements > > See complete list of changes at http://www.yourkit.com/changes/ > > Kindest regards, > YourKit Team > > ____________________________________________________________ > If you would not like to receive any more information about > YourKit Java Profiler, simply send an e-mail to info(a)yourkit.com > with the subject line "unsubscribe".

1 0

[xwiki-devs] [Proposal] Stopping the 4.4M1 release till tests are all passing - Commando mode
by Vincent Massol 14 Dec '12

14 Dec '12

Hi devs, We have too many test failures on http://ci.xwiki.org/view/Functional%20Tests/ and too many emails sent by Jenkins on the list. It has become a nightmare and it's impossible to perform a release anymore with a good confidence it's going to work. This is all the more bad that we're ending the 4.x cycle. Thus I propose to do the following: * Don't release 4.4M1 till all tests are passing with no more flickers (say the tests should all pass during 10 full builds for example) * Create a Commando unit in charge of solving the flickers. Since I've already discussed this with Marius I propose that Marius and myself be the first 2 members. If anyone else would like to help please reply to this mail and join us. * This commando unit gives itself 1 full week to solve the flickers (ie till the 21st of December). We'll decide what to do next if we fail to achieve our goal after that deadline. * We start by creating a branch for 4.4M1 so that we isolate ourselves from the rest of the devs who continue to work for 4.4RC1 (reminder: only important bug fixes should go in 4.4RC1) * When we have fixed all flickers on the 4.4M1 branch we merge the changes to both master and the stable-4.3 branch * At the end of next week we also propose a strategy so that this mess doesn't happen again in the future WDYT? Thanks -Vincent Note: We need to release 4.3.1 ASAP so this strategy above will not apply to 4.3.1. For 4.3.1 Edy will need to figure out if all the failing tests are real issues or test issues. I think Edy could do this by a combination of running them locally and doing some manual tests where they also fail locally. Edy WDYT?

7 10

[xwiki-devs] [Vote] Retire Toucan Skin
by Ecaterina Moraru (Valica) 11 Dec '12

11 Dec '12

Hi Devs, Right now we are supporting 2 skins: Toucan and Colibri (default), according to http://platform.xwiki.org/xwiki/bin/view/Features/Skins According to http://xwiki.markmail.org/thread/tyceqsfdsnq2wikh Toucan is not maintained, but supported since Jan 2010. That's about 3 years ago. The question is what do we plan to do with Toucan skin? +1 for retire and closing all JIRA issues This means that our only supported skin will be Colibri (added in 2.0, our default since Sep 2009, base skin since Dec 2010). Thanks, Caty P.S. Dodo and Finch skins were retired in Nov 2009 http://markmail.org/thread/56stmwtylwglozyh Albatross skin was retired in Oct 2010 http://xwiki.markmail.org/thread/jx5vyqtrwwaidfka (< 1.3 - 2.5)

7 7

[xwiki-devs] [Proposal] XWiki 4.5 Roadmap dates and 4.x end of cycle
by Vincent Massol 10 Dec '12

10 Dec '12

Hi devs, 4.4 and 4.5 go together since they contain the leftover that we wish to do for the 4.x cycle. Could all developers please edit http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap for both 4.4 and 4.5 and spread between 4.4 and 4.5 the JIRAs that they wish/need to fix for the 4.x cycle? So we need: * All JIRA created * JIRA listed in that roadmap page * Committers assigned to them It's important that we have a good vision of the leftover and ensure we can reach the targeted dates. Reminder: AWM and EM need to be working well and be production ready at the end of 4.5. I think it's the case for AWM (even if there could have been some improvements) but for EM it has still not achieved our goal of "be able to update a wiki farm in a few minutes". I think Thomas and Marius should really focus on this for the remaining time they have. I'd also like to propose dates for the 4.5 release: * 4.5M1: 14th of Jan 2013 * 4.5RC1: 21st of Jan 2013 * 4.5 Final: 4th of February 2013 WDYT? We can do it! :) -Vincent

5 5

[xwiki-devs] [VOTE] Move all lucene plugin classes to internal
by Jerome Velociter 08 Dec '12

08 Dec '12

Hello, Right now all code in the lucene plugin is exposed as API while almost none of it is actual API. I would like to move all lucene plugin classes to an internal package, except for "LucenePluginApi". For the non API "LucenePlugin", I'm not sure, since moving it would break users conf (xwiki.cfg). WDYT ? My +1, Jerome

6 10

[xwiki-devs] [VOTE] Stop shading Rendering Standalone
by Vincent Massol 06 Dec '12

06 Dec '12

Hi devs, I'd like to propose that we stop shading Rendering Standalone. The reasons are: 1) It's far from perfect. For example we have at least 3 libs we cannot shade:  2) As we added some libs to our deps we forgot to relocate them so right now we don't shade (to cite a few): com.steadystate.css, javax.validation, ant, aspectj, slf4j, etc 3) There are lots of resources coming from dependent jars and those are not shaded. For example: 283 Tue Dec 04 18:50:42 CET 2012 javacc.class 286 Tue Dec 04 18:50:42 CET 2012 jjdoc.class 235 Tue Dec 04 18:50:42 CET 2012 jjtree.class 0 Tue Dec 04 18:50:42 CET 2012 org/xwiki/shaded/javacc/ or 3783 Tue Dec 04 18:50:42 CET 2012 org/xwiki/shaded/javacc/utils/JavaFileGenerator.class 3693 Tue Dec 04 18:50:42 CET 2012 templates/CharStream.template 15990 Tue Dec 04 18:50:42 CET 2012 templates/JavaCharStream.template 867 Tue Dec 04 18:50:42 CET 2012 templates/MultiNode.template 1317 Tue Dec 04 18:50:42 CET 2012 templates/Node.template 5962 Tue Dec 04 18:50:42 CET 2012 templates/ParseException.template 12711 Tue Dec 04 18:50:42 CET 2012 templates/SimpleCharStream.template 3227 Tue Dec 04 18:50:42 CET 2012 templates/SimpleNode.template 4005 Tue Dec 04 18:50:42 CET 2012 templates/Token.template 368 Tue Dec 04 18:50:42 CET 2012 templates/TokenManager.template 4244 Tue Dec 04 18:50:42 CET 2012 templates/TokenMgrError.template 48 Tue Dec 04 18:50:42 CET 2012 version.properties So I'd like to keep a standalone distribution to make it easy to test XWiki Rendering but without any shading. Here's my +1 Thanks -Vincent

5 8