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

[xwiki-devs] document index / live table last author bug?

by Mark Wallace

In xwiki 4.1.3, there is a document index page that uses live table. It lists authors by first/last name, not their real user name. E.g. if author is user name XWiki.jgibbs, with first/last names "Joe Gibbs", the table shows "Joe Gibbs". But if I enter "joe" in the search box, I get nothing because it is actually searching the user name (XWiki.jgibbs), which does not have "joe" in it. This seems like a bug because the text shown is not the text being searched for. Has this been fixed in 4.2 or the upcoming 4.3? -- Mark Wallace Principal Engineer, Semantic Applications Modus Operandi, Inc.

12 years, 10 months

1
0
0 0

[xwiki-devs] [VOTE] Functional test best practice: test order and change of configuration/creation of pages

by Vincent Massol

Hi devs, I've just added 3 items on http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HSelenium2-basedFrame… and I'd like to ensure that we agree about them (if not I'll remove them): * Tests must not depend on one another. In other words, it should be possible to execute tests in any order and running only one test class should work fine. * Test chat need to change existing configuration (e.g. change the default language, set specific rights, etc) must put back the configuration as it was * Tests are allowed to create new documents and don't need to remove them at the end of the test Here's my +1 Thanks -Vincent

12 years, 10 months

4
5
0 0

[xwiki-devs] [Proposal] Bug Fixing Day #7, 22 November 2012 (second try)

by Vincent Massol

Hi devs, Ok BFD #7 which was planned for the 1st of November has been cancelled since it was a day off in France (and I was on holiday at that time so I couldn't follow up on it). Hence I propose to do it on Thursday the 22nd of November (i.e. in 11 days from now). Let me know if you can attend it. Thanks -Vincent

12 years, 10 months

4
5
0 0

[xwiki-devs] Bug Fixing Day #7, 1st of November

by Ecaterina Moraru (Valica)

Hi devs and contributors, According to a past vote we had [1] we are having a BFD every month on the first Thursday of every month, with the goal of reducing drastically the bug count. This month the BFD is on 1st November, which means Today. This mail is a reminder that today we are counting :) As a practice: Once you close an issue (whether you fixed it or mark it with "duplicate", "won't fix", etc) please ensure you label it with "bugfixingday" so that we can easily count them at the end of the day. You can see the current status of issues fixed during all our past Bug Fixing Days at http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=11196 Let's make a dent in this stat: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10000#Created-vs-R… Thanks, Caty of behalf of the XWiki Development Team [1] http://markmail.org/thread/np65udilrwnuekyh

12 years, 10 months

3
3
0 0

[xwiki-devs] Macro inside a javascript extension

by firmusoft.xwiki

Can we call a macro from a javascript extension Thanks, Firmusoft

12 years, 10 months

2
1
0 0

[xwiki-devs] Set javascript variable to velocity variable

by firmusoft.xwiki

How can we set javascript variable to a velocity variable? Please reply with a solution for this. If you have sample it would be more helpful. Thanks, Firmusoft

12 years, 10 months

2
1
0 0

[xwiki-devs] [Contrib] xwiki-task-executor

by Fabio Mancinelli

Hi, while working on a project I developed this simple system for managing the execution of long running execute-once tasks. It uses the scheduler and it provides a nice framework for logging and error reporting. The main use case for this extension is batch import of data, but also execute-once maintenance operations. Basically every task that is too long or heavy to be carried on in a single request, and doesn't really qualify to be a scheduler job. You can think of this system as a task queue that is processed in the background. I am contributing it to xwiki contrib. Thanks, Fabio

12 years, 10 months

3
6
0 0

[xwiki-devs] [PROPOSAL] Allow servlets to be registered with the ComponentManager.

by Caleb James DeLisle

Hi, I'd like to register servlets in the component manager and have them called by their hint. The oldcore struts servlet would be @Named("bin") and the rest servlet would be @Named("rest") Reasons to want to do this: * There are things which are currently impossible without a servlet, things like REST, GWT and WebDav. * If somebody has servlet code and they want to make it run in XWiki, this is a real answer for them whereas "rewrite your app using XWiki actions" isn't. * Even if we had an Actions system which made it *possible* to implement REST, GWT, and WebDav entry points, we would have to rewrite the universe since all external libraries use Servlet. * Web.xml is an eyesore, it's full of content which is the concern only of a particular module, this could (mostly) be fixed by using injected servlets. The big reason not to like it is because it could undermine the proposal for Actions. The JIRA issue for actions http://jira.xwiki.org/browse/XWIKI-4713 was opened on January 1 of 2010. It is stalled because nobody really knows how to make an abstraction which represents Servlets or Portlets without any lost features. If we make it easier for servlets to be used, we might begin down a slippery slope toward everything being done using servlets and then we lose portlet compatibility. But the alternative as I see it is to block progress in this direction and hope that somebody steps up to implement Actions which are fully compatible with portlets and servlets. WDYT? Are there reasons not to do this which I missed? Caleb

12 years, 10 months

3
6
0 0

[xwiki-devs] [VOTE] Dynamically registered wiki translations

by Thomas Mortagne

Hi devs, Following the discussion about general architecture of the new localization module here is a more detailed proposal for the dynamically registered wiki translations pages. Here is how I propose to indicate that a document contains key=value pair translations: * put an object of class "XWiki.TranslationDocumentClass" * set the "visibility" field to "Global", "Current wiki", "Current user" As for the content of the document it will stay the same as in preferences based documents for now. I have other fields in mind for later (on demand, translation message syntax, etc.) but this is a 4.3 proposal here. WDYT ? Here is my +1. -- Thomas Mortagne

12 years, 10 months

9
19
0 0

[xwiki-devs] [VOTE] merge branch 'feature-solr-search' into 'master' for 4.3M2

by Eduard Moraru

Hi devs, I would like your vote on merging the 'feature-solr-search' branch with 'master' for 4.3M2 as planned in the Roadmap. Merge Notes: - A first version of the Solr search is bundled by default as experimental with XE, but Lucene is still the default search engine. --- Lucene has been upgraded to 3.6.1 [1] and Solr has been downgraded to the same (3.6.1) version in order to achieve the peaceful cohabitation between the 2 search versions. If we want Solr 4.0, we need to work a bit more on the Lucene search, since Lucene 4.0 comes with a considerable number of refactorings. ----- I have just noticed Jerome's feature-lucene-4.0.0-upgrade [2] branch. - The admin needs to use the Search Administration to switch from Lucene to Solr and back. (each engine has its own index) - The back-end contains a SolrIndex for add/delete operations and a QueryExecutor to query the index trough XWiki's Query API using the 'solr' language. - Indexing is only manually performed for now, from the Search Administration, blocking the request until the operation is complete. - Search highlighting is available - The default search looks only for Documents. Filtered/Advanced search options can be used to change some of the search parameters. - Lucene/Solr syntax is supported in the query string - Faceted search is currently hidden because it is not yet in an usable state. - SearchSuggest is still using Lucene, no matter what the configuration in Search Administration says - The merge also contains a fix for a pretty nasty yet easily fixable Lucene deadlock [3] (introduced 10 months ago) and some Search Admin UI improvements [4] The pull requests [5][6] are available for reviewing so start shooting :) Thanks, Eduard ---------- [1] http://jira.xwiki.org/browse/XWIKI-8407 [2] https://github.com/xwiki/xwiki-platform/tree/feature-lucene-4.0.0-upgrade [3] http://jira.xwiki.org/browse/XWIKI-8406 [4] http://jira.xwiki.org/browse/XWIKI-8408 [5] https://github.com/xwiki/xwiki-platform/pull/73 [6] https://github.com/xwiki/xwiki-enterprise/pull/34

12 years, 10 months

7
9
0 0

Re: [xwiki-devs] [xwiki-users] Paste picture/image from clipboard

by Paul Libbrecht

There are several such features related to copy and paste (and drag-and-drop) which a newer trends could choose to follow. I'd be more than happy to advise on a GSoC project for such. But maybe there's an interest before. It's almost exclusively JS work. paul Le 9 nov. 2012 à 12:05, Guillaume Lerouge a écrit : > No. You have to save it first, then upload it to the wiki page. > > Guillaume > > On Fri, Nov 9, 2012 at 11:59 AM, Hamster <teunham(a)hotmail.com> wrote: > >> Is it possible to paste an image from MS Paint directly into an xwiki page?

12 years, 10 months

1
0
0 0

[xwiki-devs] [VOTE] New release dates for the 4.3M2/RC1/Final releases

by Eduard Moraru

Hi devs, Since last week was light on development (due to various holidays) and today we are already past the release date for 4.3M2, after talking with Vincent, we propose to postpone the 4.3 releases by a couple of days, as follows: Current dates: 4.3M2: 5 Nov 4.3RC1: 12 Nov 4.3final: 19 Nov Proposed postpone dates: 4.3M2: 9 nov 4.3RC1: 14 nov 4.3final: 21 nov Here's my +1 and I will be Release Manager for 4.3M2. We are still looking for Release Managers for the next releases, so please feel free to propose your selves Thanks, Eduard

12 years, 10 months

6
9
0 0

[xwiki-devs] Fwd: Github tracker. was: Re: [xwiki-users] New Realtime collaborative editing extension.

by Ludovic Dubost

This should have been for devs Envoyé de mon iPhone Début du message transféré : > Expéditeur: Ludovic Dubost <ludovic(a)xwiki.com> > Date: 23 octobre 2012 09:19:55 UTC+02:00 > Destinataire: XWiki Users <users(a)xwiki.org> > Objet: Github tracker. was: Re: [xwiki-users] New Realtime collaborative editing extension. > > Just a quick. You seem to introduce a practice to use the github tracker instead of xwiki.org jira's > > Not sure it's a good thing. I'm sure Vincent will agree > > Ludovic > > > Envoyé de mon iPhone > > Le 23 oct. 2012 à 04:17, Caleb James DeLisle <calebdelisle(a)lavabit.com> a écrit : > >> One other thing, please report the features which you want and what you imagine as >> best on the github tracker, it's easier to close an issue as "won't fix" than it is >> to remember an important issue which nobody wrote down ;) >> >> Thanks >> Caleb >> >> On 10/22/2012 10:14 PM, Caleb James DeLisle wrote: >>> Hi, >>> >>> Thanks for the complement. >>> >>> I just updated it and fixed issue #1. Thanks for reporting it. >>> Somehow showing who else is editing, showing where they are editing in the document >>> and allowing the user to spawn a chat window with other editors on the page are all >>> interesting possibilities. Right now I think the thing to do is decide where there >>> is the most bang for your buck in terms of feature value and get an idea of what's >>> most natural for the user. >>> >>> Thanks, >>> Caleb >>> >>> >>> On 10/19/2012 07:59 AM, Ryszard Łach wrote: >>>> Great work! >>>> >>>> It looks like good starting point to give xwiki the main (at least for >>>> me) feature, that makes googledoc sometimes more suitable for >>>> collaborative editing. It would be really great, if your editor would >>>> show somehow, where the other editor (person) is now, where is his >>>> cursor. Maybe a highlight (the whole line) showing the other's cursor >>>> placement? >>>> Do you plan to work on such improvements? >>>> >>>> R. >>>> >>>> _______________________________________________ >>>> users mailing list >>>> users(a)xwiki.org >>>> http://lists.xwiki.org/mailman/listinfo/users >>> >>> >>> _______________________________________________ >>> users mailing list >>> users(a)xwiki.org >>> http://lists.xwiki.org/mailman/listinfo/users >> >> >> _______________________________________________ >> users mailing list >> users(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/users

12 years, 10 months

5
18
0 0

[xwiki-devs] [VOTE] Clirr difference for fixing content dirty flag.

by Andreas Jonsson

Hi, I am requesting a vote for adding the following clirr difference: <difference> <className>com/xpn/xwiki/objects/ListProperty</className> <field>list</field> <differenceType>6006</differenceType> <justification>Elemenents must be added to the wrapping NotifyOnUpdateList to ensure that the property is marked 'dirty' when updated. To avoid that this mechanism is circumvented, the field is made final.</justification> </difference> The flag isContentDirty in XWikiDocument is currently always true when a document is loaded from the database. This means that a script that just load and save a document without modifying it will generate a new version, and the point of the flag is completely lost. It is also a blocker for my work in the feature-authorization-context branch. Fixing this was non-trivial. It is assumed everywhere that the content dirty will be set, not only when the document content changes, but also when a property, the xclass or any attachment changes. But there were no code that actually set the flag on updates (because it was always true anyway). What's worse is that we have API methods that returns lists that are live updateable. I have added a wrapper list class to detect the updates in these lists. Hibernate refuse to store elements from my wrapper list for some reason which forced me to add a workaround for hibernate. Surprisingly, Clirr doesn't require any exception for the below methods which I have added, but I will list them here for your information: In BaseClass: public void setOwnerDocument(XWikiDocument ownerDocument) public void setDirty(boolean isDirty) In BaseProperty: public boolean isValueDirty() protected void setValueDirty(Object newValue) public void setValueDirty(boolean valueDirty) public void setOwnerDocument(XWikiDocument ownerDocument) In ListProperty: public void setUseHibernateWorkaround(boolean useHibernateWorkaround) In XWikiAttachmentContent: public void setOwnerDocument(XWikiDocument ownerDocument) New class: AbstractNotifyOnUpdateList<E> Best Regards, /Andreas

12 years, 10 months

2
2
0 0

[xwiki-devs] Release Manager for 4.3M2 needed ASAP!

by Vincent Massol

Hi devs, We need a RM for 4.3M2 which should have been released yesterday... See the Roster to see if you'd be a good candidate: http://dev.xwiki.org/xwiki/bin/view/Community/ReleaseManagerRoster If you haven't done a lot of releases yet then you're a good candidate ;) Thanks -Vincent

12 years, 10 months

1
0
0 0

[xwiki-devs] Improved User Picker

by Marius Dumitru Florea

Hi devs, I committed an improved User Picker in the feature-xclass-property-component branch. You can see some images on http://jira.xwiki.org/browse/XWIKI-4022 . I'd like to integrate it in the platform. Thanks, Marius [1] https://github.com/xwiki/xwiki-platform/compare/feature-xclass-property-com…

12 years, 10 months

6
5
0 0

[xwiki-devs] [VOTE] Name of the localization module script service

by Thomas Mortagne

Hi devs, Quick vote on the name of the localization module: * $services.l10n * $services.localization something else ? I'm ok with both even if "localization" is a bit "cleaner". -- Thomas Mortagne

12 years, 10 months

7
7
0 0

[xwiki-devs] [VOTE] Name of the localization macro name

by Thomas Mortagne

Hi devs, Quick vote for the macro name: * {{l10n}} * {{locallization}} localization is a bit too long for a macro so I would go for "l10n". We can also decide to maintain both aliases. -- Thomas Mortagne

12 years, 10 months

7
13
0 0

[xwiki-devs] How to Include a page without velocity code into another page

by Geo Du

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? Thanks very much for your help. David

12 years, 10 months

2
2
0 0

[xwiki-devs] [Vote] Use the Date Picker from AppWithinMinutes as the default picker for Date XClass properties

by Marius Dumitru Florea

Here's the commit https://github.com/xwiki/xwiki-platform/commit/a6f4bd499fc2b1cf3757d423205a… . The main changes are: * Move the JS/CSS of the date picker used by AppWithinMinutes into the file system (/resources/uicomponents/widgets/datepicker). * Apply checkstyle to DateProperty and DateClass. * Modify DateClass to use the AWM date picker when the 'picker' meta property is set. * Add back the 'picker' meta property to Date property (in DateMetaClass) to allow developers to use a different picker than the default one (or no picker at all). * Use Boolean property for 'picker' and 'emptyIsToday' meta properties (was Number property). Since a Boolean property is stored as an integer property the only difference will be visually (checkbox instead of text input). I'd like to merge this into the platform. My +1. Thanks, Marius

12 years, 10 months

4
4
0 0

[xwiki-devs] [VOTE] Add xwiki-platform-wiki-manager-api as a dependency for XE - Pull request "Add REST APIs for creating wikis and importing XARs"

by Fabio Mancinelli

Hi everybody, I will try to go forward in committing REST API improvements made by Ludovic and me. Looking at the discussion about the pull request I opened https://github.com/xwiki/xwiki-platform/pull/68 Thomas pointed out the fact that it brings "xwiki-platform-wiki-manager-api" as a dependency in XE, and this might require a vote. xwiki-platform-wiki-manager-api is something that was bundled only in XEM and not in XE. I added it as a dependency because I use its code for performing wiki creation and XAR importing. Thomas' comment is here: https://github.com/xwiki/xwiki-platform/pull/68#discussion_r1335333 So the vote is about the bundling of xwiki-platform-wiki-manager-api in XE for merging this pull request. I am +1, of course. Thanks, Fabio

12 years, 10 months

3
5
0 0

[xwiki-devs] [VOTE] Merge feature-localization branch to master

by Thomas Mortagne

Hi devs, I would like to merge the https://github.com/xwiki/xwiki-platform/tree/feature-localization branch to master. Here is a summary of what it contains: * new localization module API following what described in http://markmail.org/message/blynasgz53ys345i * implementation of this API for ApplicationResources resources and document bundles listed in the preferences * implementation of this API for dynamically registered wiki document translations as described on http://markmail.org/message/bcmbhpwxnbagma3g Here is my +1. Thanks, -- Thomas Mortagne

12 years, 10 months

7
7
0 0

[xwiki-devs] [VOTE] Property declarations for the execution context

by Andreas Jonsson

Hi Everyone, I would like you to vote on merging the feature-execution-context branches of commons and platform before the release of 4.3M2: https://github.com/xwiki/xwiki-commons/compare/master...feature-execution-c… https://github.com/xwiki/xwiki-platform/compare/master...feature-execution-… Explanation of the feature: The execution context is a simple map that binds a string to an object. This can be compared to how variables are handled by scripting languages such as bash, where an assignment brings the variable into existance: $ my_variable="some value" In the case of the execution context, the syntax is: context.setProperty("my_variable", "some value"); This feature is about adding property declarations, where a property can be associated with attributes that controls how the execution context and execution context manager handles the property. The general idea can, once again, be compared to bash and how it is possible to declare variables there: $ declare -ru my_variable="read only, forced upper case" Of course, the set of attributes that are interesting to us is different from bash. Currently the feature branch have support for declaring properties with these attributes: * Final - The value may not be updated within the the execution context. Default: false. * Inherited - The property will be inherited from the current context when replacing the execution context within the current scope. Default: false. * Cloned value - Also clone the value when the execution context is cloned. Default: false. * Type - The class of the value, for typechecking when setting the value. Default: null (unchecked). * Non-null - The value may not be null, checked when setting the value. Default: false. Example declaration: ExecutionContextProperty property = new ExecutionContextProperty("my_variable"); property.setValue("some value"); property.setType(String.class); property.setInherited(true); context.declareProperty(property); The property value may be updated and the property may be removed and redeclared, unless declared 'final': context.setProperty("my_variable", "some new value"); context.removeProperty("my_variable"); Additional attributes may be added later. This feature is also backwards compliant, in that implicit declaration by just setting a value is allowed. (Although we might want to make explicit declarations mandatory in the future.) Within the scope of a request, or the life time of a thread executing some administrative task (e.g., the lucene index updater) the basic life cycle of the execution context is the following: @Inject Execution execution; @Inject ExecutionContextManager ecm; ExecutionContext context = new ExecutionContext(); ecm.initialize(context); try { // Do work } finally { ecm.removeContext(); } Within the life cycle of the "root" execution context, we may push a new execution context, which may either be a clean context, or a clone of the current context: // Pushing a clone ExecutionContext context = ecm.clone(execution.getContext()); execution.pushContext(context); try { // Do work } finally { execution.popContext(); } // Pushing a clean context ExecutionContext context = new ExecutionContext(); execution.pushContext(context); try { // Do work } finally { execution.popContext(); } Component authors that needs to place a value in the execution context provides an initializer that declares the variable and sets an initial value. The attributes 'final', 'cloned value', and 'inherited' lets component authors control how the value is managed during the lifecycle of the root execution context. The attributes 'type' and 'non-null' provides some runtime assertions to catch some errors earlier. So to summarize, this feature: 1. is a convenient mechanism for managing properties in the execution context, 2. provides some validation of the property values, 3. improves performance slightly by avoiding unnecessary cloning. For more information, see the proposal thread: http://xwiki.475771.n2.nabble.com/PROPOSAL-Execution-context-property-decla… Best Regards, /Andreas

12 years, 10 months

4
7
0 0

Re: [xwiki-devs] Remove or change menu

by Geo Du

Can anybody shed any lights on this topic? from the default standard deployment of the xwiki, it has the menus like Add, Wiki, Space, Page, I need to change or remove these kind menus as I described in the question. Thanks David On Fri, Oct 26, 2012 at 9:20 PM, Geo Du <dddu88(a)gmail.com> wrote: > Hi all, > > I like to remove some of the menu items based on the user logged in, for > example for one type of users, I need to remove the Add menu, or change > Wiki, Space or Page menus to my own menus, I checked the users rights, it > has View, Comment, Edit, Delete, Register, Program, they seem not designed > for that, any suggestions? I checked menuview.vm, that is where to control > the menus, it seems I need to change this file. > > Thanks for your suggestions in advance. > > David >

12 years, 10 months

1
0
0 0

[xwiki-devs] JAR Duplicates in 4.3 Milestone 1 and SNAPSHOT

by Sorin Burjan

Hello everybody, After the release of 4.3 Milestone 1, I wanted to start testing the new features but I ran into an issue ( http://jira.xwiki.org/browse/XWIKI-8365 ) when starting and accessing the Wiki based on 4.3 M1. After Marius helped me figure out the cause, it seemed that we had a jar duplication of Xalan in our Manager package. I have tested this on another machine and wasn't able to reproduce. Fabio also tested, without success, but the duplication is clear - I had 2 Xalan jars in my /lib folder (even on the machine where I had no errors). After that, I started to look for other duplicates in my /lib folder. Below are my findings. Checked these 2 XWiki packages to be sure it's not package dependant: * xwiki-manager-jetty-hsqldb * xwiki-manager-jetty-mysql Found the following JAR duplicates: 1) activation-1.1.1.jar activation-1.1.jar 2) commons-lang3-3.1.1jar commons-lang-2.6.jar 3) jdom-1.0 jdom-1.1.jar 4) plexus-utils-2.0.6.jar plexus-utils-2.0.7.jar 5) rome-0.9.jar rome-1.0.0.jar rome 1.0.jar 6) vorbis-java-core-0.1.jar vorbis-java-core-0.1-tests.jar 7) xercesImpl-2.9.1.jar xercesImpl-2.8.1.jar After the release of 4.3 M1 I have also downloaded a 4.3-SNAPSHOT build (xwiki-manager-jetty-hsqldb-4.3-20121025.181227-95.zip). Besides the duplicates from above, I have also found a lot of XWiki jars duplicated. Note, the list if far from being complete ! xwiki-commons-classloader-api-4.3-20121024.173322-34.jar xwiki-commons-classloader-api-4.3-SNAPSHOT.jar xwiki-commons-classloader-protocol-jar-4.3-20121024.173330-34.jar xwiki-commons-classloader-protocol-jar-4.3-SNAPSHOT.jar xwiki-commons-component-observation-4.3-20121024.173347-34.jar xwiki-commons-component-observation-4.3-SNAPSHOT.jar xwiki-commons-configuration-api-4.3-20121024.173413-34.jar xwiki-commons-configuration-api-4.3-SNAPSHOT.jar xwiki-commons-context-4.3-20121024.173359-34.jar xwiki-commons-context-4.3-SNAPSHOT.jar xwiki-commons-diff-api-4.3-20121024.173722-33.jar xwiki-commons-diff-api-4.3-SNAPSHOT.jar xwiki-platform-bridge-4.3-20121025.165136-181.jar xwiki-platform-bridge-4.3-20121025.174305-182.jar xwiki-platform-cache-api-4.3-20121025.165403-177.jar xwiki-platform-cache-api-4.3-20121025.174540-178.jar xwiki-platform-cache-infinispan-4.3-20121025.165428-177.jar xwiki-platform-cache-infinispan-4.3-20121025.174606-178.jar xwiki-rendering-transformation-icon-4.3-20121024.193826-57.jar xwiki-rendering-transformation-icon-4.3-SNAPSHOT.jar xwiki-rendering-transformation-linkchecker-4.3-20121024.193846-57.jar xwiki-rendering-transformation-macro-4.3-20121024.193051-57.jar xwiki-rendering-transformation-macro-4.3-SNAPSHOT.jar xwiki-rendering-transformation-wikiword-4.3-20121024.193833-57.jar xwiki-rendering-transformation-wikiword-4.3-SNAPSHOT.jar Items statistics: /lib folder on SNAPSHOT : 126.6 MB - 445 Items /lib folder on Milestone 1: 126.3 MB - 392 Items The odd thing is that I do not get any warnings, errors, stacktraces when starting the 4.3-SNAPSHOT. I wrote this mail to report the issue, because IMO this can cause serious issues. Regards, Sorin B.

12 years, 10 months

5
7
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs