Hi XWikiers,
In BaseClass there is possibility to add Boolean type field with
"addBooleanField". In XwikiDocument (and then in BaseCollection), we
use "getIntValue" and "setIntValue" to retrieve or set the value with
0=false and 1=true. It's very simple but I think a
"get/setBooleanValue" that do the conversion would be much more
readable and avoid developper to search how boolean values are really
stored.
Regards,
Thomas Mortagne
Hi,
The current header copyright says:
"Copyright 2006-2007, XpertNet SARL, and individual contributors as
indicated by the contributors.txt."
2 issues:
- The sentence is not english
- We don't have such a file
I propose that we change it in favor of:
"Copyright 2006-2007, XpertNet SARL, and individual contributors."
Main Reason:
- We don't specify where the contributors are listed which means we
can decide to change that location. For example a list of
contributors is on http://www.xwiki.org/xwiki/bin/view/Community/
HallOfFame#HContributors but it's far from being accurate. Tomorrow
we may use another strategy or another location and we'd rather not
change all headers. So better not specify where we define them.
Another location is SVN.
Here's my +1 to that.
I also propose that we continue listing contributors on that
HallOfFame page. Unfortunately I've been the only one adding names
there. I need help.
Thanks
-Vincent
Hi,
We need a global solution for including/excluding pages in the XE
wiki. The needs comes from the fact that we shouldn't show internal
pages to casual xwiki users and we shouldn't show pages that they
don't have the rights to view. At least the following places need to
use this feature:
* Navigation panel
* All docs Treeview
* All docs Index
* WebSearch
* WebSearchRss
* WebRss
* Orphaned pages + Panel
I propose the following implementation:
1) Add a new API $xwiki.filterDocuments(List docNamesList, String
persmissionToCheck). It would be used like this:
for each ($item in $xwiki.filterDocuments($xwiki.searchDocuments
($sql), "view"))
...
In the XE wiki:
2) Add a XWiki.PageFiltersClass class with 1 property: Includes. This
property will contain pages to exclude, using HQL like format (one
entry per line)
3) Add a XWiki.PageFiltersClassSheet to explain what this is about,
explain how to add/remove entries, etc
4) Add a XWiki.PageFilters document that contains a
XWiki.PageFiltersClass object and which has velocity code in its wiki
content to compute the HQL clause corresponding to the exclusions
specified in its object.
5) Modify the documents listed above to use XWiki.PageFilters as
follows:
#includeInContext("XWiki.PageFilters")
#if (!$pageFiltersSqlClause)
#set ($pageFiltersSqlClause = "")
#end
#set ($sql = ".... and $pageFiltersSqlClause ...")
#set ($list = $xwiki.filterDocuments($xwiki.searchDocuments($sql ,
$nb , 0), "view"))
...
WDYT?
Thanks
-Vincent
Hi,
Sometime ago, there was a discussion regarding how should the document
history be stored in a better way.
Right now, the complete history is stored as one field in the xwikidoc
table. From my PoV, this has some major disadvantages:
- loading an older version requires parsing all the history -> memory
inefficiency
- as the documents grow older, loading a document will take a lot of time ->
time inefficiency
- queries on archives cannot return just one version, but they match the
whole document (somewhere in the history, there was a version containing
"search term")
The blocking issue with storing old version in a different table was, at
that time, the fact that a document archive should contain all information
needed for completely restoring the document, like content, metadata,
objects.
I don't think that is actually an issue. We are archiving document versions,
but we're joining all versions in one large string. Why don't we archive the
complete version, but one version per row?
So, the archive table should look like:
- document name
- version number
- language (for translations)
- content
- archived metadata (one field, or the same fields as in xwikidoc)
- archived objects (one field)
- attachment names and versions
It is not like storing the version as a normal document is, with separate
objects and properties, but at least it provides a better storage and
retrieval mechanism, and it separates a bit the parts of a wikidocument -
content, metadata, objects.
WDYT?
--
http://purl.org/net/sergiu
ok, after fighting for 2 days, TeamCity is back working fine.
http://teamcity.xwiki.org
We had a disk full problem dues to the large size of our maven repos
so I cleaned them all and then discovered the build on TC wasn't
working anymore. This was due to several errors in the build which
were hidden by the fact that the local repo on the TC machine had the
artifacts there. To be more precise, in order to do a release with
maven we cannot have any SNAPSHOT deps in our POM so we had to
"release" some external dependencies we're using in SNAPSHOT version.
One of these was the maven selenium plugin and I've discovered that
faking a release of an external maven plugin isn't as simple as it
appears... But I now know how to do that.
Thanks
-Vincent
Hi Vincent,
We are going to add copyright statements to Xeclipse source, I think we can
get them from xwiki sources, please let us know if you have any concerns...
Btw, is it Xeclipse or XEclipse ? :)
Thanks.
- Tharindu & Asiri
All those errors were caused by some disk space issue that has been
fixed now.
-Vincent
On Jul 24, 2007, at 2:18 PM, teamcity(a)xwiki.org wrote:
> Build XWiki Platform Web::Maven2 #217 failed
> Agent: Default agent
> Build results: http://teamcity.xwiki.org/viewLog.html?
> buildId=1395&buildTypeId=bt7
>
> Changes included (1 change)
> ====================================================
> Change 4019 by vmassol (1 file):
> XWIKI-1519: The version shouldn't come from xwiki.cfg file
>
> see more information about changed files: http://teamcity.xwiki.org/
> viewLog.html?tab=buildChangesDiv&buildId=1395&buildTypeId=bt7
>
>
> ======================================================================
> ======
> Configure email notifications: http://teamcity.xwiki.org/
> profile.html?init=1#notifications