Hi,
Now that we've started creating the branch for 1.3 I'd like to remove
the 1.1 branches for Core, Web, Panels and XE.
Rationale:
* Cleanliness
* Having opened branches can tempt committers to commit stuff to the
branch. Closing it clearly shows that we don't intend to work on it
anymore
* We still have the latest released 1.1.x versions, so if there's an
urgent need to release a 1.1.3 version we can still do it.
* This will allow us to remove the 1.1.3 version in JIRA thus keeping
it clean too and again preventing people from using it.
* We can't work/support too many branches at once, that's just too
much work
* We want people to upgrade to newer versions.
* XE 1.2 was released quite some time ago and is stable. 1.3 is about
to be released as final too.
Here's my +1
Thanks
-Vincent
Hi,
Here are the modules I'd like to release in preparation for the 1.3RC1
release:
* Top level POM: new config for license files + default goal + new
surefire plugin version
* Tools POM: addition of new license module
* License module, v1.0
* Packager, v1.9: updated core dep to 1.3 + license + fixed
integration tests
* Config resources 1.10: LDAP config improvements from Thomas
* XAR plugin 1.9: ignore META-INF files in XARs
* Jetty resources 1.9: move jetty files into a jetty/ directory proper
Here's my +1 to both
Thanks
-Vincent
Since I'm getting such a great response from the community to help us
win the vote (the community rulez !), I'm going to ask for some more help.
We are looking for some Interns (Paris or even remotely) and/or
employees for our Iasi Office in Romania.
More info about the profiles we are looking for at
http://www.xwiki.com/xwiki/bin/view/About/Jobs
We are especially looking for Web Developers working on top of the XWiki
platform (scripting, web technologies, javascript, AJAX, CSS) to work on
XWiki applications and on client projects.
http://www.xwiki.com/xwiki/bin/view/About/JobsWebDeveloper
We are looking obviously for people that believe in Open Source and it's
values. We see the XWiki company (currently XPertNet, soon XWiki SAS) as
a bridge between the business world and the open source world. We want
XWiki to be both available for free but also easily available for
companies wanting support and services (maybe that would require a much
longer email to the community).
In any case if any of you are interested or if you know people that
might, don't hesitate to forward this around and make it known that
there is an great open source company looking for more help to make
great software and provide great solutions.
Thanks for you help
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi XWiki users and developers !
I've had the chance to participate to a contest on a french radio
(specialized in Business).
There is a vote which will allow to get another few minutes of radio
show in a while en eventually (with more votes to show the power of the
communities that could lead to the final, etc..).
You can listen to the podcast (in french):
http://www.bfmradio.fr/index.php?id=149&idemission=80
and vote here (in french too but that should not be too difficult ! Make
sure you select the guy on the right !):
http://www.bfmradio.fr/bfm_academie/emission2008.php?emission=2
This can give a nice additional boost to XWiki !
Thanks to all of you for you continuous support of XWiki and
participation to the lists.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Marius and developers,
I've commited a working gwt 1.4 based wysiwyg editor module.
You need to take
https://svn.xwiki.org/svnroot/xwiki/xwiki-platform/web/branches/xwiki-web-g…
and
https://svn.xwiki.org/svnroot/sandbox/wysiwyg/
You should put the wysiwyg under web/
The two files standard.pom.xml and web.pom.xml are web/standard/pom.xml
and web/pom.xml modification to build the wysiwyg module in addition.
The initial editor is available using mvn install -Pjettyrun at
http://localhost:8080/xwiki/com.xpn.xwiki.wysiwyg.Wysiwyg/Wysiwyg.html
It's a rich text editor with the full standard toolbar and two text
boxes allowing to view the wiki-> html -> wiki conversion.
It currently uses the Radeox renderer for wiki->html and the code from
Christian Gmeiner for html -> wiki
This part is not yet the important part. We shoud replace them with a
more powerfull HTML to Wiki parser. Either directly based on a new XWiki
2.0 syntax or working with new AND old syntax.
I think we need to start by getting the editor UI in place. I think the
architecture should be as much to be very independent from the syntax
itself.
The editor should as much as possible work without knowing much about
the HTML itself. This might be a bit complex for links, images or
attachments.
Maybe what we need is the FF3 (and IE6) feature that allows to make a
block non editable in the editor (content-editable = false or something
like that). We then take control of the double click on the item and
open the appropriate dialog box to edit.
We should use the same type of thing to show macros in WYSIWYG mode (we
would need a macro renderer API - macro + params).
Maybe the first thing you can start doing Marius, is get used to the
editor by implementing simple stuff that we currently have in the
editor. We need to do:
- links
-- lnternal links (last, search, recent, multiwiki, other by extension)
-- Attachements (page, space, wiki, multiwiki, webdav, other by extension)
-- Image
-- email
-- external link
- images (need to chose image with link or link with image)
- table icons
- colors and fonts
- switch to wiki syntax
- view in the xwiki styles
We also need to make eveything configurable:
- which buttons and features
- choice of output syntax
We then will need among other things
- make it properly embeddable
- import from HTML/Word/other wiki syntax
- shortcuts for links and titles without using the menus (to be as
efficient as typing [ ])
- visual macros (with many macros, using DnD)
- a macro editor
- real time editing (need to take it into account right away)
- powerfull tables (a la Excel)
I'm just talking about all these things so that we have a view on the
final objective.
More info here about the feature requirements.
http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorBasedOnGwt
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
I'm going to create a new branch in
https://svn.xwiki.org/svnroot/xwiki/xwiki-platform/web/ and a new module
in sandbox.
1/ Wysiwyg module in sandbox.
New GWT based editor. It will use the GWT Rich Editor and the XWiki GWT
Api to allow editing wiki pages. The objective is to have a:
- feature equivalent editor
- highly improved stability of the editor
- highly improved stability of the html -> wiki -> html convertor with a
server side convertor
- support for velocity and groovy
- great speed enhancements thanks to no popup and great ajax
- great architecture
- support for the future XWiki Rendering
- new cool features
The editor will need GWT 1.4 and a server side module for the syntax
conversion.
2/ Branch for GWT 1.4 Port
It will port the GWT Api to GWT 1.4, adding a js function that was
removed from GWT and getting rid of gwttk which does not have a 1.4
support.
This branch will also include the syntax convertor for the wysiwyg
module. This will be only temporarly to only have one branch for working
on the editor. Once GWT 1.4 gets into the trunk we can get rid of this
code and move it to a wysiwyg specific branch or wire it to a core
syntax conversion API once it exists.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
fyi.
We should probably do our releases through a staged process too.
This allows:
1) giving binaries to people so that they can test
2) voting on something tangible and not on sources which can be
modified before they're really released
3) ability to rollback a release if something is found faulty during
the release
-Vincent
Begin forwarded message:
> From: "Wendy Smoak" <wsmoak(a)apache.org>
> Date: February 23, 2008 4:38:42 AM CEST
> To: announce(a)maven.apache.org
> Subject: [ANN] Maven Stage Plugin 1.0-alpha-1 Released
> Reply-To: users(a)maven.apache.org
> Reply-To: wsmoak(a)apache.org
>
> The Maven team is pleased to announce the first release of the Maven
> Stage
> Plugin, version 1.0-alpha-1.
>
> http://maven.apache.org/plugins/maven-stage-plugin/
>
> This plugin assists with staging and promoting releases by allowing
> you to
> copy artifacts from one repository to another. It currently supports
> copying from http|https to scp urls.
>
> You can run 'mvn -up stage:copy ... ' to get the latest version of the
> plugin.
>
> (Nothing was closed in JIRA for this initial release, so there are no
> release notes.)
>
> Enjoy,
> --
> Wendy Smoak
> on behalf of the Maven team
>
Hi,
I was trying to compare XWiki with some of the functionality of MediaWiki.
One of my concerns about attchements is the security. For example,Do the
page access rights in XWiki, apply also to the attachements of that page?
In mediawiki, there is special page called File list where one can go and
see the entire list of files uploaded to the wiki. But, if we want to allow
access restrictions to those, this should not be allowed.
So, does XWiki take care of this issue? Not allowing restricted users from
viewing confodential attachemnts at all.
Also, what is the syntax of XWiki and how is it different from Mediawiki if
at all it is?
Thanks
vmassol (SVN) wrote:
> Author: vmassol
> Date: 2008-02-25 15:40:53 +0100 (Mon, 25 Feb 2008)
> New Revision: 7930
>
> Modified:
> xwiki-platform/xwiki-tools/trunk/xwiki-license-resources/src/main/resources/META-INF/NOTICE.vm
> Log:
> XTLICENSE-1: Add a remote resources JAR that includes XWiki License/Notice files
>
> * Fixed problem with missing EOL (not sure why but this fixes it).
>
That's how velocity works, #end at the end of the line eats the \n
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi JV,
On Feb 22, 2008, at 12:07 PM, jvdrean (SVN) wrote:
> Author: jvdrean
> Date: 2008-02-22 12:07:00 +0100 (Fri, 22 Feb 2008)
> New Revision: 7914
>
> Modified:
> xwiki-platform/xwiki-plugins/trunk/watchlist/src/main/java/com/xpn/
> xwiki/plugin/watchlist/WatchListJob.java
> xwiki-platform/xwiki-plugins/trunk/watchlist/src/main/java/com/xpn/
> xwiki/plugin/watchlist/WatchListPlugin.java
> xwiki-platform/xwiki-plugins/trunk/watchlist/src/main/java/com/xpn/
> xwiki/plugin/watchlist/WatchListPluginApi.java
> Log:
> XPWATCHLIST-12 : Global user can't watch sub-wiki's documents
>
[snip]
> + /**
> + * @return the full list of all database names of all defined
> virtual wikis. The database names
> + * are computed from the names of documents having a
> XWiki.XWikiServerClass object
> + * attached to them by removing the "XWiki.XWikiServer"
> prefix and making it lower case.
> + * For example a page named
> "XWiki.XWikiServerMyDatabase" would return "mydatabase" as
> + * the database name.
> + */
> + public List getVirtualWikisDatabaseNames(Context context, XWiki
> xwiki) throws XWikiException
> + {
> + List databaseNames = new ArrayList();
> +
> + String database = context.getDatabase();
> + try {
> + context.setDatabase(context.getMainWikiName());
> +
> + String hql =
> + ", BaseObject as obj, StringProperty as prop where
> obj.name=doc.fullName"
> + +
> + " and obj.name <>
> 'XWiki.XWikiServerClassTemplate' and
> obj.className='XWiki.XWikiServerClass' "
> + + "and prop.id.id = obj.id ";
> + List list = xwiki.searchDocuments(hql);
> +
> + for (Iterator it = list.iterator(); it.hasNext();) {
> + String docname = (String) it.next();
> + if (docname.startsWith("XWiki.XWikiServer")) {
> +
> databaseNames.add(docname.substring("XWiki.XWikiServer".length())
> + .toLowerCase());
> + }
> + }
> + } finally {
> + context.setDatabase(database);
> + }
> +
> + return databaseNames;
> + }
This method looks like a duplicate of the code in the XWiki class. Why
is that?
Thanks
-Vincent
Hi,
Has anyone already tried using Toucan 1.0 with XE 1.3M2?
Since we're going to release Toucan 1.1 today or tomorrow and XE
1.3RC1 today or tomorrow it would be great to get some feedback ASAP
if anything is not working as expected with the Toucan skin.
Thanks
-Vincent
Hi,
Just to let you know that I'm upgrading the Packager dep on XWiki Core
from 1.1.x to 1.3-SNAPSHOT. The main reason for the upgrade is to fix
this issue:
http://jira.xwiki.org/jira/browse/XWIKI-2134
For products who need to use an older version of the core, there are 2
solutions:
1) Use a version on packager up to 1.8 since starting from 1.9 it'll
depend on core 1.3
2) Branch the packager module
Thanks
-Vincent
Hi,
We need to decide if we want to have a single SVN repository or
several. Right now we have 4:
- main xwiki: XE, XEM, Watch, Curriki
- chronopolys
- xwiki workspaces
- sandbox
I prefer to have a single one for the following reasons:
1) Simpler Admin
2) Consolidate history
3) Ability to move sources from one project to another. For example
the fact the sandbox is in a separate repo is a real pain since it's
not possible to perform a svn move so we loose the history when we
move things around
4) Complex to configure. You have to configure all your tools to point
to several repos (IDE, etc)
5) Hard to configure external tools and no consolidated search,
stats,etc. For example: ohloh, sourcekibitzer
Note that Apache has a single repo for all its projects so it's not
like this is something that is weird and that hasn't been done before.
To be honest I don't see a single advantage to have several repos.
However we would need to configure the SVN hooks to send svn commit
emails to different mailing lists and do the user authentication based
on *.xwiki.org mapped to directories in SVN, but that's not a problem.
WDYT?
Thanks
-Vincent
Hi,
Some projects have wrong dates planned for their schedules:
* XWiki Workspaces: 1.0M1 planned for 4th of Feb 2008.
* Chronopolys 1.0 planned for 21st of Feb 2008.
They need to be fixed and rescheduled.
Thanks
-Vincent
Hi JV,
We need to add functional tests for the Watchlist feature. Do you
think you could make sure to add tests for it?
I think we have 2 possible approaches:
1) unit testing, which means we catch the email before it's sent and
verify that it contains the correct things.
2) functional testing. This can be done very easily using Selenium and
using a tool like Dumbster inside the Selenium test. For an example of
using Dumbster, see
http://quintanasoft.com/dumbster/#Examples
Note that Dumbster is already in the central maven repo so it should
be dead easy to use.
Another possible tool to use is James (http://james.apache.org/)
I'd recommend doing 2).
WDYT?
Thanks
-Vincent
Hi,
I'd like to bring forward the release dates for XE 1.3 final, as
follows:
* 1.3RC1 - 25/02
* 1.3Final - 3/03
I'd also like to create a branch for 1.3 since it's now in RC stage
and trunk will become 1.4-SNAPSHOT so that committers eager to work on
1.4 can start doing so and so that we're not tempted to push non bug
changes in 1.3...
The reasons:
1) We're ready to release it barring any regression we have introduced
(which will be fixed in 1.3RC1)
2) Some of us are eager to work on 1.4 (like JV who's working on
performance improvements for ex) :)
3) I'd like to drop support for 1.2 ASAP since it's hard to support
several branches at once. When 1.3 is released it means we will be
supporting 1.3 and 1.4 but no longer 1.2 (since our standard rule is
to support 2 versions - Of course anyone is free to support whatever
he wants but this is our general rule to make it easy to progress in
our devs).
4) 1.3 hasn't had any major changes since 1.2 and thus should be
pretty stable
Here's my +1 to both the new dates and the branch creation.
Thanks
-Vincent
Hi Thomas,
On Feb 21, 2008, at 3:07 PM, tmortagne (SVN) wrote:
> Author: tmortagne
> Date: 2008-02-21 15:07:45 +0100 (Thu, 21 Feb 2008)
> New Revision: 7902
>
> Modified:
> xwiki-platform/xwiki-tools/trunk/xwiki-configuration-resources/src/
> main/resources/xwiki.cfg.vm
> Log:
> Improve LDAP default configuration
>
> Modified: xwiki-platform/xwiki-tools/trunk/xwiki-configuration-
> resources/src/main/resources/xwiki.cfg.vm
> ===================================================================
> --- xwiki-platform/xwiki-tools/trunk/xwiki-configuration-resources/
> src/main/resources/xwiki.cfg.vm 2008-02-21 14:06:38 UTC (rev 7901)
> +++ xwiki-platform/xwiki-tools/trunk/xwiki-configuration-resources/
> src/main/resources/xwiki.cfg.vm 2008-02-21 14:07:45 UTC (rev 7902)
> @@ -84,15 +84,15 @@
> #-------------------------------------------------------------------------------------
>
> #-# new LDAP authentication service
> -#
> xwiki
> .authentication
> .authclass=com.xpn.xwiki.ldap.authentication.XWikiLDAPAuthServiceImpl
> +#
> xwiki
> .authentication
> .authclass=com.xpn.xwiki.user.impl.LDAP.XWikiLDAPAuthServiceImpl
>
> #-# Turn LDAP authentication on - otherwise only XWiki authentication
> #-# 0 : disable
> #-# 1 : enable
> -xwiki.authentication.ldap=0
> +# xwiki.authentication.ldap=1
Why is LDAP authentication on by default?
I would have assumed it to be off by default since the default
authentication mechanism is to use xwiki's DB. I know the new LDAP
impl will try XWiki's DB if it can't log on LDAP but that's not a good
thing to do by default since everyone will incur some overhead and the
fact that LDAP is on by default is misleading in this case.
Note: I may have missed something since I've been off for 2 days and
only unpiling my emails now ;)
Thanks
-Vincent
Hi devs,
I've seen that lots of bugs have been fixed and several improvements
introduced. For most of them the issues have been closed without tests
and this is really not good. We've decided that the 1.3 release would
be the release when we start adding tests and even though some efforts
were made for 1.3M2 this is not regressing in 1.3RC1 and it's not good.
Could those who've been doing commits recently try to spend some more
time on the tests please?
Note: A special congrats to Thomas who's done the LDAP integration
tests :)
Thanks
-Vincent
Hi all,
As XEM 1.1 is planned for current March I would like to synchronise
XEM 1.1 release on XE 1.3 final release planned for 14th of March.
WDYT ?
--
Thomas Mortagne
Pardon me if I am asking very basic questions.
But, my question is about being able to build enterprise level application
on top of XWiki.
For doing something like this, do I have to use the XWiki platform (core )
source code or XWiki Enterprise code or both?
Is there a location on XWiki website which talks about the details of this.
Thanks
Vincen,
Thanks much for the reply. It is very helpful
But, the http://tinyurl.com/3352dy does not seem to work.
Thanks
On 2/21/08, devs-request(a)xwiki.org <devs-request(a)xwiki.org> wrote:
>
> Send devs mailing list submissions to
> devs(a)xwiki.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.xwiki.org/mailman/listinfo/devs
> or, via email, send a message with subject or body 'help' to
> devs-request(a)xwiki.org
>
> You can reach the person managing the list at
> devs-owner(a)xwiki.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devs digest..."
>
>
> Today's Topics:
>
> 1. Re: [VOTE] Bring forward XE 1.3 final + create branch
> (Sergiu Dumitriu)
> 2. Re: [vote] Switch to java 5 (Ludovic Dubost)
> 3. Re: [vote] Switch to java 5 (Sergiu Dumitriu)
> 4. XWikiAttachments in SVN ? (Kamna Jain)
> 5. Re: XWikiAttachments in SVN ? (Vincent Massol)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 20 Feb 2008 14:11:46 +0100
> From: Sergiu Dumitriu <sergiu(a)xwiki.com>
> Subject: Re: [xwiki-devs] [VOTE] Bring forward XE 1.3 final + create
> branch
> To: XWiki Developers <devs(a)xwiki.org>
> Message-ID: <47BC2712.3070305(a)xwiki.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> Vincent Massol wrote:
> > Hi,
> >
> > I'd like to bring forward the release dates for XE 1.3 final, as
> > follows:
> >
> > * 1.3RC1 - 25/02
> > * 1.3Final - 3/03
> >
> > I'd also like to create a branch for 1.3 since it's now in RC stage
> > and trunk will become 1.4-SNAPSHOT so that committers eager to work on
> > 1.4 can start doing so and so that we're not tempted to push non bug
> > changes in 1.3...
> >
> > The reasons:
> > 1) We're ready to release it barring any regression we have introduced
> > (which will be fixed in 1.3RC1)
> > 2) Some of us are eager to work on 1.4 (like JV who's working on
> > performance improvements for ex) :)
> > 3) I'd like to drop support for 1.2 ASAP since it's hard to support
> > several branches at once. When 1.3 is released it means we will be
> > supporting 1.3 and 1.4 but no longer 1.2 (since our standard rule is
> > to support 2 versions - Of course anyone is free to support whatever
> > he wants but this is our general rule to make it easy to progress in
> > our devs).
> > 4) 1.3 hasn't had any major changes since 1.2 and thus should be
> > pretty stable
> >
> > Here's my +1 to both the new dates and the branch creation.
> >
> > Thanks
> > -Vincent
> >
>
> +1
>
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 20 Feb 2008 15:07:08 +0100
> From: Ludovic Dubost <ludovic(a)xwiki.org>
> Subject: Re: [xwiki-devs] [vote] Switch to java 5
> To: XWiki Developers <devs(a)xwiki.org>
> Message-ID: <47BC340C.2080507(a)xwiki.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> +1
>
> Sergiu Dumitriu wrote:
> > Hi devs,
> >
> > I think it is time to completely switch to Java 5. It adds several nice
> > features we could use.
> >
> > I think it is safe to make the switch, given that:
> >
> > - We get only few mails related to deployment on Java 1.4, and only very
> > few say that they cannot drop 1.4.
> > - Java 1.4 is in the late EOL process (should end this summer)
> > - We already have some requirements on 1.5 libraries, so XWiki doesn't
> > really work on 1.4, anyway
> >
> > Here's my +1
> >
>
>
> --
> Ludovic Dubost
> Blog: http://blog.ludovic.org/
> XWiki: http://www.xwiki.com
> Skype: ldubost GTalk: ldubost
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 20 Feb 2008 15:21:33 +0100
> From: Sergiu Dumitriu <sergiu(a)xwiki.com>
> Subject: Re: [xwiki-devs] [vote] Switch to java 5
> To: XWiki Developers <devs(a)xwiki.org>
> Message-ID: <47BC376D.7080109(a)xwiki.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> 5 +1, 3 nb +1.
>
> Now I hope Velocity knows about enums...
>
> Sergiu Dumitriu wrote:
> > Hi devs,
> >
> > I think it is time to completely switch to Java 5. It adds several nice
> > features we could use.
> >
> > I think it is safe to make the switch, given that:
> >
> > - We get only few mails related to deployment on Java 1.4, and only very
> > few say that they cannot drop 1.4.
> > - Java 1.4 is in the late EOL process (should end this summer)
> > - We already have some requirements on 1.5 libraries, so XWiki doesn't
> > really work on 1.4, anyway
> >
> > Here's my +1
>
>
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 20 Feb 2008 12:41:16 -0600
> From: "Kamna Jain" <kammy.scorpi(a)gmail.com>
> Subject: [xwiki-devs] XWikiAttachments in SVN ?
> To: devs(a)xwiki.org
> Message-ID:
> <fb681d280802201041r462f5314k9f3e56f8470d726c(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> I was wondering if this has ever been discussed before in this mailing
> list
> - Having the attched files being version controlled by SVN?
> We use SVN a lot in our company and it would be great if there exists some
> integration between XWiki and SVN to save the attached files.
>
> Thanks
>
Hi,
I was wondering if this has ever been discussed before in this mailing list
- Having the attched files being version controlled by SVN?
We use SVN a lot in our company and it would be great if there exists some
integration between XWiki and SVN to save the attached files.
Thanks
Hi devs,
I think it is time to completely switch to Java 5. It adds several nice
features we could use.
I think it is safe to make the switch, given that:
- We get only few mails related to deployment on Java 1.4, and only very
few say that they cannot drop 1.4.
- Java 1.4 is in the late EOL process (should end this summer)
- We already have some requirements on 1.5 libraries, so XWiki doesn't
really work on 1.4, anyway
Here's my +1
--
Sergiu Dumitriu
http://purl.org/net/sergiu/