The XWiki development team is pleased to announce the release of XWiki
Enterprise 2.5 Release Candidate 1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
Main changes since XWiki Enterprise 2.5 Milestone 2:
* New macros for the Space List and Tag Cloud
* Display user avatars in annotations
* A few improvements to the Extension Manager
* A few improvements to the User Directory
* WYSIWYG and Rendering improvements
* A few security and performance improvements
For more information see the Release notes at
http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXWikiEnterprise25RC1
Thanks
-The XWiki dev team
This is just a small API change proposal. Since my implementation changes for XWikiAttachment store
the attachment content in a temp file rather than a byte array, there is no need to require the user
to provide the length of the provided stream and in many cases (upload for instance) this number is
very difficult to determine in advance.
I propose we add:
public void setContent(InputStream is) throws IOException
In addition to the existing:
public void setContent(InputStream is, int length) throws IOException
WDYT?
Caleb
Hi,
I have some changes to the attachment system which will allow XWiki to handle much larger
attachments without memory exhaustion. I have found that there are some places where I cannot make
any changes because the code is not in XWiki but rather in JRCS.
XWiki versions attachments by creating a JRCS node for the XML version of each version of each
attachment. This means that memory consumption improvements hit a hard wall at 2 * 2 * 1.3 * the
size of the attachment. base-64 encoding for XML increases the size by 1.3 times, storage as a
String (array of 16 bit chars) doubles the size and the need to copy the String doubles the size again.
The second issue is that the database and JDBC do not handle multiple hundreds of megabytes in a
single query well. If I try to attach a 500MB attachment with attachment versioning disabled, my
changes allow the attachment to be streamed to the database but postgresql is not able to save it. I
am able to attach a 256MB attachment but with 512MB of heap space, the attachment cannot be loaded
from the database because JDBC lacks the necessary streaming functionality.
An option which I am now considering is adding a binary table to the database schema. The table
would contain a composite id made of the id of the data and the part number of that entry, and a
data column slightly smaller than 1MB (default max_allowed_packet in mysql). All interaction with
this table would go through a storage engine which would require InputStreams and OutputStreams and
the streams would be written and read by the storage mechanism which would ID tag them and break
them up into parts to be sent to the database individually.
WDYT?
Caleb
Hi devs,
I don't think that Monday is a good day for releases, since voting over
the weekend is not a good thing. Thus, I propose to move the general
release day to the Thursday of the week. The current release process
doesn't really follow the VOTE rules, since the way it's done is: send
vote mail at 10AM, wait a few hours, start the release around 1PM. The
rule for VOTE emails is to wait for three days.
Thus:
- Send release VOTE on Monday
- Prepare the release during the following three days (release plan,
release notes)
- Perform the maven release on Thursday, request tests for publishing
the release (testing of the build)
- Finalize the release on Friday (download, announcements, version update)
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hello Xwiki devs,
I want to customize the COLIBRI skin.. for the very beginning just the
colibry.css file.
Basically I've just added a few lines to the original file.
I don't want to paste into the 'style' text area (
http://localhost:8080/xwiki/bin/edit/XWiki/RtSkin?editor=object) the whole
content of the css file because like I said it has minor additions not
modifications.
Furthermore when a modification is done to the default colibry.css file,
mine's will be deprecated!
So do you happen to know if there is a placeholder for the default
colibry.css file?
To make myself clear, I've painted a pictogram :
Style________________________________
| %{placeholder for original Colibry.css}%
|
| AND here are my additions |
|____________________________________|
--
ing. Flueras Bogdan
How about <th width="50px"> in the HTML (like on
http://l10n.xwiki.org/xwiki/bin/view/L10N/ ) so that it works also for IE6?
Caty
On Tue, Oct 12, 2010 at 22:37, sdumitriu
<platform-notifications(a)xwiki.org>wrote:
> Author: sdumitriu
> Date: 2010-10-12 21:37:35 +0200 (Tue, 12 Oct 2010)
> New Revision: 31742
>
> Modified:
>
> platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/usersandgroups/usersandgroups.css
> Log:
> XWIKI-5572: Make the avatar column in the User Directory smaller
> Done.
>
> Modified:
> platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/usersandgroups/usersandgroups.css
> ===================================================================
> ---
> platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/usersandgroups/usersandgroups.css
> 2010-10-12 18:53:36 UTC (rev 31741)
> +++
> platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/usersandgroups/usersandgroups.css
> 2010-10-12 19:37:35 UTC (rev 31742)
> @@ -78,4 +78,9 @@
>
> tr.userorgroups-header {
> background-color:#DDDDDD;
> -}
> \ No newline at end of file
> +}
> +
> +/* Make the avatar column smaller */
> +table#groupusers th.xwiki-livetable-display-header-text:first-child {
> + width: 50px;
> +}
>
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications
>
Moving to github is an interesting solution, also it looks like they only gitified branches and tags
on an "as needed" basis.
Caleb
-------- Original Message --------
Subject: [hibernate-dev] Hibernate Core is now using Git
Date: Thu, 7 Oct 2010 11:30:11 +0200
From: Emmanuel Bernard <emmanuel(a)hibernate.org>
To: hibernate-dev(a)lists.jboss.org
Hibernate Core now uses Git as the version control system.
You can access it at http://github.com/hibernate/hibernate-core
Core on Git
We have imported the SVN history (at least what GIT could extract) and pushed the SVN trunk, branch
3.5 and branch 3.3. If you need more of the legacy branches or tags, let me know, that can be arranged.
If you want to contribute a fix or new feature, either use the pure Git approach, or use the GitHub
fork capability (see http://help.github.com/forking/ and http://help.github.com/pull-requests/ ) The
benefit of the GitHub approach is that we can comment on the pull request and code though I am far
from an expert so far and their flow could easily be improved (slightly confusing).
If you still want to do it the old way a provide a patch file, that's ok too.
Tips on Git
Here are some tips on Git:
o read Pro Git http://progit.org/book/ awesome book and very practical. It has a free html and epub
version (buying the tree version is recommended to repay the author).
o prefer the git protocol when cloning over http (so say the experts). At the very least that will
be much faster. cloning the repo from GitHub took me less than 3 minutes
#for people with read/write access
git clone git@github.com:hibernate/hibernate-core.git
#for people with read-only access
git clone git://github.com/hibernate/hibernate-core.git
It will create a "remote" link named origin. I usually tend to rename it to reflect what it is really.
git remote rename origin core-on-github
o always work on a topic branch and merge your work when you are done
git checkout master
git checkout -b HHH-XXX
hack commit hack commit
Likewise if you want to share a work with somebody from the Hibernate team, push or define the pull
request of your topic branch (though make sure your topic branch is above master).
o prefer small commits, they will be more readable and will very unlikely fail on merge
o write good comments (short one line including the issue at stack followed by a blank line and a
more detailed explanation if needed)
`HHH-XXX Fix NPE on persist
Fix stupid bug by Gavin that lead to a NPE when persisting objects with components`
o prefer rebase over merge
Rebase put changes from the branch you forked below the new commits you have done and thus keep the
history linear.
got checkout HHH-XXX
git rebase master
DO NOT rebase a branch that you have shared publicly (unless you know people won't use it or you
wish them harm).
o while you are at rebasing, you can rewrite your commit history to clean comments or merge some
commits together (named squashing)
git rebase -i HEAD~6 (go back 6 commits in time)
o once you're fed up with typing longish command lines, use aliases (see below)
o I've put a copy of my ~/.gitconfig file in case people want to copy some things including aliases
(see below)
o if you use Mac OS X, GitX is a fantastic tool, in particular to do interactive staging and commit
only some parts of a file
o you can read this blog entry that was some more info
http://blog.emmanuelbernard.com/2010/05/git-how-my-life-has-improved-since-…
o feel free to add your tips to this email thread, I'll likely compile them in a blog entry.
~/.gitconfig
[user]
name = Redacted
email = redacted(a)redacted.com
signingkey = id_key.pub
[core]
editor = open -nW -a Smultron
[merge]
tool = opendiff
[color]
ui = auto
[color "branch"]
current = yellow reverse
local = yellow
remote = green
[color "diff"]
meta = yellow bold
frag = magenta bold
old = red bold
new = green bold
[color "status"]
added = yellow
changed = green
untracked = cyan
[github]
user = redacted
token = redacted
[alias]
co = checkout
undo = reset --hard
cb = checkout -b
br = branch
cp = cherry-pick
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev