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

[xwiki-devs] Future of mailsender plugin

by Ludovic Dubost

Hi, I wanted to discuss about the future of the mailsender plugin ? I've been working on a small tool to be able to send a Calendar Invitation by email from a Meeting Notes AppWithinMinutes application and I found some limitation in the mailsender plugin, namely you cannot add multipart alternative email parts in addition to the text and html parts already supported by the plugin. I was able to hack the mailsender plugin to add a vcalendar part but it does not really sound right to do that since we should support any part of any content type, but this is a bigger refactoring. I was wondering what the future is for the mailsender plugin. Do we plan to make it a component and keep the same functionality ? Is there a plan for an alternative component ? And what would be the approach to add a vcalendar part in emails sent by the current mailsender ? This would be needed to support the feature of sending invitation emails which would be very powerfull. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

12 years, 7 months

6
27
0 0

[xwiki-devs] [ANN] XWiki 4.5 released

by Vincent Massol

The XWiki development team is proud to announce the availability of XWiki 4.5. This version brings improvements and stabilization to the Extension Manager and Distribution Wizards. It also adds the ability to internationalize applications created with the App Within Minutes tool, and continues the improvements of the new experimental Solr search integration. This is the last release of the XWiki 4.x cycle. 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/ReleaseNotesXWiki45 Thanks -The XWiki dev team

12 years, 7 months

1
0
0 0

[xwiki-devs] OpenFire xwiki integration?

by Paul Libbrecht

Hello fellow XWiki developers, I was wondering if anyone had taken the time to have a joint install of XWiki and OpenFire, apparently a fairly scalable XMPP server with nice feature completeness. Something should be done at the UI level, such as candy-chat probably. My question is more about the server side, there seems to be a way to write an adapter to fetch user-information from a database, so that exposing users of XWiki might be simple. Did anyone try this already? Did it scale? thanks in advance paul

12 years, 7 months

6
8
0 0

[xwiki-devs] [VOTE] Make UTF-8 mandatory for a valid installation

by Sergiu Dumitriu

Hi devs, We've moved more and more toward an UTF-8-only application, and XWiki has only been tested with this configuration for several years. I propose that we require UTF-8 for a valid, supported installation. This means: - JVM encoding (-Dfile.encoding=UTF8) - Container default URL encoding (Tomcat has ISO-8859-1 by default) - Database encoding (MySql is still configured with latin1 on some distros) There's one big site to update on our side: xwiki.org. Here's my +1. This is a move toward a future web, since more and more standards require (or at least assume as a default) UTF-8. After thinking a bit more, it would make sense to require a valid Unicode encoding, including UTF-16, which is preferable in countries that don't use a latin alphabet. However, XWiki doesn't currently work under 16-bit encodings at all. -- Sergiu Dumitriu http://purl.org/net/sergiu

12 years, 7 months

8
12
0 0

[xwiki-devs] [Proposal] Naming scheme for e.x.o extensions

by Vincent Massol

Hi, I'd like to propose to use the following naming conventions for the extensions from commons/rendering/platform that are exposed on e.x.o: - "API" suffix for api modules. e.g. "Text API" , "Velocity API" instead of currently "Text Module", "Velocity Module", etc - "Application" suffix for ui modules, e.g. "Wiki Manager Application", "Logging Application", "IRC Bot Application", etc - "Macro" suffix, e.g. "JIRA Macro", etc Technically this means using the following in pom.xml: <properties>  <xwiki.extension.name>Wiki Component API</xwiki.extension.name> </properties> WDYT? Thanks -Vincent

12 years, 7 months

3
5
0 0

[xwiki-devs] Testing some JVM Analysis Tool

by Ludovic Dubost

Hi, I've been testing newrelic which has some interesting live JVM analysis. I've been running the JVM Profiling while running a load test going on various XWiki pages (except activity stream) including AWM, LiveTable Searches, Content pages, Lucene search and loading ressources. Here is a result of the profiling: 25.0% - java.net.SocketInputStream.socketRead0 32 Collapsed methods (show) 25.0% - com.xpn.xwiki.store.hibernate.query.HqlQueryExecutor.execute 21.0% - org.xwiki.query.internal.DefaultQueryExecutorManager.execute 11.0% - org.xwiki.query.internal.DefaultQuery.execute 127 Collapsed methods (show) 11.0% - java.lang.Thread.run 9.9% - org.xwiki.query.internal.SecureQueryExecutorManager.execute 4.2% - com.xpn.xwiki.store.hibernate.query.DefaultQueryExecutor.execute 12.0% - org.apache.velocity.runtime.parser.node.SimpleNode.render 12.0% - org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate 12.0% - org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate 8.1% - org.xwiki.rendering.internal.macro.velocity.VelocityMacro.evaluateString 4.3% - com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate 9.2% - org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate 8.5% - com.xpn.xwiki.render.DefaultVelocityManager.getVelocityEngine 4.1% - org.apache.velocity.runtime.parser.node.ASTBlock.render 4.1% - com.xpn.xwiki.web.XWikiAction.execute 3.6% - org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transformOnce 3.2% - org.apache.velocity.runtime.directive.Foreach.render 2.9% - org.xwiki.rendering.wikimodel.xwiki.xwiki21.javacc.XWikiScanner.docElements 2.8% - com.xpn.xwiki.plugin.lucene.SearchResults.getRelevantResults 2.6% - com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate 2.4% - com.mysql.jdbc.PreparedStatement.executeQuery 2.4% - org.xwiki.uiextension.internal.WikiUIExtension.getParameters 2.3% - org.xwiki.rendering.wikimodel.xwiki.xwiki21.javacc.XWikiScanner.line My understanding is that we spend 25% of time reading from the DB (this could be livetable related for instance). Around 50 in various velocity parts. Around 10% in the XWiki rendering and 3% in Lucene search. 2,4% in UI extensions (no visible rights, probably because running as Admin) Velocity is clearly quite expensive. Now I see particularly: 8.5% - com.xpn.xwiki.render.DefaultVelocityManager.getVelocityEngine Would this mean we are spending 8,5% of the time getting the velocity engine to use ? This sounds a lot. In any case this is food for thoughts for future optimizations. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

12 years, 7 months

3
6
0 0

[xwiki-devs] Free Web-based diagraming tool

by Roman Muntyanu

Hi Devs! Thought you might be interested http://www.diagram.ly/ Roman Muntyanu | rmuntyan(a)softserveinc.com<mailto:rmuntyan@softserveinc.com> | Project Manager | SoftServe<http://www.softserveinc.com/> Inc. | +380-32-240-9090 x3738

12 years, 7 months

2
1
0 0

[xwiki-devs] [Brainstorming] Handling "young" APIs for backward compatibility

by Vincent Massol

Hi devs, We have recently voted a rule where we said that we will do the following: * Always deprecate APIs * Always move them to Legacy modules * And when there's a technical issue to moving stuff to the Legacy module, only then, send a VOTE to remove an API (see http://markmail.org/message/tino4ngttflc5i3s). This means that from now on (starting on 26th of April 2012) we're not allowed to put excludes in CLIRR. However I've seen that we have added some CLIRR excludes after the vote was passed. I believe that the main issue we have is for "young" APIs that are not considered stable. Proposal 1: Internal package ========= * Young APIs must be located in the "internal" package till they become stable. I propose "internal" to reuse an existing package that we filter when testing for CLIRR. "internal" means that users should not use this API because it's considered unstable and can change at any time. * When a Young API is considered stable enough and we want to open it to public consumption then we move it from "internal" to its target package (that's easy to with IDEs). From that point forward any changes to them goes through the standard mechanism of deprecation/legacy. * If we want to add a new method to an existing public API then this should not be considered a "young" API. It's just an addition to an existing API and thus goes directly to the deprecation/legacy cycle. * We need to be careful to isolate "young" APIs from public API so that users don't inadvertently use "young" unstable APIs by mistake. If not possible then directly go through the deprecation/legacy cycle. The advantage of this proposal is that it doesn't change our current practices and is very easy to verify through CLIRR. Proposal 2: Experimental package ========= Another possibility I can think of is to introduce a new "experimental" package instead of reusing the "internal" one. It has the advantage of being able to follow "young" APIs and ensure they don't stay in that state indefinitely, while still allowing the user who uses it to notice it's experimental. Proposal 3: Experimental Annotation ========= Another idea is to just use an @Experimental javadoc tag for experimental code. It has the advantage of using the target package but it has drawbacks: * It's impossible for users to notice that they're using Experimental APIs since when they import a class they won't see anything that'll tell them they're using a "young" API * It's almost impossible to tell CLIRR to exclude those APIs from its checks. The only way to do this is to modify the source code of the CLIRR plugin AFAIK. Thus we would need to exclude those manually using CLIRR excludes and thus before we release we would need to go over the full list of CLIRR excludes to ensure the excludes listed are only for "young" APIs marked "experimental". Note that I mentioned javadoc tag and not annotation because I believe we need to add information about when the Experimental API was first introduced so that we eventually move it as a proper API by removing the Experimental tag. Maybe we would need a rule such as: keep that tag for less or equal to 3 full minor releases (i.e. 6 months). WDYT? Any other idea? Thanks -Vincent

12 years, 7 months

8
25
0 0

[xwiki-devs] [Contrib] Meeting and File Manager applications

by Thomas Delafosse

Hi devs, I'm currently working on two new applications : Meeting and File Manager. I've already published a first version of them on extensions.xwiki.org ( http://extensions.xwiki.org/xwiki/bin/view/Extension/Meeting+Applicationand http://extensions.xwiki.org/xwiki/bin/view/Extension/File+Manager+Applicati…), and now I would need a folder on github (my github user name is tdelafosse) and a maven groupID for each of them so I can release them with maven. Thanks, Thomas

12 years, 7 months

2
1
0 0

[xwiki-devs] [Notice] Removing all teams on xwiki-contrib on github except a few

by Vincent Massol

Hi devs, So far I've always created a new Team for new repos on xwiki-contrib. This is a bit too high maintenance and in addition it doesn't help for cross-project collaboration. Thus I'm going to remove them in the coming minutes and I'll keep only the following teams: * currikiorg * gsoc * xclams* * xwikiorg Basically I'll fold all users currently on the other teams into xwikiorg. Thanks -Vincent

12 years, 7 months

1
0
0 0

[xwiki-devs] JIRA cleanup for missing fixversion

by Vincent Massol

Hi guys, Can you help me fix all those issues that are missing fixfor? http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=status… Thanks -Vincent

12 years, 7 months

3
5
0 0

[xwiki-devs] [VOTE] Skip tests while building a release

by Eduard Moraru

Hi devs, Well, the subject pretty much sums it up. I am proposing to skip any testing while building a release, since that is the job of the CI infrastructure and, it happened more than once for the build of the release to fail because of a flickering test. This is really annoying for a release manager that has to start over the entire build (since right now it's a real pain to alter the scripts to continue the build). Besides this, tests (specially the functional ones added into platform) uselessly delay the build, thus, the release. Note: We are already skipping tests for enterprise and manager. This vote is actually about skipping tests for commons, rendering and platform as well. Here's my +1. Thanks, Eduard

12 years, 7 months

5
8
0 0

[xwiki-devs] Provide translations in JAR extensions

by Thomas Mortagne

Hi devs, The last piece missing to the new localization framework for 4.x is to allow providing translations in a jar extension. Here are some ideas: 1) Continue with ApplicationResources_*.properties files but loads it from everywhere instead of taking the first one we find like now 2) Same that 1) but place it somewhere a bit "cleaner" like org/xwiki/localization/translation_*.properties 3) Completely different system. I looked a bit if any simple de facto standard was already existing but was not obvious. Keep in mind the localization framework allow providing any source so it's easy to move/add a new way to get translations in jar extensions later without touching the API so while it would be better to do something good it's mostly implementation details and whatever we choose we are not going to be stuck with it forever. WDYT ? I would go for 2) (I'm +0 for 1)) with org/xwiki/localization/translation_*.properties for 4.x and keep 3) for later when we have some time to work on it a bit more. -- Thomas Mortagne

12 years, 7 months

4
7
0 0

[xwiki-devs] Fwd: [xwiki-infra] vxwikiorgfarm: wiki is not responding!(real URL)

by Caleb James DeLisle

20 threads blocked on: at com.xpn.xwiki.render.DefaultVelocityManager.getVelocityEngine(DefaultVelocityManager.java:177) - waiting to lock <0x637cbe38> (a com.xpn.xwiki.render.DefaultVelocityManager) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:105) https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… The holder of this lock calls context.getWiki().getSkinFile("macros.vm", skin, context); and context.getWiki().exists(skin, context), both of which potentially access the database while holding a global lock. Looks like some delicious low hanging fruit to me. Thanks, Caleb Original message removed because it is too big for the list. See it here: https://ezcrypt.it/4H5n#8mjU1voDtZsANw9vsLa8WM8Y

12 years, 7 months

2
1
0 0

[xwiki-devs] [Contrib] Classification Extension

by Thomas Delafosse

Hi devs, I would need a contrib repo for an extension I've developped for USH. It is called Classification and enables to create easily a classification plan with categories and sub-categories. Apparently such a feature is often needed on client project, so I hope it could be useful. Thanks, Thomas

12 years, 7 months

3
3
0 0

[xwiki-devs] [VOTE] Get rid of Portlet API in oldcore

by Thomas Mortagne

Hi guys, oldcore contains references to Portlet API 1.0 in various API. There is several issues: 1) Thoses API are useless since most of the code expect a servlet and would never work inside a Portlet so that make this API totally useless 2) It's a real pain for things like https://github.com/xwiki-contrib/sandbox/tree/master/xwiki-portlet (a portlet proxy/translator in front of XWiki) since it makes impossible to use Portlet API 2.0 (we had to create our own special branch were we remove all reference to 1.0 API in oldcore) 3) XWiki cannot work without the portlet jar even when used as Servlet which is quite ugly Since we are starting a new major version and it's a breaking change I propose to do it now. Here is my +1 -- Thomas Mortagne

12 years, 7 months

4
5
0 0

[xwiki-devs] [Contrib] xwiki-application-mailarchive

by Jeremie BOUSQUET

Dear community, I would like to request for a new contrib project to store the Mail Archive application I'm currently writing. Name: xwiki-application-mailarchive Description: A mailing-list archive application. - For now a GitHub project to store sources should be fine. My username on GitHub is "jbousque". - For Jira it might be useful to have a project once the application is released "officially", that is still not the case. Meanwhile the generic project is ok for me. - There is a specific page in Design space on xwiki.org : http://dev.xwiki.org/xwiki/bin/view/Design/MailArchiveApplication , but for now no extension has been added. I would like if possible to test my extension (automatic install with dependencies) before publishing it The Design page also gives some info about the current state and progress, and some screenshots. There is many remaining work, but it begins to look like something usable. The bad side is the lack of unit tests most of all ... A question : the groupId "org.xwiki.contrib" is to be used, do I have to use this exact groupId or can there be sublevels if needed ? If so I would use org.xwiki.contrib.mailarchive as groupId. Thanks, Jeremie

12 years, 7 months

6
87
0 0

[xwiki-devs] [Idea]"Community" flavor

by Jeremie BOUSQUET

Hi xwiki devs, Don't know if it's really the right place, but something strikes me when re-reading the thread about XWiki development flavor, fosdem feedback from Ludovic, last extensions posted on xwiki.org, and my own requests / use-cases I have in my office ..., and I just wanted to share my thoughts with no particular expectation. At least in my office, the "big thing" these days is community building. The intent to materialize "communities", that could be around subjects as business interests, technical interests, skills, ... Currently our difficulty is that we have some "bricks", but they are spread amongst several tools and not integrated. For example mailing-lists were defined in mail server (in fact, distribution lists with owner), the reason why I created the MailArchive application in first place, to archive these mails somewhere browsable and searchable. But when I see the "Newsletter application", the "Meeting application", the Workspace feature, I can't help but think that ideally all these should/could be linked together to materialize that "community" thing. For example community members could be a ldap or xwiki group of users. Shared space for the community could be a xwiki Workspace, with workspace owner as guardian. Newsletters templates could be automatically generated for that community, using community members as first newsletter target (using a mailing-list address or a list of distinct persons). Other persons of a community could have a "view" access to it (workspace, newsletter targets) if they decide to (or are volunteered into by community owner). The workspace of a community could come from a template, showing configured newsletter, and a default mail archive with view on specific mailing-list(s) for that community. There could be a documentation part (space?) with easy export to .doc/.pdf of multiple pages. The "topics" of that community could be materialized as blog categories, and suggested as tags for othere pages... That "flavor" would not be particularly "social" (meaning, connected with facebook...) nor "dev", still reuse existing components and add some glue between them. As far as I know it could be merely a Workspace template, but I don't know if such workspace template could easily be packaged and contributed as an extension (should be). Comes also the idea that "flavors" could have some hierarchy, for example, the "dev" flavor could be built on top of such "community" flavor, extending it with other specific integrations (jira, ...). Also brings the idea of optional dependencies between extensions. Is there an (easy) way to know, for an extension, if a prerequisite extension is installed ? (something from EM public API for example). Currently I just check for specific page existence, or for specific $service... call, to infer that another extension is already installed. For example you could decide to create meetings from mail archive app, if and only if the Meeting application is already installed. Integration of remote systems is nice, but cross-integration of existing extensions would be even nicer to start with :-) BR, Jeremie

12 years, 7 months

2
2
0 0

[xwiki-devs] FOSDEM Feedback

by Ludovic Dubost

Hi, We were 9 xwikiers at FOSDEM this week-end and I wanted to take the occasion to give some feedback on what I saw there. The Community Dev Room ----------------------------------------- First XWikiers participated in the devroom co-organized by Sergiu: "Community Development and Marketing". The great news is that the room was full quite a big amount of the time. It was not a huge room but well placed (in the "original" area of FOSDEM which is still quite active). I think it shows more and more interest of people for this subjects which are less usual at FOSDEM which is very technological. Kudos to Sergiu for co-organizing this dev room. There was also a keynote from Kohsuke Kawaguchi (creator of jenkins) on how the jenkins community was build which was on a similar subject as the dev room (I'll give some feedback on the talk below). Sergiu has a presentation about "how to cope with a proliferation of tools in your community" which presented how XWiki can be used to be a portal to all the contents of all the tools you have in your community (aka "the dev flavor). The content of the talk was great but to my taste it was really missing screenshots to show practically what happens. There was a mini demo at the end but it was not enough to really make people realize how great xwiki.org is :) But the idea of the presentation is great and if we can spend a bit of time to not necessarly make the flavor, but publish the different pieces of xwiki.org as extensions, including some simple macros we are using (like how we integrate nabble). There was the 1M$ question of if we can migrate existing wikis to which we could have answered a bit better as we do have a few migrators for some specific wikis (Mediawiki, dokuwiki) but nothing fully done and fully generic. This is another area were we could spend some time making some specific migrators easier to use. If there are any contributors that would like to help out improving and publishing the migrators and "dev extensions" on extension.xwiki.org as well as document how other communities could use our tools, it would be very useful to help spread the XWiki work out there. Sergiu should publish his slides and maybe somebody can improve them with screenshots. Vincent and myself had a "devil (business) and angel (open source)" presentation on "Combining Open Source ethics with private interests". 20 minutes was a bit short to cover this subject fully in details but it was great to be able to share our experience on this. The room was quite full when we did this presentation and there were a few questions which I believe showed the interest of participants with this subject. Vincent will publish the slides although it's not easy to follow without the additional "talking". We should definitively try to do this again. MySQL and Security ------------------------------ I attended a few MySQL presentations as well as some security presentations. There seems to be some interesting improvements in InnoDB in MySQL 5.5 and 5.6 (currently RC) and even MariaDB and Percona have some work that improve InnoDB (with XTraDB). As we are planning to work on performance we should look into testing how XWiki behaves on MySQL 5.1 to 5.6 and compare the performance also with Postgres. In any case we should follow what is happening in this area. On security there was a presentation about OWASP ZAP ( https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project) and attack proxy to test the security of Web Applications. This is something to look at for the Thomas D's coming work on security. Kohshuke presentation on Jenkins community ------------------------------------------------------------------- On the "community" subject there was interesting presentations about "how to cope with assholes in your community" and the presentation of Kohshuke. To summarize very quickly while Kohshuke says part of the big reasons why jenkins has been succesful is "good software" and "being there at the right time" he would like to believe that the way the community is run and the software is architectured has a lot to do with this success. Some important items: - small core with apis, many extensions, extensions are "first-class citizens" of jenkins - very extensible - very open to contribute an extension with almost automatic commit right (with an IRC bot to get a rights) What we can learn for XWiki ----------------------------------------- There are a few things to learn here for XWiki I believe: XWiki has a lot of what is said here, particularly the extensibility but we could "finish" things a bit more with these learnings in mind. XWiki is very extensible in many areas (but not all, like the old core). It is very easy to publish an extension, particularly a XAR file on extensions.xwiki.org and we have extension manager to install this extension. However there are a few things we can do better: 1/ On the java side, contributing is still difficult. The core is still big and not well defined. In the "platform" repository we have many different things, including modules that are not vital to the XWiki core and that could be maintained by contributors. Our development rules and methodologies are very "strict" when it comes to the "platform", "commons" or "rendering" and since many many things are published there it's not easy to participate there. If we separated a bit the "real core" from the additional modules that depend on the core apis but are not as critical to the core, and we move the additional modules to an area with potentially less stricts rules of development and where each developer can decide his own rules, maybe we would greatly improve potential contributions. It's also a question of how we "consider" the extensions and we publish information about them and recognize them when they end up in the default install. More on this below. 2/ On the xar/scripting side, it's "almost" easy to publish something and make it available thanks to EM but there are a few quirks that we need to solve: - Exporting a XAR is not fully supported by the core (we need Admin Tools and it's not enough documented). - Committing your work is not easy which makes it more complicated to get contributors to extend an existing extension. But the good news is that we are quite close: - AppWithinMinutes has an extension to publish an application on Extension Repository - SVN and GitHub app allow to commit XWiki pages - Maven allows to build and release an XWiki app - Admin Tools has ways to export multiple pages - XEM code has an "Application Descriptor" which could be useful for not AWM code If we bind all these together a bit more we can have a killer. Let's image the following: 1/ In an admin area you go to "Extensions" and you have a button to "create a local extension" and can add XWiki pages to your extension which would add your pages to an "Extension descriptor" 2/ AWM would automatically use this extension descriptor. 3/ You would have a way to: - ask for a git repository for your extension - commit your extension from XWiki - release your extension from XWiki and publish it on extensions.xwiki.org - allow another user to install this extension using EM and then decide to fork it, modify it and commit the changes and create a pull request for the changes - finish the contribution loop 4/ On extensions.xwiki.org you could see who the contributors are for the extension and what they committed. Then you have an even more powerful way to contribute to XWiki, wether it is an AWM application or just a snippet of code. Aside from that we should make it a bit easier through documentation or tools mainly) to publish java code as it is still slightly complicated to make it easily installed using EM. More important even would be to continue improving AWM to make it easier to add Javascript, CSS or REST apis to an application but this is another story for more complex applications. This is food for thoughts to allow XWiki to get more help from new committers which is a great solution to help XWiki spread more. On the spreading subject, I also think we should make more effort to publish some "mashup" macros or snippets and publish them both on extensions.xwiki.orgas well on the other projects extensions or plugins pages. This would help show how easy it is to integrate XWiki with other tools. I was quite happy with this year's FOSDEM. It's getting more and more interesting. Open Source is alive and kicking. We could push for happing a "Web Application Dev Room" (we tried to get a "wiki one"), as there is not much on this subject. There was a "web development" track but it was a bit empty. Maybe this is an area to work on to get Wikis, CMS tools, Web and Javascript frameworks presented. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

12 years, 7 months

4
4
0 0

[xwiki-devs] [PROPOSAL] Include require.js in XWiki by default and make jQuery available through require.js.

by Caleb James DeLisle

Hi, I'd like to add require.js to XWiki to be included in every page just before prototype.js. I would also like to add jQuery to our resources directory but only make it available to scripts which "pull it in" using require(). I have come to the conclusion that jQuery is a de-facto standard and even if we don't port to it, we should make it available to our users. Require.js is an implementation of the Asynchronous Module Definition standard which will allow us to use both jQuery and prototype relatively harmoniously. I think it's obvious that if javascript rich webapps are going to scale, they need modularity and I've reviewed AMD and the main competitor CommonJS and concluded that AMD will provide the user with better page load time by asynchronously loading modules according to a dependency tree while CommonJS blocks on each call to require(). I would like to see us move away from prototype but it provides more functionality than jQuery including an OOP framework and while there are other libraries which show promise, I don't feel right proposing a best practice without first porting some code to it to see what issues arise so IMO we should begin using require.js but accept that prototype still has it's place. So I propose: Include require in the header vm. Include jQuery but only if a script "require()'s" it. Establish a best practice of using require() and define() instead of global variables but accept that prototype.js still has it's place. WDYT? Caleb miscellany: ------------------------------ require.js vital statistics: Dual licensed BSD and MIT. Latest Release: 2.1.2 1,993 lines before minification 24,621 lines in every .js file in the /tests/ directory. Used by: https://github.com/adobe/brackets/ https://github.com/ajaxorg/cloud9 (https://c9.io/) http://browserquest.mozilla.org/ http://www.bbc.co.uk/frameworks/barlesque/examples/global/requirejs http://www.officejs.org/ ----------------------------- Optimization: require.js comes with a tool for linting, compiling (using Closure Compiler), and linking AMD modules together based on their dependencies. Complex projects with many js files can be can be compiled into a single "statically linked" js file. It supports Rhino so it could be included in the maven build. ----------------------------- My experimentation with require.js: I use the require.js legacy shim to make jquery.sheet function as a require.js module without making any direct changes to jquery.sheet. I was able to move the code from XWiki to the filesystem (file:///) a total change of the directory structure and only needed to change the main example.html file. I was able to include the content in an iframe simply by defining a require.js plugin see: http://requirejs.org/docs/plugins.html for loading through an iframe and changing the require() call to require the iframe'd sheet. https://github.com/cjdelisle/jquery-sheet-amd

12 years, 7 months

5
4
0 0

[xwiki-devs] FAQ Application Tutorial

by Paul-Catalin Cojan

Hello devs, I wrote a tutorial on "How to create a FAQ application with APP Within Minutes": http://dev.xwiki.org/xwiki/bin/view/Drafts/FAQ++Application+with+AWM+Tutori…. Is it ok to add it on the "Tutorials and Guides" section? Thank you, Paul.

12 years, 7 months

3
2
0 0

[xwiki-devs] [Brainstorming] Sources of HTML and ability to use pre-made CSS like Bootstrap

by Denis Gervalle

Hi Devs, As you may have noted from a previous mail, I have given a try to skin XWiki differently, based on Bootstrap. There is certainly many ways to get it done, but IMO, building over any pre-made css solution requires an adaptation of the HTML generated. In the early days of XWiki, the were few places were we have HTML generated. Most of the html produce came from three major places: 1) .vm templates including macros.vm 2) java generated (#display()) 3) XWiki tech document While 2) and 3) either provide very basic markup or customizable one and are not so much, and 1) was fully customizable by skins, to work out a new skin was not too complex. Today however, the UI of XWiki has considerably increase its complexity, and the source of HTML has followed, added to the above 3: 4) XWiki and Java macros 5) JavaScript (ie: annotation UI, comments preview) Changing all these places has become really more painful. There is no central place, and a lot of hidden dependencies between UI components exists. Worse examples are those written in JS, that hook into the UI. I should admit that I have not a clear idea of the best way to improve that, but my feeling is that changing so much places simply to adapt our wiki skin to the "a la mode" skin solution (something that will happen again) is not nice. So this thread is now open for anyone to discuss the situation and for anyone interested to provide its input to the discussion. Looking at what I face building the UI with bootstrap, here is what I noticed: 1) Bootstrap customize standard tags, without any css class associated 2) Bootstrap provide standard css classes to skin a given kind of UI component 3) Bootstrap use these class and custom attribute to inject JS interactivity All these are really clean methods and work really well at building very simple html construct while providing nice looking and easy interface. Let's take a concrete example, to build a button, you may use either an a tag, an input tag, a button tag or whatever, and set it a 'btn' css class. You may complement it with additional 'btn-primary', 'btn-success', ... css classes, to choose the kind of button you really want. However, in our XWiki UI, there no single place where we construct buttons, we do so in some velocity macros of macros.vm, we do so in .vm of the UI, we also do so in javascript, and finally in some wiki documents, maybe we also generate some in a java component. All those buttons are usually built the same, with a very similar HTML, but there is no central place where the button markup is produced. And the same is true for most UI component. You may say we don't care, and CSS could solve them all, making any kind of markup look the way we want. But, we will loose the benefit of using existing CSS solution. And there are interesting benefit to that, since those solution gets customized, see BootsWatch for example. Therefore, it seems to me that we need something like an UI generator, so that when you build a application, you would simply says, I want a primary button here, a secondary button there, and it gets created both the way it should for your apps to use it, but also for the UI design we want to use. Defining a list of these UI component is not simple, but we may take Bootstrap as a starting point. There is in Bootstrap a large number of control already, that should cover many UI possibilities. How to provide that UI component to all the places we need it may be less obvious. For example, we need to create button from .vm, XWiki document, XWiki and java Macros, and even from javascript. Also defining how you could expect to interact with each control, from Javascript or from java on the server needs clarification. I have not yet googled, but there may be existing experience regarding these matters on other project. Not reinventing the wheel is always better. Your ideas are welcome. IMO, we really need that if we want our Skin 4.x to be really more usable for customization. WDYT ? -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

12 years, 7 months

6
10
0 0

Re: [xwiki-devs] [xwiki-notifications] xwiki-enterprise-test-extension - Build # 1503 - Unstable!

by Vincent Massol

Added as a false positive. Someone needs to look at it and understand the problem though… Seems to be some browser setup issue on that agent Thanks -Vincent On Feb 7, 2013, at 10:30 AM, Jenkins <build.noreply(a)xwiki.org> wrote: > Check console output at http://ci.xwiki.org/job/xwiki-enterprise-test-extension/1503/ to view the results. > > Failed tests: > 1 tests failed. > FAILED: org.apache.maven.surefire.junit4.JUnit4Provider.org.xwiki.test.ui.AllTests > > Error Message: > Failed to initialize PersistentTestContext > > Stack Trace: > java.lang.RuntimeException: Failed to initialize PersistentTestContext > at org.xwiki.test.ui.PageObjectSuite.beforeTests(PageObjectSuite.java:63) > at org.xwiki.test.integration.XWikiExecutorSuite.run(XWikiExecutorSuite.java:170) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: org.openqa.selenium.WebDriverException: Failed to connect to binary FirefoxBinary(/home/hudsonagent/firefox/firefox) on port 7055; process output follows: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > Build info: version: '2.28.0', revision: '18309', time: '2012-12-11 15:53:30' > System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-042stab061.2', java.version: '1.6.0_33' > Driver info: driver.version: FirefoxDriver > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:118) > at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) > at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:179) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:96) > at org.xwiki.test.ui.WebDriverFactory.createWebDriver(WebDriverFactory.java:46) > at org.xwiki.test.ui.PersistentTestContext.<init>(PersistentTestContext.java:73) > at org.xwiki.test.ui.PageObjectSuite.beforeTests(PageObjectSuite.java:60) > ... 13 more > Caused by: org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:106) > ... 22 more > Caused by: org.openqa.selenium.WebDriverException: Failed to connect to binary FirefoxBinary(/home/hudsonagent/firefox/firefox) on port 7055; process output follows: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > Build info: version: '2.28.0', revision: '18309', time: '2012-12-11 15:53:30' > System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-042stab061.2', java.version: '1.6.0_33' > Driver info: driver.version: FirefoxDriver > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:118) > at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) > at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:179) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:96) > at org.xwiki.test.ui.WebDriverFactory.createWebDriver(WebDriverFactory.java:46) > at org.xwiki.test.ui.PersistentTestContext.<init>(PersistentTestContext.java:73) > at org.xwiki.test.ui.PageObjectSuite.beforeTests(PageObjectSuite.java:60) > ... 13 more > Caused by: org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:106) > ... 22 more > > > > > Last build logs: > [...truncated 659 lines...] > 10:26:47.365 [main] INFO o.x.test.integration.XWikiExecutor - Checking that XWiki is up and running... > 10:26:47.379 [Thread-1] INFO o.x.t.i.XWikiLogOutputStream - Starting Jetty on port 8080 ... > 10:26:48.080 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:26:48.079:INFO::jetty-7.4.5.v20110725 > 10:26:48.098 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:26:48.098:INFO::Opened /home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/xwiki-enterprise-jetty-hsqldb-5.0-SNAPSHOT/data/logs/2013_02_07.request.log > 10:26:48.102 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:26:48.102:INFO::Deployment monitor /home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/xwiki-enterprise-jetty-hsqldb-5.0-SNAPSHOT/jetty/contexts at interval 1 > 10:26:48.107 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:26:48.106:INFO::Deployable added: /home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/xwiki-enterprise-jetty-hsqldb-5.0-SNAPSHOT/jetty/contexts/root.xml > 10:26:48.224 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:26:48.224:INFO::NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet > 10:26:48.277 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:26:48.277:INFO::started o.e.j.w.WebAppContext{/,file:/home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/xwiki-enterprise-jetty-hsqldb-5.0-SNAPSHOT/webapps/root/},/home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/xwiki-enterprise-jetty-hsqldb-5.0-SNAPSHOT/jetty/../webapps/root > 10:26:48.289 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:26:48.289:INFO::Deployable added: /home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/xwiki-enterprise-jetty-hsqldb-5.0-SNAPSHOT/jetty/contexts/xwiki.xml > 10:27:05.641 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:05.641:INFO::NO JSP Support for /xwiki, did not find org.apache.jasper.servlet.JspServlet > 10:27:15.823 [Thread-1] INFO o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:15,819 [main] INFO istributionInitializerListener - Distribution state: NEW > 10:27:15.828 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:15.827:INFO::started o.e.j.w.WebAppContext{/xwiki,file:/home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/xwiki-enterprise-jetty-hsqldb-5.0-SNAPSHOT/webapps/xwiki/},/home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/xwiki-enterprise-jetty-hsqldb-5.0-SNAPSHOT/jetty/../webapps/xwiki > 10:27:16.158 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:16.158:INFO::Started SelectChannelConnector@0.0.0.0:8080 STARTING > 10:27:16.158 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:16.158:INFO::---------------------------------- > 10:27:16.160 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:16.160:INFO::Server started, you can now open http://agent-12:8080/ in your browser to access your wiki. > 10:27:16.161 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:16.160:INFO::---------------------------------- > 10:27:25.798 [Thread-1] INFO o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:25,797 [http://localhost:8080/xwiki/rest/repository/extensions/org.xwiki.platform%3…] INFO .HibernateDataMigrationManager - Storage schema updates and data migrations are enabled > 10:27:25.798 [Thread-1] INFO o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:25,798 [http://localhost:8080/xwiki/rest/repository/extensions/org.xwiki.platform%3…] INFO .HibernateDataMigrationManager - No data migration to apply for database [xwiki] currently in version [43000] > 10:27:25.798 [Thread-1] INFO o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:25,798 [http://localhost:8080/xwiki/rest/repository/extensions/org.xwiki.platform%3…] INFO .HibernateDataMigrationManager - Checking Hibernate mapping and updating schema if needed for database [xwiki] > 10:27:35.698 [main] INFO o.x.test.integration.XWikiExecutor - Server is answering to [http://localhost:8080/xwiki/bin/view/Main?xpage=plain]... cool > 10:27:35.861 [Thread-2] ERROR o.x.t.i.XWikiLogOutputStream - 2013-02-07 10:27:35.861:INFO:/xwiki:RestletServlet: [Restlet] Attaching application: org.xwiki.rest.internal.XWikiRestletJaxRsApplication@2862c542 to URI: /xwiki/rest > org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:106) > at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) > at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:179) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:96) > at org.xwiki.test.ui.WebDriverFactory.createWebDriver(WebDriverFactory.java:46) > at org.xwiki.test.ui.PersistentTestContext.<init>(PersistentTestContext.java:73) > at org.xwiki.test.ui.PageObjectSuite.beforeTests(PageObjectSuite.java:60) > at org.xwiki.test.integration.XWikiExecutorSuite.run(XWikiExecutorSuite.java:170) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 184.657 sec <<< FAILURE! > org.xwiki.test.ui.AllTests Time elapsed: 184657 sec <<< ERROR! > java.lang.RuntimeException: Failed to initialize PersistentTestContext > at org.xwiki.test.ui.PageObjectSuite.beforeTests(PageObjectSuite.java:63) > at org.xwiki.test.integration.XWikiExecutorSuite.run(XWikiExecutorSuite.java:170) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: org.openqa.selenium.WebDriverException: Failed to connect to binary FirefoxBinary(/home/hudsonagent/firefox/firefox) on port 7055; process output follows: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > Build info: version: '2.28.0', revision: '18309', time: '2012-12-11 15:53:30' > System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-042stab061.2', java.version: '1.6.0_33' > Driver info: driver.version: FirefoxDriver > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:118) > at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) > at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:179) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:96) > at org.xwiki.test.ui.WebDriverFactory.createWebDriver(WebDriverFactory.java:46) > at org.xwiki.test.ui.PersistentTestContext.<init>(PersistentTestContext.java:73) > at org.xwiki.test.ui.PageObjectSuite.beforeTests(PageObjectSuite.java:60) > ... 13 more > Caused by: org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:106) > ... 22 more > Caused by: org.openqa.selenium.WebDriverException: Failed to connect to binary FirefoxBinary(/home/hudsonagent/firefox/firefox) on port 7055; process output follows: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > Build info: version: '2.28.0', revision: '18309', time: '2012-12-11 15:53:30' > System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.32-042stab061.2', java.version: '1.6.0_33' > Driver info: driver.version: FirefoxDriver > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:118) > at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:244) > at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:188) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:183) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:179) > at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:96) > at org.xwiki.test.ui.WebDriverFactory.createWebDriver(WebDriverFactory.java:46) > at org.xwiki.test.ui.PersistentTestContext.<init>(PersistentTestContext.java:73) > at org.xwiki.test.ui.PageObjectSuite.beforeTests(PageObjectSuite.java:60) > ... 13 more > Caused by: org.openqa.selenium.firefox.NotConnectedException: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output: > *** LOG addons.manager: Application has been upgraded > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi-utils: Opening database > *** LOG addons.xpi-utils: Creating database schema > *** LOG addons.xpi: New add-on fxdriver(a)googlecode.com installed in app-profile > *** Blocklist::_loadBlocklistFromFile: blocklist is disabled > *** LOG addons.xpi: New add-on {972ce4c6-7e08-4474-a285-3208198ce6fd} installed in app-global > *** LOG addons.xpi: Updating database with changes to installed add-ons > *** LOG addons.xpi-utils: Updating add-on states > *** LOG addons.xpi-utils: Writing add-ons list > *** LOG addons.manager: shutdown > *** LOG addons.xpi: shutdown > *** LOG addons.xpi-utils: shutdown > *** LOG addons.xpi-utils: Database closed > *** LOG addons.xpi: startup > *** LOG addons.xpi: Ignoring file entry whose name is not a valid add-on ID: /tmp/anonymous964742403872399312webdriver-profile/extensions/webdriver-staging > *** LOG addons.xpi: checkForChanges > *** LOG addons.xpi: No changes found > at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:106) > ... 22 more > > > Results : > > Tests in error: > org.xwiki.test.ui.AllTests: Failed to initialize PersistentTestContext > > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > > [ERROR] There are test failures. > mojoSucceeded org.apache.maven.plugins:maven-surefire-plugin:2.12.3(default) > > Please refer to /home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/target/surefire-reports for the individual test results. > [JENKINS] Recording test results > mojoStarted org.apache.maven.plugins:maven-install-plugin:2.4(default-install) > [INFO] > [INFO] --- maven-install-plugin:2.4:install (default-install) @ xwiki-enterprise-test-extension --- > [INFO] Installing /home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/pom.xml to /home/hudsonagent/.m2/repository/org/xwiki/enterprise/xwiki-enterprise-test-extension/5.0-SNAPSHOT/xwiki-enterprise-test-extension-5.0-SNAPSHOT.pom > mojoSucceeded org.apache.maven.plugins:maven-install-plugin:2.4(default-install) > mojoStarted org.apache.maven.plugins:maven-deploy-plugin:2.7(default-deploy) > [INFO] > [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ xwiki-enterprise-test-extension --- > Downloading: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… > Downloaded: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… (624 B at 1.4 KB/sec) > Uploading: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… > Uploaded: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… (7 KB at 17.7 KB/sec) > Downloading: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… > Downloaded: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… (581 B at 1.6 KB/sec) > Uploading: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… > Uploaded: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… (624 B at 1.8 KB/sec) > Uploading: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… > Uploaded: scp://maven.xwiki.org/home/maven/public_html/snapshots/org/xwiki/enterprise… (581 B at 1.6 KB/sec) > mojoSucceeded org.apache.maven.plugins:maven-deploy-plugin:2.7(default-deploy) > projectSucceeded org.xwiki.enterprise:xwiki-enterprise-test-extension:5.0-SNAPSHOT > sessionEnded > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 8:52.764s > [INFO] Finished at: Thu Feb 07 10:30:25 CET 2013 > [INFO] Final Memory: 52M/760M > [INFO] ------------------------------------------------------------------------ > Projects to build: [MavenProject: org.xwiki.enterprise:xwiki-enterprise-test-extension:5.0-SNAPSHOT @ /home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/pom.xml] > [JENKINS] Archiving /home/hudsonagent/hudson_root/workspace/xwiki-enterprise-test-extension/xwiki-enterprise-test/xwiki-enterprise-test-extension/pom.xml to /home/maven/.hudson/jobs/xwiki-enterprise-test-extension/modules/org.xwiki.enterprise$xwiki-enterprise-test-extension/builds/2013-02-07_10-21-28/archive/org.xwiki.enterprise/xwiki-enterprise-test-extension/5.0-SNAPSHOT/xwiki-enterprise-test-extension-5.0-SNAPSHOT.pom > [WARNING] The requested profile "legacy" could not be activated because it does not exist. > [WARNING] The requested profile "jetty" could not be activated because it does not exist. > Waiting for Jenkins to finish collecting data > channel stopped > Email was triggered for: Unstable > Sending email for trigger: Unstable > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

12 years, 7 months

1
0
0 0

[xwiki-devs] Minor improvements to the Release Plan app

by Vincent Massol

Hi devs, Just to let you know I've done 3 improvements this morning on the Release Plan app at: http://dev.xwiki.org/xwiki/bin/view/ReleasePlans/WebHome 1) Each release plan now shows the release date + an avatar of the RM For ex: http://dev.xwiki.org/xwiki/bin/view/ReleasePlans/ReleasePlan45RC1 2) The livetable now automatically links to the Release notes: http://dev.xwiki.org/xwiki/bin/view/ReleasePlans/WebHome 3) Minor UI stuff: - Added translations for the livetable columns - Improved the input field to mention that a version is expected by adding a label Future work: * Generate the release notes page automatically * Import all past releases/release plans * Add stats Thanks -Vincent

12 years, 7 months

1
1
0 0

[xwiki-devs] [ANN] XWiki 4.5 Release Candidate 1 released

by Vincent Massol

The XWiki development team is proud to announce the availability of XWiki 4.5 RC 1. 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/ReleaseNotesXWiki45RC1 Thanks -The XWiki dev team

12 years, 7 months

1
0
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