Hi,
Thanks to Raffaello we also have the JIRA charting plugin (http://
confluence.atlassian.com/display/JIRAEXT/JIRA+Charting+Plugin)
installed now on jira.xwiki.org.
For example go to http://jira.xwiki.org/ and check the chart. I'm
attaching it here too. This is an interesting chart showing resolved
issues vs new issue being created, for the past 90 days. As you can
see in january of this year we've crossed a threshold where there are
more issues created than we can close and this is increasing...
Meaning we need to find a way to deal with this somehow...
Also when in the navigator you there's now a Chart button that you
can use to display charts of the current filtered issues. Last you
can add several new charting portlets in your dashboards now.
Thanks
-Vincent
On Mar 9, 2007, at 6:47 PM, Vincent Massol wrote:
> Author: vmassol
> Date: 2007-03-09 18:47:21 +0100 (Fri, 09 Mar 2007)
> New Revision: 2368
>
> Modified:
> xwiki/branches/XWIKI_1_0/core/src/main/java/com/xpn/xwiki/web/
> XWikiMessageTool.java
> Log:
> XWIKI-957: refactor XWikiMessageTool to get a translation list from
> a given documentbundle
>
> * Fixed failing m3 build due to previous commit
>
> Merge from trunk (rev 2366, 2367) and also merged rev 2297 which
> wasn't forgotten to be merged earlier on
s/wasn't/was
I'm too tired...
-Vincent
On Mar 9, 2007, at 6:36 PM, Vincent Massol wrote:
> Author: vmassol
> Date: 2007-03-09 18:36:14 +0100 (Fri, 09 Mar 2007)
> New Revision: 2366
>
> Modified:
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/web/
> XWikiMessageTool.java
> Log:
> XWIKI-957: refactor XWikiMessageTool to get a translation list from
> a given documentbundle
>
> * Fixed failing m3 build due to previous commit
^^^^^^^^^^
wishful thinking :-)
-Vincent
Hi there,
As I wanted to apply to some for the lucene plugin I've tried to use
it (I don't know anything about it really). However it's not been
working for me and it doesn't return anything when doing a full text
search.
Here's what I've done:
Configuration:
xwiki.plugins.lucene.indexdir=/tmp/lucene/xwiki
xwiki.plugins.lucene.analyzer=org.apache.lucene.analysis.standard.Standa
rdAnalyzer
xwiki.plugins.lucene.indexinterval=20
Usage:
#set($results = $xwiki.lucene.getSearchResults("wordToLookUp",
"default,en,fr"))
nb found : $results.hitcount
#foreach($result in $results.results)
* [${result.web}.${result.name}] #if($result.filename)
($result.filename)#end : $result.score
#end
This works if I use the following query "name:NameOfAPage" but it
doesn't with "wordToLookUp". I have even tried a reindexation by
calling ($xwiki.lucene.rebuildIndex()) to no avail.
Can anyone help? Is the plugin working at all?
Thanks
-Vincent
It would be cool if all committers used the coding conventions have
defined and agreed upon. There are Eclipse and IDEA configuration
files for them here: http://www.xwiki.org/xwiki/bin/view/Community/
CodeStyle
Generally speaking all committers should read everything that's on
http://www.xwiki.org/xwiki/bin/view/Community/
Feedback is welcome BTW but unless someone says something this is
what we've agreed on previously and what should be used.
Thanks
-Vincent
Hi Ludovic,
On Mar 6, 2007, at 12:07 PM, Ludovic Dubost wrote:
> Author: ludovic
> Date: 2007-03-06 12:07:59 +0100 (Tue, 06 Mar 2007)
> New Revision: 2319
>
> Added:
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> AutoTagPlugin.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> AutoTagPluginAPI.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> FrenchStemmer.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> Tag.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> TagCloud.java
> xwiki/trunk/web/gwt/src/main/java/com/xpn/xwiki/gwt/api/server/
> XWikiRequestWrapper.java
> Modified:
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/api/XWiki.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/objects/classes/
> DBListClass.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/objects/classes/
> DBTreeListClass.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/feed/
> FeedPlugin.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/feed/
> FeedPluginApi.java
> xwiki/trunk/web/gwt/pom.xml
> xwiki/trunk/web/gwt/src/main/java/com/xpn/xwiki/gwt/api/client/
> XWikiService.java
> xwiki/trunk/web/gwt/src/main/java/com/xpn/xwiki/gwt/api/client/
> XWikiServiceAsync.java
> xwiki/trunk/web/gwt/src/main/java/com/xpn/xwiki/gwt/api/server/
> XWikiServiceImpl.java
> xwiki/trunk/web/standard/pom.xml
> Log:
> XWIKI-938 Exposed clearAccents API
> XWIKI-939 Allow to have DBList queries dependent on the context
> XWIKI-759 Improved Feedplugin article storage
> XWIKI-894 Improvements to the GWT API. Added getDocumentContent API
> which allows to render a document with parameters passed to it
> XWIKI-940 Text analyzing plugin
Can you explain what the "Text Analyzing Plugin" does exactly? Also
why is it named as a text analyzing plugin when it's package name is
"autotag" and there are classes like TagCloud, etc?
Bonus: It would be nice also if this plugin could be documented on
xwiki.org in the Plugin section of the Code Zone...
Thanks
-Vincent
Hi Ludovic,
Just a general comment... It's really hard to do a review of your
commits as they're really big and all mixed up.
As a consequence it's hard for any developers of XWiki to know what
has been added and thus it'll be hard to support your changes if any
question is asked.
It would be nice if next time you could commit one at a time.
Thanks
-Vincent
On Mar 6, 2007, at 12:07 PM, Ludovic Dubost wrote:
> Author: ludovic
> Date: 2007-03-06 12:07:59 +0100 (Tue, 06 Mar 2007)
> New Revision: 2319
>
> Added:
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> AutoTagPlugin.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> AutoTagPluginAPI.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> FrenchStemmer.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> Tag.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/autotag/
> TagCloud.java
> xwiki/trunk/web/gwt/src/main/java/com/xpn/xwiki/gwt/api/server/
> XWikiRequestWrapper.java
> Modified:
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/api/XWiki.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/objects/classes/
> DBListClass.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/objects/classes/
> DBTreeListClass.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/feed/
> FeedPlugin.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/plugin/feed/
> FeedPluginApi.java
> xwiki/trunk/web/gwt/pom.xml
> xwiki/trunk/web/gwt/src/main/java/com/xpn/xwiki/gwt/api/client/
> XWikiService.java
> xwiki/trunk/web/gwt/src/main/java/com/xpn/xwiki/gwt/api/client/
> XWikiServiceAsync.java
> xwiki/trunk/web/gwt/src/main/java/com/xpn/xwiki/gwt/api/server/
> XWikiServiceImpl.java
> xwiki/trunk/web/standard/pom.xml
> Log:
> XWIKI-938 Exposed clearAccents API
> XWIKI-939 Allow to have DBList queries dependent on the context
> XWIKI-759 Improved Feedplugin article storage
> XWIKI-894 Improvements to the GWT API. Added getDocumentContent API
> which allows to render a document with parameters passed to it
> XWIKI-940 Text analyzing plugin
>
[snip]
Hi,
Thanks to Raffaello we now have the SVN plugin installed on
jira.xwiki.org. Thus it's possible to link the SVN commit to JIRA
issues.
For example: http://tinyurl.com/24v766
Thanks
-Vincent
Hi, With b5, I'm getting:
08:40:44,392 ERROR main [/xwiki]:listenerStart:3767 - Exception sending context initialized event to listener instance of class com.xpn.xwiki.web.InitializationServletContextLi
stener
...
Caused by: java.lang.NullPointerException
at com.xpn.xwiki.util.XWikiVelocityUberspector.init(XWikiVelocityUberspector.java:57)
at org.apache.velocity.runtime.RuntimeInstance.initializeIntrospection(RuntimeInstance.java:289)
at org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:231)
at org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:114)
at org.apache.velocity.app.Velocity.init(Velocity.java:80)
at com.xpn.xwiki.web.InitializationServletContextListener.initializeVelocity(InitializationServletContextListener.java:88)
at com.xpn.xwiki.web.InitializationServletContextListener.contextInitialized(InitializationServletContextListener.java:44)
... 24 more
Mar 7, 2007 8:40:44 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Mar 7, 2007 8:40:44 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/xwiki] startup failed due to previous errors
Anything special I should look at?
B4 started up OK.
My environment is:
Linux 2.6.15-28-686
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
Apache Tomcat/5.5.20
-Thanks, -Tom
--
May 4, 1970: Alison Krause, Jeffrey Miller, Sandra Scheuer, William Schroeder.
Hi,
Just wanted to let you know I have started a page about Testing on
xwiki.org. It's meant to continue our official testing strategy:
http://www.xwiki.org/xwiki/bin/view/Community/Testing
There isn't much now but we'll go from there and improve it as we
firm up our testing strategy.
Please comment and suggest ideas.
Thanks
-Vincent
Hi everyone,
Here's a status on the 1.0 roadmap:
* Beta 5 was supposed to be released last monday. I'll cut the
release tomorrow. So that's one week late... Good news is that we
have preliminary working support for page rename in it (it renames
backlinks)... (but no GUI for it yet) ;-)
* We still have 52 opened issues for 1.0...
* We were supposed to release RC1 next week but in view of this I
don't think it's reasonable to do so with so many issues.
* We've implemented more features and improvements than we had
planned for 1.0 which is one reason for being late (things like
Internationalization of xwiki apps, improvements to calendar, etc).
Other reason is that we're having regressions (due to our lack of
automated functional tests) and more bug created than anticipated I
believe.
* Out of the remaining 52 opened issues I've counted 33 issues which
are either improvements/new features or documentation tasks. Thus in
practice we have "only" something like 19 real issues. That's more
manageable.
Proposal
-----------
* I think we'll need another B6 that'll run from Monday onwards and
for 2 weeks, i.e. till the 19th of March. This means that RC1 would
be released only on the 2nd of April.
* Seen the extra delay I propose to vote RC1 as final one week after
the RC1 release instead of 2, i.e. release 1.0 final on the 9th of
April (just one day after my birthday ;-)).
* We really need help from the community on the easy tasks,
especially on the documentation ones listed on http://jira.xwiki.org/
jira/browse/XWIKI-586
* Committers try to focus on fixing bugs in the outstanding list:
http://tinyurl.com/2arvjf
* There are special 2 areas of focus I think:
- WYSIWYG editor: lots of people are using it or waiting for it to
stabilize. It's been getting much better but we need to run thorough
tests on it and squash the last remaining bugs
- PDF generation. We have lots of issues for it. I think we need to
have it working at least for exporting single pages. PDF export for a
full site would also be nice to have though (there's some code that
worked in the past but I don't think it's currently working anymore)
WDYT about this proposal? Anything else to add? Any other proposal?
Thanks
-Vincent
Hi,
We're pleased to announce the availability of the 1.0 Beta 5 release.
The focus is till bug fixing but this release brings other nice
improvements:
* Added support for parametrizing document resource bundles (See
internationalizing XWiki applications)
* Upgrade to Velocity 1.5 Beta 2 and Velocity Tools 1.3 (Velocity
1.5 Beta 2 release notes)
* Security: prevents instantiating random classes in Velocity
* Improved user profile sheet
* Add Calendar interface to edit and delete events
* Charting plugin is functional again
* Made Calendar and User profiles use Microformats (hCard and
hCalendar)
* Allow putting Velocity code in CSS and Javascript skin files
* Improved Calendar plugin
* Store the panel state (expanded/collapsed) for each user
* Experimental: Backend implementation for rename (renames the
document + all backlinks). There's no GUI yet (planned for Beta 6).
To try it out, you can call the following in Velocity:
$xwiki.getDocument("Space1.MyPageToRename").renameDocument
("Space2.MyNewName")
See the full release notes on http://www.xwiki.org/xwiki/bin/view/
Main/ReleaseNotesXWiki10Beta5
Enjoy
-The XWiki development team
Dear XWiki developers,
I'm configuring XWiki 1.0b4 to run on top of JOnAS 4.8.4 to use it for the
future website of the OW2 Consortium.
When I start XWiki (on JOnAS), a file xwiki.log is created in the current
directory.
First at all, I was suspecting a configuration problem in the webapp. So I've
discovered that the log xwiki.log is configured in the file log4j.properties
included within xwiki.jar. This is not really handy to configure XWiki log
directory.
I think it should be better if that file would be directly in WEB-INF/ at the
same level of xwiki.log. Unless if there is a way to configure the log
directory in xwiki.cfg, isn't there ?
Cheers
--
Xavier MOGHRABI - OW2 Consortium
Jabber: moghrabi(a)objectweb.org
Tel: +33 4 76 61 52 35
Hi committers,
I'd like to propose Christian as a committer on the newly created
XWIKI_WYSIWYG_NEWARCHI branch. This is a branch for working on a new
architecture for our WYSIWYG editor (based on Tiny MCE plugins rather
than the way we're currently doing it - which is non-canonical). I've
just created that branch to let Nam, Christian and others interested
(for example Mathieu Emptoz seems interested too) to work together on
this.
Christian, you must understand that this does not give you the right
to commit to the main trunk (we may vote you in later on for this
though). Technically I'll have to give you full access but you should
only commit on that branch :)
Here's my +1 to give write access to Christian to the branch.
Thanks
-Vincent
Hello again,
I have developed a method that allows creating a personal rss feed for
the wiki. The user can chose to follow (and un-follow) a page by
clicking on a link in the page. Users can follow the pages they want.
Answers me if you're interested in seeing my method in order to
ameliorate it.
@+
---------------------------------------------------
Mathieu Emptoz
CEA Cadarache
DRFC/STEP
XWiki's EFDA Remote Participation Administrator
---------------------------------------------------
Hi,
For those using a custom XWiki configuration with a custom web.xml,
we have changed yesterday the way to configure xwiki. Namely we have
changed the way XWiki is initialized.
So if you're using a custom web.xml and you wish to upgrade to the
trunk version (or to 1.0 beta 5 when it's out) you'll need to read
the following:
http://www.xwiki.org/xwiki/bin/view/Main/
ReleaseNotesXWiki10Beta5#HMigrationnotesfromallpreviousversions
Thanks
-Vincent
Hi all.
At the moment I am looking into problems exists with xwikis wysiwyg
editor. For instance, it is not possible to save the result of image
operations in the wiki page.
I have created an jira - http://jira.xwiki.org/jira/browse/XWIKI-906 -
to update tiny_mce to most recent version. But know I need more
informations, where, how, ... tiny_mce is integrated in xwiki. Where
can i find the setup of tiny_mce...
I hope somebody can help me,
Christian
Sorry about the ContentParserException which was committed by
error... I'm leaving it as I need it for a future commit of tomorrow...
Thanks
-Vincent
On Mar 1, 2007, at 12:50 AM, Vincent Massol wrote:
> Author: vmassol
> Date: 2007-03-01 00:50:18 +0100 (Thu, 01 Mar 2007)
> New Revision: 2279
>
> Added:
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/content/
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/content/parsers/
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/content/parsers/
> ContentParserException.java
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/web/
> InitializationServletContextListener.java
> xwiki/trunk/lib/velocity-tools-1.3.jar
> Removed:
> xwiki/trunk/lib/velocity-tools-1.1.jar
> xwiki/trunk/web/standard/src/main/webapp/WEB-INF/toolbox.xml
> Modified:
> xwiki/trunk/build.xml
> xwiki/trunk/core/src/main/java/com/xpn/xwiki/render/
> XWikiVelocityRenderer.java
> xwiki/trunk/web/standard/src/main/webapp/WEB-INF/web.xml
> Log:
> XWIKI-923: Upgrade to Velocity Tools 1.3
>
> - Upgraded to newest version
> - Removed unused Velocity View Servlet and unused toolbox.xml
> config file
> - Added XWiki Initialization strategy and initialized Velocity there
Hi,
We need to start a quick discussion to propose Google Summer of Code
projects for students.
We will apply on March 5th to be part of the Google Summer of Code and
we need a few things by then:
1/ A list of project proposals (with some cool and fun projects)
2/ A list of volunteer mentors (a mentor will have to follow at least
one student during the summer)
Any ideas welcome on this.
Ludovic
--
Ludovic Dubost
Blog: http://www.ludovic.org/blog/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
AIM: nvludo Yahoo: ludovic
Hi everyone,
I think it would be better for the XWiki project to use a org.xwiki
package. There are several reasons for this:
- fits better as XWiki is under OSS/LGPL
- the company name can change, it's less likely the product name will
change
- I believe if we want to make that change we should do it before the
1.0 release, as it's quite an important change and would break some
advanced usages of XWiki (like plugin creators, extension creators in
general). I think users should be safe though for the vast majority,
unless they're doing funky stuff in their pages.
Here's my +1
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Hello everybody,
Is there a way to get a cookie value with a function of the velocity
syntax? I created a cookie with the javascript "createCookie()" function
(in the file skins.js) and I would like to get it value in a velocity
script in order to insert it in a sql query. Because I need to get the
cookie value before the velocity parsing.
For example in my wiki page :
#set($sql = " where doc.fullName =
'$a_function_which_read_a_cookie_value(name_of_the_cookie)' ")
Regards, Mathieu
---------------------------------------------------
Mathieu Emptoz
CEA Cadarache
DRFC/STEP
XWiki's EFDA Remote Participation Administrator
---------------------------------------------------
Hi all,
I'm currently working on allowing xwiki to manage documents (and
their urls) in utf-8 or other non latin1 encodings.
I saw that the method:
public static String getURLEncoded(String content)
{
try {
return URLEncoder.encode(content, "UTF-8");
} catch (UnsupportedEncodingException e) {
return content;
}
}
in XWiki class is hardcoded in UTF-8, which is strange as the default
encoding of xwiki is iso-latin-1.
The method is used in the core source:
1. To prepare "Content-disposition" headers for the responses (for
package export and file download)
--> it encodes the filename for file downloads.
2. To generate ids of TOC in TOCGenerator
It is also used through velocity macros (mainly editrights, to allow
passing of a full URL, with GET attributes as a simple attribute
value usually for xredirect).
Hence it is a problem as soon as a document can have an url involving
non ascii characters.
Currently, everything works because the encoded URL do not include
non ascii chars as it is used in few places, but this method will
pose problem even in a default wiki (i.e. latin1) settings. Moreover,
this method is static and it is not possible to fetch the current
xwiki encoding.
So I propose to:
1. make this method non static and use the xwiki configuration to
specify the encoding to be used...
2. propose a way to encode filenames of content disposition which is
compatible with RFC 2231 which allows the specification of filenames,
even if they do contains non ascii chars (names in japanese of thai
for instance...)
Does anyone object against this proposal ?
Regards, Gilles,
--
Gilles Sérasset
GETA-CLIPS-IMAG (UJF, INPG & CNRS)
BP 53 - F-38041 Grenoble Cedex 9
Phone: +33 4 76 51 43 80
Fax: +33 4 76 44 66 75
Hi there,
Sometime we forget to add a jira issue # to an issue or we make a
mistake. Here's below a solution for editing an already committed
message.
Thanks
-Vincent
Begin forwarded message:
> From: Brett Porter <brett(a)apache.org>
> Date: February 20, 2007 12:19:20 PM CEST
> To: continuum-dev(a)maven.apache.org
> Subject: Re: svn commit: r509415 [1/3] - in /maven/continuum/
> trunk: continuum-security/src/main/java/org/apache/maven/continuum/
> security/p rofile/ continuum-webapp/src/main/java/org/apache/maven/
> continuum/web/action/ continuum-webapp/src/main/java/org/apache/m
> Reply-To: continuum-dev(a)maven.apache.org
>
> Can you do....
>
> svn propedit svn:log -r509415 --revprop
>
> And add that to the front?
>
> - Brett
>
> On 20/02/2007, at 8:38 PM, oching(a)exodus.exist.com wrote:
>
>> Hi Wendy,
>>
>> This is for CONTINUUM-1147
>>
>> Thanks,
>> Deng
>>
>>> On 2/19/07, oching(a)apache.org <oching(a)apache.org> wrote:
>>>> Author: oching
>>>> Date: Mon Feb 19 18:41:37 2007
>>>> New Revision: 509415
>>>>
>>>> URL: http://svn.apache.org/viewvc?view=rev&rev=509415
>>>> Log:
>>>> Added isAuthorized* methods in ContinuumActionSupport for checking
>>>> authorization in action classes with different permissions.
>>>> Implemented
>>>> SecureAction in some of the action classes that has a specific
>>>> permission. Also added 'modify-project-notifier' operation in
>>>> ProjectDeveloperDynamicRoleProfile.
>>>
>>> Is there a JIRA issue for this?
>>>
>>> --
>>> Wendy
>>>
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com