If i go through the Tutorial for "Writing XWiki components",
I had problem, on using it while I'm put the code for groovy on a
XWiki-site.
It returns only "null" and nothing what "HelloWorld" means.
Can someone give me a detailed description for realizing the HelloWorld
- component
from beginning with eclipse and groovy?
Me again :)
XWiki has been allocated 1 day a week to my time, that day being Monday,
so it's probably mostly Mondays that you'll hear from me.
I'm setting up our spaces, groups & users and have discovered the
following:
"Subgroups" are really confusing and apparently have no hierarchy, and
can even be shared amongst top level groups and can refer to one another
(or self!)
When I add a subgroup, then click on it, I get told that the page does
not exist. Shouldn't it be a new group to which I can add users and
subgroups?
When adding Members to a Group, the Auto-Find is really neat - but I can
add XWiki.hhulme by clicking on the suggestion as well as hhulme. The
same is true of subgroups.
By clearing the XWikiContext in the tearDown of the unit test, I can
stop the memory leak and stop running the tests in isolation. I am
proposing we apply this change because the XWikiContext is created
per test and the worst problem which can be created is tests
erroneously passing which I don't think is very likely from a change
like this.
Jira issue: http://jira.xwiki.org/jira/browse/XWIKI-4953
Patch:
http://jira.xwiki.org/jira/secure/attachment/16788/XWIKI-4496-patchTestMemo…
Patch content:
Index: core/xwiki-core/pom.xml
===================================================================
--- core/xwiki-core/pom.xml (revision 27357)
+++ core/xwiki-core/pom.xml (working copy)
@@ -823,10 +823,6 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
- <configuration>
- <!-- Prevent Out Of Memory errors resulting from tests
that do no free up the memory correctly -->
- <forkMode>pertest</forkMode>
- </configuration>
</plugin>
<!-- Publish a Core Test JAR -->
<plugin>
Index:
core/xwiki-core/src/test/java/com/xpn/xwiki/test/AbstractBridgedXWikiComponentTestCase.java
===================================================================
---
core/xwiki-core/src/test/java/com/xpn/xwiki/test/AbstractBridgedXWikiComponentTestCase.java
(revision 27357)
+++
core/xwiki-core/src/test/java/com/xpn/xwiki/test/AbstractBridgedXWikiComponentTestCase.java
(working copy)
@@ -80,6 +80,7 @@
protected void tearDown() throws Exception
{
Utils.setComponentManager(null);
+ getContext().clear();
super.tearDown();
}
Hi devs,
The Google summer of code 2010 will start soon:
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#…
First deadline:
"March 8-29: Mentoring organizations can begin submitting applications to Google."
So we need to propose applications.
We have already listed some there:
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/
Now we need mentors for them since we should only propose projects for which we have declared mentors.
So can all the people who want to be mentors this year please edit the projects and put themselves as Project Lead (we can have several project leads for now)?
If you can fill this for Monday 8 it would be great since we need to move these projects into google's own application and it would show to google that we are active and it'll help XWiki to be chosen as a SOC organization this year.
thanks for your help
-Vincent
Hi devs,
Jerome and I have explored using Selenium2 (see http://xwiki.markmail.org/thread/cqbxdmhqdi36kovn)
The code is in http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/webdriver-ui-tests/
I'd like to propose to:
* Move the code in http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution-test/ui-te…
* Agree that from now on *new* UI functional tests are written using Selenium2
* Slowly migrate current functional tests over time (I have almost finished migrating the login/logout tests for ex)
* Use the PageObject pattern as shown in the existing tests in http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution-test/ui-te…
The pros to use selenium2 are those listed in http://xwiki.markmail.org/thread/cqbxdmhqdi36kovn:
* No more JS sandbox. In selenium1 all the selenium API is executed as JS in the browser. In Selenium2 the browsers are controlled using their native APIs (JNA).
* Faster (as a consequence of the previous point)
* Allows to do stuff such as file uploads, etc since there's no longer the issue of the JS sandbox
* No need to start a Selenium Proxy. All you need is to start XE and then you can run the tests as simple JUnit tests.
* The API is much cleaner (this is to be expected with hindsight). See http://seleniumhq.org/docs/09_webdriver.html
* There's a very fast executing HtmlUnit driver (not to be used with tests using JS though since it emulates browser JS support and thus cannot guarantee the result in the real browser)
Caveat:
* Selenium2 is still quite young so it's possible that there are cases when it'll have bugs or be instable. We should still allow using selenium1 tests when this happens.
Note: I have configured hudson to run the selenium2 tests from the sandbox to see how stable it is.
Here's my +1
Thanks
-Vincent
sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2010-03-06 02:23:19 +0100 (Sat, 06 Mar 2010)
> New Revision: 27501
>
> Modified:
> platform/web/trunk/standard/src/main/webapp/templates/informationinline.vm
> Log:
> XWIKI-4980: Backlink information is not sorted by space
> Fixed.
>
> Modified: platform/web/trunk/standard/src/main/webapp/templates/informationinline.vm
> ===================================================================
> --- platform/web/trunk/standard/src/main/webapp/templates/informationinline.vm 2010-03-06 01:20:42 UTC (rev 27500)
> +++ platform/web/trunk/standard/src/main/webapp/templates/informationinline.vm 2010-03-06 01:23:19 UTC (rev 27501)
> @@ -40,7 +40,7 @@
> </dd>
> #end
> #end
> - #set($blinks = $doc.getBacklinks())
Should getBackLinks use an "order by" clause at the database level?
I don't think any order is guaranteed at the moment in which case it would not be breaking API.
Also getChildren could be changed at the same time since documents can have children in other spaces.
> + #set($blinks = $sorttool.sort($doc.getBacklinks()))
> #if($blinks.size()>0)
> <dt>$msg.get('core.viewers.information.backlinks')</dt>
> <dd>
>
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications
>
The XWiki development team is pleased to announce the release of XWiki
Enterprise and XWiki Enterprise Manager 2.2.2.
This is a bug fix release for the 2.2 branches.
It fixes mainly two important regressions around documents object
handling and office importer on Internet Explorer 7 so if you are
using 2.2 or 2.2.1 you should really upgrade to 2.2.2.
Improvements:
* XAADMINISTRATION-115 - Left align check boxes in "Registration >
Customize XWiki Registration"
* XAADMINISTRATION-63 - In "Administration" -> "Users" closing the
"Add new user" pop-up causes the page to refresh
* XAADMINISTRATION-67 - In "Administration > User > Add new user"
indicate which fields are mandatory
* XAADMINISTRATION-103 - Make registration page support lightbox so
administrator can use it to add users in admin users sheet.
* Updated translations
Important Bugs fixed:
* XWIKI-4955 - Page with empty content leads to "This template does
not exist" message when viewed in plain mode
* XWIKI-4967 - Impossible to import office (copy/paste) with style using IE7
* XWIKI-4965 - Objects can no longer be retrieved relative to their document
* XWIKI-4931 - Links are badly saved on IE7
* XWIKI-4977 - AJAX behavior broken in IE6 for documents with
non-ASCII characters in the name
* XWIKI-4974 - Adding tags with non-ASCII characters fails in Internet Explorer
* XWIKI-4968 - Deleting a comment appears in the history as being
deleted by the person who made the comment instead of the deleter
* XWIKI-4971 - Header generated ids are wrong in 1.0 syntax
* XWIKI-4966 - Missing translation keys for application configuration.
* XWIKI-4590 - View Statistics increment too fast because of AJAX
features in bottom page tags and ratings
* XWIKI-4925 - When XWiki is initialized via a XMLRPC request, it is
in a wrong state and redirect-to-login URLs will be wrong
* XWIKI-3915 - XWiki.copyWiki does not copy hidden documents
* XWIKI-4954 - XWikiDocument#clone should use set/getParent instead of
set/getParentReference
* XWIKI-4555 - XWikiHibernateStore#countDocuments does not always
return the same number as would be the size of #searchDocuments for
the same query
* XWIKI-4969 - Missing translation value for key
"import_listoferrorsfiles" in new Import UI
* XWIKI-4978 - Previewing a comment for a document with non-ASCII
characters in the name uses a wrong URL
* XAADMINISTRATION-68 - In "Administration > User > Add new user"
notify the user when the passwords he types in don't match
* XAADMINISTRATION-21 - User not created when registration information
isn't correct when creating new user in new Administration UI
For more information see the Releases notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise222
and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM222
Thanks
-The XWiki dev team