On Jan 27, 2009, at 12:30 PM, jvdrean (SVN) wrote:
> Author: jvdrean
> Date: 2009-01-27 12:30:04 +0100 (Tue, 27 Jan 2009)
> New Revision: 15759
>
> Modified:
> platform/core/trunk/xwiki-core/src/main/resources/
> ApplicationResources.properties
> platform/xwiki-applications/trunk/administration/src/main/
> resources/XWiki/AdminGeneralSheet.xml
> Log:
> XAADMINISTRATION-17 : Display date format option in the general
> section of the administration
>
> Implemented.
>
> Modified: platform/core/trunk/xwiki-core/src/main/resources/
> ApplicationResources.properties
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/resources/
> ApplicationResources.properties 2009-01-27 11:28:16 UTC (rev 15758)
> +++ platform/core/trunk/xwiki-core/src/main/resources/
> ApplicationResources.properties 2009-01-27 11:30:04 UTC (rev 15759)
> @@ -158,6 +158,7 @@
> registration=Registration
> multilingual=Multi Lingual
> default_language=Default Language
> +dateformat=<a href="http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Configuration#HDateform…
> ">Date format</a>
hmm... do we want this? Are we already linking from the source to
external documentation?
The risk is that it's going to be very easy to break the link when we
reorganize documentation and that it requires internet connection.
The alternative could be to have a tooltip with the format defined in
there.
WDYT?
Thanks
-Vincent
>
> authenticate_view=Prevent unregistered users from viewing pages,
> regardless of the page or space rights
> authenticate_edit=Prevent unregistered users from editing pages,
> regardless of the page or space rights
> baseskin=Base Skin
>
> Modified: platform/xwiki-applications/trunk/administration/src/main/
> resources/XWiki/AdminGeneralSheet.xml
> ===================================================================
> --- platform/xwiki-applications/trunk/administration/src/main/
> resources/XWiki/AdminGeneralSheet.xml 2009-01-27 11:28:16 UTC (rev
> 15758)
> +++ platform/xwiki-applications/trunk/administration/src/main/
> resources/XWiki/AdminGeneralSheet.xml 2009-01-27 11:30:04 UTC (rev
> 15759)
> @@ -58,7 +58,7 @@
> <content>### Administrate general wiki preferences, at global level
> #set($legend = ["language", "editor", "admin", "server"])
> #set($params = $util.hashMap)
> -#set($params.language = ["multilingual", "languages" ,
> "default_language"])
> +#set($params.language = ["multilingual", "languages" ,
> "default_language", "dateformat"])
> #set($params.editor = ["editor"])
> #set($params.admin = ["admin_email"])
> #set($params.server = ["smtp_server"])
Devs,
I've been brainstorming about implementing office importer functionality in
wysiwyg where the user will be able to upload a document and have it's
content imported into the current page being edited (i.e into the wysiwyg
editor). Note that we already have the copy/paste functionality implemented.
The first problem I see is that GWT doesn't have a way to upload a file with
a usual RPC call. Given the parameters, following is one possible way out of
this problem,
1. Define an OfficeImporterServlet which mapps to /xwiki/officeimporter
2. Let the office importer wysiwyg plugin make a POST request to this
servlet with a FileUpload widget (
http://google-web-toolkit.googlecode.com/svn/javadoc/1.5/com/google/gwt/use…
).
3. The servlet will import the document into xhtml and write back the result
as the response.
4. Office importer wysiwyg plugin in turn takes the result and put it into
the wysiwyg editor.
And the second problem arises when there are non-textual content (ex.
images) in the document submitted. In this case, office importer servlet
must attach these files into the wiki page which is being edited. Now, if
the user decides to cancel the whole edit operation just after the import
operation, there must be a way to remove those attachments. How can we do
this? (For the moment I don't know how to handle this case)
Please let me know if you have any comments :)
Thanks.
- Asiri
Hi,
In order to better organize our SVN/JIRA I propose to implement the
following refactoring:
1) Release all platform modules simultaneously. Rationale: make it
easy to release and to ensure all versions work together.
2) Remove notion of core. Keep only notion of platform. It's up the
products/projects to hand pick whatever components they need from the
platform.
3) Move in SVN platform/core/* to platform/components/ except for
platform/core/xwiki-core which is moved to platform/xwiki-core/ (while
waiting to be split into components)
4) in JIRA create a new category named "XWiki Platform Components" and
have one jira project for each top level module in platform/
components/. Move the "XWiki Core" jira project from the "XWiki Core &
Products" category to the "XWiki Platform Components" category.
5) In JIRA rename "XWiki Core & Products" to "XWiki Top Level Projects"
6) Create some tools on dev.xwiki.org to help with releases (using
swizzle jira). Namely:
- a tool to automatically add a version to a set of jira projects
(we'll need to do that to manipulate all jira projects in "XWiki
Platform Components" all together). Same to release a version
WDYT?
Note that I've tried imagining keeping all platform modules under the
same jira project but I've ruled it out since that doesn't work well
for several reasons:
* there's no notion of sub-components in jira which would mean
creating hundreds of jira components...
* we already have some modules in separate jira projects
* it may happen that we may want to occasionally release a module
separately in the future for some reason
Thanks
-Vincent
http://xwiki.comhttp://xwiki.orghttp://massol.net
Hi devs,
column sorting (as shown in table generated by "xwiki.result") does only
string sort. Is there any way to do alphanumeric sort?
for example sorting does something like this: a1, a10, a11, a2, a21,
a3,a4 ..... , a9, ......
I would like to get something like this: a1, a2, a3, a4, ... a9....
a10, a11, a21, ......
Also is there a way just to do the numeric sort?
Regards......
Groovy 1.6RC2 is out. We could upgrade.
Thanks
-Vincent
Begin forwarded message:
> From: Guillaume Laforge <glaforge(a)gmail.com>
> Date: January 22, 2009 10:25:26 PM CEST
> To: Groovy User <user(a)groovy.codehaus.org>, Grails Users <user(a)grails.codehaus.org
> >, GroovyDev <dev(a)groovy.codehaus.org>, announce(a)groovy.codehaus.org
> Subject: [ossgtp] Groovy 1.6-RC-2 is out!
> Reply-To: ossgtp(a)yahoogroups.com
>
> Hi all,
>
> The Groovy development team and SpringSource are pleased to announce
> the second candidate for Groovy 1.6.
> This release is a bug fix release, and as you can see by looking at
> the JIRA issues closed -- almost a hundred, a lot of work has been
> done to ensure that our next major release is of great quality, and
> various improvements have been introduced -- check for instance the
> much nicer and thourough output of GroovyDoc!
>
> This version obviously also contain all the performance improvements
> and features of the latest betas and RC. You can read more about
> them by reading the previous announcements:
> Groovy 1.6-beta-1
> Groovy 1.6-beta-2
> Groovy 1.6-RC-1
> You can download Groovy 1.6-RC-2 at the usual place: http://groovy.codehaus.org/Download
>
> And now, we need your help to test drive this release candidate! We
> need you to find possible critical bugs or regressions, so please
> make sure you try 1.6-RC-2 with your project, to be able to upgrade
> as soon as possible to the latest and greatest Groovy.
>
> We're looking forward to your feedback.
>
> Thank you all for your hard work and your contributions.
>
>
> --
> Guillaume Laforge
> Groovy Project Manager
> Head of Groovy Development at SpringSource
> http://www.springsource.com/g2one
Hi folks,
Regarding the XWIKI-2968 <http://jira.xwiki.org/jira/browse/XWIKI-2968>
issue, this is what i've been suggested:
You should put warning, error and info macro in the same project based on the same AbstractMessageMacro or something like that because theses 3 macro have almost exactly the same code. You could even have only one java macro implementation and use the macro name to find the class name.
Personally, I'm +1 for the second approach, creating a single java class for all the three macros, and dynamically check for the macro name and deciding what exactly macro type is to be rendered at runtime. Reason: It's simple, it's light, it's an easy to track approach.
If you have a different opinion, please let me know.
Tnx, Dan
Hi
I am trying to build enterprise and get the following error. (I
downloaded using svn client from HEAD). Please help me.
C:\xwiki\source\enterprise\trunk>set MAVEN_OPTS=-Xmx600m
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] XWiki Products - Enterprise - Parent POM
[INFO] XWiki Products - Enterprise - Wiki
[INFO] XWiki Products - Enterprise - Database - Parent POM
[INFO] XWiki Products - Enterprise - Database - HSQLDB
[INFO] XWiki Products - Enterprise - Web
[INFO] XWiki Products - Enterprise - Distribution - Parent POM
[INFO] XWiki Products - Enterprise - Distribution - Jetty
[INFO] XWiki Products - Enterprise - Distribution - Jetty - HSQLDB
[INFO]
------------------------------------------------------------------------
[INFO] Building XWiki Products - Enterprise - Parent POM
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus
..velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: xwiki-license-resources}]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing C:\xwiki\source\enterprise\trunk\pom.xml to
C:\Documents and S
ettings\v105953\.m2\repository\com\xpn\xwiki\products\xwiki-enterprise-p
arent\1.
8-SNAPSHOT\xwiki-enterprise-parent-1.8-SNAPSHOT.pom
[INFO]
------------------------------------------------------------------------
[INFO] Building XWiki Products - Enterprise - Wiki
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
Downloading:
http://maven.xwiki.org/externals/opensymphony/quartz/1.6.0/quartz-1
..6.0.pom
Downloading:
http://maven.xwiki.org/releases/opensymphony/quartz/1.6.0/quartz-1.
6.0.pom
Downloading:
http://repo1.maven.org/maven2/opensymphony/quartz/1.6.0/quartz-1.6.
0.pom
[INFO] [remote-resources:process {execution: xwiki-license-resources}]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[WARNING] Attempting to build MavenProject instance for Artifact
(com.xpn.xwiki.
platform.tools:xwiki-xar-plugin:1.13-20090121.104832-4) of type:
maven-plugin; c
onstructing POM artifact instead.
-----------------------------------------------------
this realm =
app0.child-container[com.xpn.xwiki.platform.tools:xwiki-xar-plugin]
urls[0] = file:/C:/Documents and
Settings/v105953/.m2/repository/com/xpn/xwiki/p
latform/tools/xwiki-xar-plugin/1.13-SNAPSHOT/xwiki-xar-plugin-1.13-SNAPS
HOT.jar
urls[1] = file:/C:/Documents and
Settings/v105953/.m2/repository/org/codehaus/pl
exus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
urls[2] = file:/C:/Documents and
Settings/v105953/.m2/repository/org/codehaus/pl
exus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
urls[3] = file:/C:/Documents and
Settings/v105953/.m2/repository/org/codehaus/pl
exus/plexus-io/1.0-alpha-2/plexus-io-1.0-alpha-2.jar
urls[4] = file:/C:/Documents and
Settings/v105953/.m2/repository/dom4j/dom4j/1.6
..1/dom4j-1.6.1.jar
urls[5] = file:/C:/Documents and
Settings/v105953/.m2/repository/xml-apis/xml-ap
is/1.0.b2/xml-apis-1.0.b2.jar
Number of imports: 6
import: org.codehaus.classworlds.Entry@4891bb28
import: org.codehaus.classworlds.Entry@f8e44ca4
import: org.codehaus.classworlds.Entry@c51bc9e7
import: org.codehaus.classworlds.Entry@bece5185
import: org.codehaus.classworlds.Entry@3fee8e37
import: org.codehaus.classworlds.Entry@3fee19d8
this realm = plexus.core
urls[0] = file:/C:/apache-maven-2.0.9/lib/maven-2.0.9-uber.jar
urls[1] = file:/C:/Documents and
Settings/v105953/.m2/repository/org/codehaus/pl
exus/plexus-utils/1.1/plexus-utils-1.1.jar
urls[2] = file:/C:/Documents and
Settings/v105953/.m2/repository/com/xpn/xwiki/p
latform/tools/xwiki-xar-handlers/1.9-SNAPSHOT/xwiki-xar-handlers-1.9-SNA
PSHOT.ja
r
Number of imports: 6
import: org.codehaus.classworlds.Entry@4891bb28
import: org.codehaus.classworlds.Entry@f8e44ca4
import: org.codehaus.classworlds.Entry@c51bc9e7
import: org.codehaus.classworlds.Entry@bece5185
import: org.codehaus.classworlds.Entry@3fee8e37
import: org.codehaus.classworlds.Entry@3fee19d8
-----------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal
'com.xpn.xwiki.platfo
rm.tools:xwiki-xar-plugin:1.13-SNAPSHOT:xar': Unable to find the mojo
'com.xpn.x
wiki.platform.tools:xwiki-xar-plugin:1.13-SNAPSHOT:xar' in the plugin
'com.xpn.x
wiki.platform.tools:xwiki-xar-plugin'
com/xpn/xwiki/tool/xar/XarMojo (Unsupported major.minor version 49.0)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 20 seconds
[INFO] Finished at: Wed Jan 21 15:55:58 EST 2009
[INFO] Final Memory: 17M/31M
[INFO]
------------------------------------------------------------------------
Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s). All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
Hi devs,
Under Anca's pressure (joking :)) here's a vote to upgrade our
velocity deps.
Reasons:
* There are some features listed below we want to benefit from
in the near future
* We have some lock issue with some velocity code in Velocity 1.5
on myxwiki.org and we hope (dream?) that the upgrade could fix them...
For details see http://jira.xwiki.org/jira/browse/XWIKI-3142
Note that the build works fine and the selenium tests seem ok
(although some tests are failing but some - all? - were also failing
before - this is bad btw since we can't trust our build, we need to
fix that).
Here's my +1
Thanks
-Vincent
http://xwiki.comhttp://xwiki.orghttp://massol.net
Hi,
I suggest that we remove Calendar and PhotoAlbum applications from XE
default wiki.
Rationale:
- PhotoAlbum is almost unusable with HQ photos (basically any pic
taken with a digital camera) because of XE attachment management known
bugs.
- In their current state those applications doesn't meet XEs quality
requirements: test coverage, usability, performance (PhotoAlbum).
- Those 2 applications are orphan projects (no active project
leaders), btw anyone whishing to care of them is welcome.
Here's my +1.
JV.
Hi devs,
I posted a patch on http://jira.xwiki.org/jira/browse/XWIKI-3013 which
make XWiki authenticate only once by session by default, this is
configurable in xwiki.cfg using xwiki.authentication.always=1.
Pros:
- quicker navigation because user is not re-authenticated for each
request, this can be very annoying when authentication means access
another server like LDAP and when there is a lots of users at the same
time
Cons:
- you have to start a new session (by logout/login for example) to be
able to update informations from LDAP or any other authentication
which do data update from remote authentication server.
The cons is why I prefer to make this possible to disable if needed.
Here is my +1.
Thanks,
--
Thomas Mortagne
Hi,
I'd like to move calendar and photo album pages to their own
applications: xwiki-application-calendar and
xwiki-application-photoalbum.
xwiki-application-calendar pages :
- Main.EventCalendar
- XWiki.CalendarEvent
- XWiki.CalendarSheet
xwiki-application-photoalbum pages :
- Photos.Links
- Photos.NewAlbum
- Photos.WebHome
- XWiki.PhotoAlbumClass
- XWiki.PhotoAlbumClassSheet
- XWiki.PhotoAlbumClassTemplate
Here's my +1.
JV.
Hi,
I've worked on a new Dashboard for XE, you can see it at :
http://incubator.myxwiki.org/xwiki/bin/view/Main/WebHome
Note that it may differ a bit from my local version (fixed bugs,
improved styling, new tag plugin) but almost everything is there.
This new home relies on improvements in the tag application.
I'm still waiting for some CSS improvements from Laurent but I'd like
to commit it later this week.
Here's my +1.
Thanks,
JV.
Hi,
Silk icons is a 1000 icons set design for website and webapps.
Overview:
http://www.famfamfam.com/lab/icons/silk/previews/index_abc.png
In action:
http://incubator.myxwiki.org/xwiki/bin/view/Mockups/Children
I'm pretty sure you've already seen them since they are becoming a
standard all over the web.
I think we should bundle them with XWiki [1] for 3 reasons :
1/ They're gorgeous!
2/ We're using icons coming from here and there in our applications
(RMUI, Blog, etc) and we're missing some consistency.
3/ Since XWiki is also a webapp development framework I think it would
be a good thing that it comes with a complete webapp icons set.
Here's my +1.
[1] I've mailed Silk author to discuss about licensing issues. I don't
know if bundling CCA2.5 licensed work within a LGPL package is
allowed.
JV.
Hi,
Now that Toucan has been up and running for more than 1 year what do
we do with the Albatross skin?
Several options:
1) We continue to support it and fix bugs such as http://jira.xwiki.org/jira/browse/XWIKI-679
2) We decide to mothball it, ie not support it ourselves but apply
patches from users if they come. This means keeping it in svn but not
packaging it with XE
I'm hesitating. Maybe we should poll our users list?
Thanks
-Vincent
http://xwiki.comhttp://xwiki.orghttp://massol.net
Hi,
I'd like to move Tags related pages to their own app: xwiki-application-tag.
I'd also like to commit a small plugin that allows to manipulate tags easily.
It also avoid the need of programming rights on pages Tags and TagsRss.
The application and the plugin would have the same release cycle and would
be included in xwiki enterprise (like skinx or watchlist plugins/apps).
This also mean that we'll have a tag application in JIRA.
Tag pages :
- Main.TagCloud
- Main.Tags
- Main.TagsRss
- XWiki.TagClass
Tag plugin API :
public List<String> getTags(boolean distinct);
public List<String> getPagesWithTag(String tag);
public boolean renameTag(String tag, String newTag);
public boolean deleteTag(String tag);
Here's my +1.
JV.
Hi devs,
There are 4 votes required, see bellow.
1/ UI. See the screenshot at
http://incubator.myxwiki.org/xwiki/bin/view/Mockups/Children
Note that this list comes along with a generic way of building
spaces/pages/attachment/comments lists (ul) in our skin files.
Here's my +1
2/ Add a getChildren() method to XWikiDocument and Document (API).
Rationale: XWiki is a wiki and the parent/child relationship should
be made more visible and easy to display in order to make it useful. I
know we should try not to put new methods in our APIs but IMHO this
should have been there from the beginning.
Proposal:
{{code}}
Document.java
public List<String> getChildren() throws XWikiException
{
return this.doc.getChildren(getXWikiContext());
}
XWikiDocument.java
public List<String> getChildren(XWikiContext context) throws XWikiException
{
String hql ="select doc.fullName from XWikiDocument doc " +
"where doc.parent='" + getFullName() + "' order by
doc.space, doc.name";
return context.getWiki().search(hql, context);
}
{{/code}}
Note: I've put doc.space and doc.name in the order by clause since
getting pages in the 'absolute' alphabetical order afterwards is easy
using util.sort while the contrary is not true.
Here's my +1
3/ Add a $blacklistedSpaces list in xwikivars.vm. Rationale: avoid
duplicates; this list is already present in some panels and pages
since it is a common need.
Proposal:
#set($blacklistedSpaces = ["Import", "Panels", "Scheduler", "Stats",
"XAppClasses", "XAppSheets", "XAppTemplates", "XWiki"])
Here's my +1
4/ Don't display the number of children in tab. Rationale: limit the
number of HQL queries made on the view action.
Here's my +1
Thanks,
JV.
Hi devs,
Currently we are unable to insert what we want in list item or table
for example.
One way to support it is to introduce "embedded document", meaning a
syntax which act like we are including another document.
See http://jira.xwiki.org/jira/browse/XWIKI-2890 for details.
Wikimodel is using (((....))) in it's own syntax.
Since we don't use this currently, I propose to use the same syntax in
XWiki 2.0 syntax.
Here is my +1.
Thanks,
--
Thomas Mortagne
Hello,
in the new Servlet Component, there is the Container which contains the
global environment.
When it receives an action request, it gets the right Action from the
ComponentManager and launch the handleRequest function.
Should the Container be injected into Action components to retrieve local
Request/Response objects or may I misunderstand the model?
regards
Pascal
Hello,
I am studying the component model and its impact on the whole architecture
and naturally I have been thinking about OSGI and the possibility to deliver
component bundles and load dynamically components into a running XWiki
server etc... I'm not an OSGI expert and speak about OSGI because this seems
to be the most supported standard around these "dynamic service bundles
management with classloader isolation blablabla" questions...
I've seen OSGI is already in your thoughts and I would like to know the
status of your studies.
The question of the OSGI runtime is not quite a problem to my mind...
The new component model is well fitted to the OSGI approach IMO...
The real question is how to mix the IOC model with the OSGI bundle...
Plexus is a pretty IOC container but has no OSGI extension (there seems to
be some works around classworlds but not clear and classworlds is not OSGI
anyway...).
Would you keep Plexus and add the required extensions so that it can be
easily used with OSGI without adding too much code each time you want to
create a new OSGI service bundle?
Would you think about using another IOC container which propose OSGI
extensions (Spring DM or other)?
Pascal
Hi everyone,
This is something some of us have discussed offline but I'd like to
propose it officially to everyone. As you may know we'd like to bring
the XWiki Workspaces (XWS) features (invitation, user directory,
private wikis, etc) into the main product, i.e. XE/XEM so that we
don't have 2 platforms to maintain and so that we have a single main
product and several add-ons (xwiki watch, etc).
So the idea here is to add the following social features to XEM and
not to XE, thus mapping the notion of XWS spaces to wikis (XE wikis):
* Invitation manager
* User Directory
* Social network (people I follow, people following me)
* My dashboard (see all my wikis, their activities, etc)
* Wiki dashboard (stats on wikis)
The idea is that XEM is for the enterprise and thus it makes sense to
have the user directory in there rather than in XE. Same for all the
other social features.
Thanks
-Vincent
http://xwiki.comhttp://xwiki.orghttp://massol.net
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.8 Milestone 1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
First milestone of the XWiki Enterprise 1.8 version.
Main changes:
* Syntax API to convert a document from one syntax to another +
first beta of the XWiki 1.0 syntax to XWiki 2.0 syntax.
* New Office Importer.
* REST API
* Make it easier to disable footer information (comments, history, etc)
* New blog
Important bug fixes:
* Errornous rendering of links to page anchors
* If a macro fail it breaks the whole rendering process
Note that general goals for XWiki Enterprise 1.8 are:
* Office Importer
* New Blog
* REST API
* Finish new rendering/syntax
* Finish new WYSIWYG
* French XE
* MediaWiki import
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise18M1
Thanks, The XWiki dev team