The XWiki development team is pleased to announce the release of XWiki
Workspaces 1.1 final.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This release spanned about 5 months (beginning of May to end of september), with a 2 months pause this summer. During that period we implemented 47 issues, fixing 24 bugs and adding new features such
as:
* Global groups management
* Email invitation manangement
* A Workstream application
* A Revamped global administration
* A new mode of publication : Open
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesWorkspaces11
Regards
-The XWiki dev team
Hello XWikiers,
I did not find a nice way to package our reviews-application.
It should yield a xar and I would have expected the xar could be built
with all items.
Unfortunately, I have only found a way to package the xml files in the
xar and I would like to put groovy and .vm sources there... thus far
I am copy and pasting.
mvn -g did not help me.
thank for hints.
paul
Hi devs,
while developing my XWiki watch component, I've written a quick start tutorial
on XWiki components, which I would like to add in the dedicated section on
platform.xwiki.org.
It is currently in draft version at
http://dev.xwiki.org/xwiki/bin/view/Drafts/CreatingComponents . Please give it a
critical look and signal any errors that might have slipped or send improvement
suggestions.
Here's my +1 for taking it out of draft version, WDYT?
Happy coding,
Anca Luca
Hi Devs,
In the current xwiki-webdav implementation we have introduced a feature
where all the pages under a certain space is grouped according to the
starting characters of those pages. For an example, consider the following
setup :
space : Farm
pages under Farm : Dog, Cat, Donkey, Carrot, Mouse
Then the user will see the following directory structure on webdav,
xwiki/webdav/spaces/Farm/
|
|-D (Dog & Donkey goes here)
|
|-C (Cat & Carrot goes here)
|
|-M (Mouse ends up here)
Note : How many starting characters used to make groupings depends on the
number of documents inside the space.
Now, from xwiki-ui to access various documents via webdav, we have to allow
direct access to pages as well. That is, following url pattern should work
fine :
xwiki/webdav/spaces/<space_name>/<page_name> (makes sense right ?)
Now the problem with the current implementation is that in a url like
xwiki/webdav/spaces/FOO/BAR we don't know whether BAR is a grouping or if it
is a page (direct access). So I propose the following :
* All the grouped directories should start with a "_" and end with a "_"
(may be only one of them, but i like symmetric)
By this way we can easily differentiate direct page requests from indirect
access.
Ex :
Indirect : /xwiki/webdav/spaces/Foo/_D_/D
Direct : /xwiki/webdav/spaces/Foo/D
Note : Here the page name is 'D'.
WDYT ?
Thanks.
- Asiri
Hi Devs, Ludovic,
I'm faced with the following problem,
Currently xwiki-webdav is deployed under /xwiki/webdav/*. And for this to
work, we need PROPFIND method to work correctly on following locations { "/"
, "/xwiki/" , "/xwiki/webdav/*". } For "/" i have written a separate
xwiki-rootwebapp and it works fine. For "/xwiki/" and "/xwiki/webdav/*" I
had defined the following servlet mapping elemnts :
<servlet-mapping>
<servlet-name>xwiki-webdav</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>xwiki-webdav</servlet-name>
<url-pattern>/webdav/*</url-pattern>
</servlet-mapping>
Everything was working fine but lately i discovered that none of the static
content is being served correctly. This is because of the first mapping on
"/", this seems to overrride the default servet of the container (which
serves static files). Without the first mapping some webdav clients fail
because they think the url is not a webdav one.
I'm really stuck here and can't think of a solution, if you have any ideas
please let me know.
Thanks a lot.
- Asiri
Hello Xwiki-Devs,
for the fun of it I let FindBugs check the Xwiki Core code and it found
a bunch of "Issues". Some of them are more severe than others.
Maybe it is interesting to check it out. In my own programs I found some
really interesting errors/problems I was never aware of. (Including some
thread safety related stuff)
The good thing with Findbugs is the extensive documentation, that gives
you a very good explanation why the found issue is an issue. There are
also some "false positives", also explained in the documentation.
http://findbugs.sourceforge.net/
Findbugs also has good Eclipse Integration and a Maven plugin.
Definitely worth a try. A first peek is painlessly done via Java webstart.
It's just a pointer..
Greetings
Jonas
Hi Wang,
Long time no hear, you must be busy :)
Could you let us know what's the status WRT to cleaning up the office-
generated HTML?
The roadmap I'd like to have is to have it fully working for 1.7 final
(that's for the 1st of December). Do you think that's feasible?
My take is that we should have some pretty solid cleaning up by 1.7M1
if we want to have a chance of it being finished for 1.7 final.
Here's the currently planned 1.7 dates:
- 1.7M1: 20th of October (that's more than 3 weeks after the 1.6
release)
- 1.7M2: 10th of November (3 weeks after 1.7M1)
- 1.7RC1: 17 Nov (one week after)
- 1.7RC2 or final: 24 Nov (one week after)
- 1.7 final (if needed): 1st of December
WDYT? Do you need any help to achieve this?
Thanks
-Vincent
Hi everyone,
Just to let you know maven.xwiki.org is undergoign maintenance right
now.
So you might want to run your builds in offline mode for the time being.
Thanks
-Vincent