Hi team,
I wrore a report about the different localization strategies we could
have for XWiki comparing:
- a simple tool Jean-Vincent wrote
- an L10N app I started to build
- using launchpad.nethttp://dev.xwiki.org/xwiki/bin/view/Drafts/Selecting+a+tool+for+managing+Lo…
Please review and add requirements if you see requirements that have not been listed. I think we need to look at the applications and evaluate them in more details, especially to see of launchpad.net could work for us.
Let's discuss.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
We currently have a comments plug-in that is written for a custom
core. This plug-in enables us to have hierarchical comments and several
storage implementations.
The issue I encounter when rewriting it to a plexus component is that I
cannot make it independent from the core. I need both read and write
access to the storage, and I could not find a bridge to it. All I can do
is retrieve data, with org.xwiki.bridge.DocumentAccessBridge and
org.xwiki.bridge.DocumentModelBridge, but not write data.
Does anybody know how can I write a component that needs read/write
access to the storage without using XWiki,XWikiDocument and XWikiContext
classes?
Thanks,
Florin Ciubotaru
Hi Sergiu,
On Nov 6, 2008, at 7:22 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2008-11-06 07:22:48 +0100 (Thu, 06 Nov 2008)
> New Revision: 13997
>
> Modified:
> platform/pom/trunk/pom.xml
> Log:
> [misc]
> Lock down another maven plugin version
> Declare a default version for the shared test dependency
>
>
> Modified: platform/pom/trunk/pom.xml
> ===================================================================
> --- platform/pom/trunk/pom.xml 2008-11-06 06:08:51 UTC (rev 13996)
> +++ platform/pom/trunk/pom.xml 2008-11-06 06:22:48 UTC (rev 13997)
> @@ -171,6 +171,7 @@
> <dependency>
> <groupId>com.xpn.xwiki.platform.tools</groupId>
> <artifactId>xwiki-verification-resources</artifactId>
> + <version>${platform.tool.verification.version}</
> version>
I don't think this is right. There should be no version specified IMO
since this parent POM can be used by any module and some modules will
want to use a different version.
WDYT?
Thanks
-Vincent
> </dependency>
> </dependencies>
> <configuration>
> @@ -271,6 +272,12 @@
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> + <artifactId>maven-plugin-plugin</artifactId>
> + <!-- Lock down plugin version for build reproducibility -->
> + <version>2.3</version>
> + </plugin>
> + <plugin>
> + <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-site-plugin</artifactId>
> <!-- Lock down plugin version for build reproducibility -->
> <version>2.0-beta-6</version>
> @@ -396,6 +403,7 @@
> <properties>
> <!-- Only disable checkstyle in the clover profile. by default
> it's on. -->
> <xwiki.checkstyle.skip>false</xwiki.checkstyle.skip>
> + <platform.tool.verification.version>1.12-SNAPSHOT</
> platform.tool.verification.version>
> </properties>
> <profiles>
> <profile>
Hi,
we wish to use xwiki in a large project and find it difficult to see if the
component architeture suits us.
We need to hook into the login process (effectively logging users in through
our own authentication process). Can this be done using a 'plugin' or
'component' for xwiki?
Also: we need to intercept the page creation process and update our local
indexes with certain things when a user saves a page. Can this be done
throuh a plugin/component?
How would one go on about setting an eclipse project up, where a component
can be developed and debugged? Do I need to check out the entire Wiki into
the Eclipse workspace?
--
View this message in context: http://n2.nabble.com/XWiki-usable-for-this-%2B-how-to-go-on-about-component…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
I don't see documentation anywhere which identifies which versions of jar
files are being used (lucene, ecache, etc.). Is there a way to find this
out? Also a way to know which versions are being used in a pending release?
Thanks,
Paul Bernard
Hi,
Right now the XHTML macro parses wiki syntax by default.
For example the following generates a bold:
{{xhtml}}
<p>**bold**</p>
{{/xhtml}}
I propose to change that so that wiki syntax is not parsed by default
so that users will need to use the following to parse wiki syntax:
{{xhtml wiki=true}}
<p>**bold**</p>
{{/xhtml}}
Note that I'm proposing to change the current "escapeWikiSyntax" to
"wiki" (another proposal is to use "allowWikiSyntax").
WDYT?
Thanks
-Vincent
Hi devs,
Since the general discussion about distributions (see
http://markmail.org/message/nqyvd34knm5eqkru) will need some time and
I need to commit the glasshfish distribution build as soon as
possible, I propose:
- add a folder "glassfish"
- add a "derby" subfolder containing the glassfish-derby distribution build
- move all jetty related distributions in "jetty" folder et same lever
than "glassfish" and change all artifact ids as
xwiki-enterprise-jetty-* (xwiki-enterprise-jetty-hsqldb,
xwiki-enterprise-jetty-derby, etc.)
- use -Pglassfish to build glassfish and -Pjetty to build jetty (jetty
being the default one to not change anything to current build except
for the artifacts ids)
here is my +1
WDYT ?
--
Thomas Mortagne
asiri (SVN) wrote:
> Author: asiri
> Date: 2008-11-04 11:31:26 +0100 (Tue, 04 Nov 2008)
> New Revision: 13949
> + private void filter(Node node)
> + {
> + if (node.hasAttributes()) {
> + try {
> + node.getAttributes().removeNamedItem("style");
> + } catch (DOMException ex) {
> + // Not a problem.
> + }
> + }
I don't like this... try-catch code is costly, since creating an
exception takes a lot of time and memory. Can't you check if the 'style'
attribute exists instead?
And a catch block in general should indicate an exceptional execution,
not a normal, expected case.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/