---------- Forwarded message ----------
From: Asiri Rathnayake <asiri.rathnayake(a)gmail.com>
Date: Mon, Mar 10, 2008 at 4:55 AM
Subject: Re: [xwiki-devs] xwiki-sandbox/org.xwiki.model vs
xwiki-sandbox/components/xwiki-model
To: Vincent Massol <vincent(a)massol.net>
Cc: XWiki Developers <devs(a)xwiki.org>
Hi Vincent,
Following is a simple discussion of the two implementations of the new
data-model of ArchitectureV2.
Both of these implementations are not complete yet and my knowledge of xwiki
is still limited. There for, there may be short-commings in the following
discussion, please bare with me and try to correct me where i'm wrong (this
will help me a lot).
xwiki-sandbox/components/xwiki-model (Vincent)
-----------------------------------------------------------------------
-> Represents a clear hierarchical view of domain objects
(Server->Wiki->Space->Page)
[ A simple graphical representation of the model is attached. ]
-> Does not include any administrative / security / rights related code
(simple model definitions).
-> Currently upward navigation (given a page find it's parent space) is not
possible.
(but i believe this can be implemented at a higher layer)
-> PropertyDefinition class is currently isolated, and no mention about
Users.
-> No mention about persistence related issues (DAOs).
-> All are concrete classes
Q.) Shouldn't we have interfaces (with a default impl) rather than
classes here ?
xwiki-sandbox/org.xwiki.model (Mikhail, Stéphane)
-------------------------------------------------------------------------
-> The business layer (org.xwiki.model) contains model classes (Farm, Wiki,
Space, Document, User) Along with (Session and XWikiException)
Q.) Strictly speaking, Session and XWikiException are not domain
classes. Shouldn't we try to keep things more simple in the model ?
-> Here the notion of a hierarchy seems to be little blured, Farm doesn't
have any method like getWikis() but it seems to contain some administrative
/ authentication related methods like createUser() and checkPassword() (This
looks quite odd for me). And with this model it is possible to navigate
upwards the hierarchy (Page->Space->Wiki).
-> Some domain classes have code related to session handling / user rights.
(is this ok?)
-> In a sense, domain classes seems to be active rather than being passive
(getters / setters).
Example : space.addPage(Page page) <- passive, space.newPage(, , ,) <-
active
Example (imaginary) : space.getPages(SomeFilter) <- passive,
space.getPages(...) {/* perform validations, access rights and return */} <-
active
-> There is a persistance layer (org.xwiki.model.dao). If we are to have two
seperate plexus components for storage and data-model (or in other words, to
decouple the model from storage), DAO classes should actually go inside the
storage component. Having DAO classes inside the model will automatically
bind the model to a particular storage implementation.
-> org.xwiki.model.dao seems to have a single DAO interface (IWikiDAO) to
access the storage rather than having separate DAO classes for each domain
class.
Q.) Why not have separate DAO classes for each model class ?
Q.) org.xwiki.model.dao has *Value classes for each domain class. Why
not use domain classes directly ?
-> There is a default in-memory implementation of IWikiDAO inside
org.xwiki.model.dao.memory
I think that's all for the moment.
Thanks.
- Asiri
On Sun, Mar 9, 2008 at 7:48 PM, Vincent Massol <vincent(a)massol.net> wrote:
> Hi Asiri,
>
> On Mar 9, 2008, at 2:25 PM, Asiri Rathnayake wrote:
>
> > Hi Stéphane,
> >
> > I think the new data model is commited at xwiki-sandbox/
> > org.xwiki.model. But i'm bit confused with xwiki-sandbox/components/
> > xwiki-model. What does the latter stand for ?
>
> The one in org.xwiki.model was done by Stephane and the other one by
> me ;)
>
> I guess they are two proposals for the same thing so we'll need to
> decide which one to use. Note that the one I have isn't finished
> either. We need to continue working on it, make proposals, etc.
> Maybe you could review both and send an email with the differences.
> This is an area I'd like to work on actively too. I've just been busy
> with the 1.3 release but now it's done I'll try to spend more time on
> the v2 components. However for this to happen we need someone to work
> actively on fixing the important 1.3 bugs, releasing a 1.3.1 (for
> example to fix the login issue with tomcat/IE7) and taking the lead on
> 1.4.
>
> Anyone interested in doing this or simply helping out?
>
> Thanks
> -Vincent
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
Hi Stéphane,
I think the new data model is commited at xwiki-sandbox/org.xwiki.model. But
i'm bit confused with xwiki-sandbox/components/xwiki-model. What does the
latter stand for ?
Thanks.
- Asiri
Hello,
Sergiu criticized that a MathTran (a TeX-daeomon over the web)
solution for formulae is bad because it relies on an external service
or a complex installation... probably correct and the rest of his
argument (in particular the wish for MathML) is more than valid!
But, I realize that scientific documents, the goal of spawn, right?,
are often made of external services.
Consider the success of TeXmacs, one of the great features is its
ability to connect to external systems, precisely.
Typically, the following artifacts are sensible products of external
services:
- plots of functions
- plots of data-sets
- presentation of data-sets
- advanced visualizations (e.g. chemical diagrams, construction
plans, interactive geometry constructions...).
I don't think we want all that to be solved internally in spawn,
using external services is a must and, on a web-system, those should
be web-services.
In many cases, the XWiki source may contain info to regenerate fully
the artifact (this is the case of many TeXmacs session I think), in
other cases external interactions are needed.
The service has to be running when authoring, for sure, but it should
not need to when running. Or at least breakage of it should not
impact viewers.
That leads me to think that a good approach would be to store the
products in a more managed way, e.g., as attachments, than in a cache
where it can go away for size reasons.
Comments welcome.
paul
Hi,
I see that under xwiki webapp there is a template directory, that contains
vm files. Same filenames are included in respective skins directory also.
So based on my understanding of how velocity files are called and invoked
upon user action, the vm files under templates directory play no role.
Also in some previous discussion it was mentioned that they were redundant
and there was a plan to separate common set of vm files into single
directory.
So I have two questions:
1. Can I delete the templates directory from my deployment.
2. If these files under this are no more required then what about deleting
them from svn istelf.
If have I have missed something and these files are required then please let
me know in what case would these be required.
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Is-templates-directory-required-any-more--tp15397359p…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi XWiki Committers,
I'd like to vote Anca Paula Luca as XWiki core committer. She's been a
committer on XWiki Watch for a long time, she understand the xwiki dev
process and she wants to work on our core GWT support to move it to
use GWT 1.4.
You can see her work here:
http://svn.xwiki.org/svnroot/xwiki/xwiki-platform/web/branches/xwiki-web-gw…
I feel she would be a great committer and she's interested in
maintaing and improving this GWT code on the long run.
Note that I have little idea how good the code on that branch is since
I have not touched GWT yet but I trust Anca to do a good job and
improve it if the quality is not to the par.
Here's my +1
Thanks
-Vincent
Hi All,
Sorry if this is the wrong place / time to ask this question.
I wanted to know whether XWiki will participate in GSoC
2008<http://code.google.com/soc/2008/>.
( care to hint some project ideas ? )
Thank you.
- Asiri
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.3 final.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This release spanned 2 full months starting on the 10th of January
2008 and ending on the 7th of March 2008. During that period we
implemented over 200 issues, fixing close to 100 bugs and adding new
features such as:
* Ability to export pages as HTML in a zip file
* Ability to export the current page in a XAR
* Better Oracle support
* New Toucan skin
* Complete rewrite of the LDAP authentication support including
the support for LDAP groups
* Diff emails sent by the Watchlist feature + ability to
customize the email sent
* Improved translation (German, French, Spanish) + new
transaltions (Slovak)
Main changes from 1.3RC1:
* Core changes:
o Bugs
+ XWIKI-1850 - No security against recursive includes
+ XWIKI-2047 - DB2 Hibernate Mapping for 1.2
+ XWIKI-2163 - XWiki.parseGroovyFromPage() doesn't
work when passing the a page containing JARs to be put in the Groovy
classloader
+ XWIKI-2164 - Cannot log out
+ XWIKI-2171 - When user is not in the bind_DN/
bind_pass search for DN from user uid fail
o Improvements
+ XWIKI-2157 - Add Slovak translation
+ XWIKI-2170 - Allow inactive users to see specific
pages
* Albatross Skin:
o Bugs
+ XSALBATROSS-18 - Parse error when serving skin.js
through SkinAction
* Toucan Skin:
o Bugs
+ XSTOUCAN-11 - RSS macro isn't styled correctly in
Toucan
+ XSTOUCAN-12 - In inline edit mode all the input
fields are stretched to the full content width
+ XSTOUCAN-13 - Numbered lists do not appear as
numbered
+ XSTOUCAN-17 - Bulletted lists do not show bullets
in the WYSIWYG editor
o Improvements
+ XSTOUCAN-14 - In admin mode allow clicking anywhere
on a tab to select it
+ XSTOUCAN-15 - Increase size of info box displayed
by the #xwikimessageboxstart macro
+ XSTOUCAN-16 - Remove borders for tables using the
memberstable class id
* Watchlist plugin
o Bugs
+ XPWATCHLIST-20 - Exception on Scheduler.WebHome
about "isDocumentWatched"
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise13
Thanks
-The XWiki dev team
Hi,
I'd like to commit a new service : criteriaService [1]. This service,
both available from java and velocity, allow to get various criteria
(most of them extracted from the statistics plugin) :
- Duration, a length of time
- Period, a length of time defined by a min date and a max date
- Range (formerly named Interval), an integer range (also allow to
sublist a list according to the range)
- RevisionCriteria, criteria to match document revisions (author, min
date, max date, minor edits)
- Scope, define an xwiki scope (page, space, wiki)
Since 4 of those objects are from the statistics I've refactored the
plugin and the application.
Modifications in the public APIs : duration,period,range and scope
factories won't be available from the statsService anymore since they
have moved to criteriaService.
Please shout if you're using any of those methods from velocity :
- $xwiki.getStatsService().getDurationFactory()
- $xwiki.getStatsService().getPeriodFactory()
- $xwiki.getStatsService().getIntervalFactory()
- $xwiki.getStatsService().getScopeFactory()
Additions :
- Document.getRevisions(RevisionCriteria), allowing to get document
revisions matching the criteria
- ListTool added to the rendering velocity context ($listtool)
First use case, in the watchlist plugin the diffs sent by email will
contain all the revisions since the last email notification (was : a
diff between the last 2 revisions) [2].
[1] http://jira.xwiki.org/jira/browse/XWIKI-2159
[2] http://jira.xwiki.org/jira/browse/XPWATCHLIST-15
JV.
Hi Devs,
Where can i find more details about the Component Based Architecture of
XWiki ?
I need as much information as possible.
Sorry if the source of information is obvious, i couldn't do much search coz
my machine is almost stuck running a neural network training algorithm (for
my final year project)
Thanks a lot.
- Asiri
Hi,
I was in a dire need to extended on of the xwiki plugin classes
MailSenderPlugin because xwiki implementation does not handle the password
authentication to smtp servers that require one.
I was unable to do so because the said class is declared final.
My only option is to modify the xwiki code itself to make the desired
change, but I certainly want to avoid this as I want to use only xwiki
binaries to take advantage of future functionality implementation and bug
fixes in by xwiki team.
So is there any specific reason why these classes were defined as final?
Is there anyway I can add such functionalities to xwki plugins without
modifying the xwiki source.
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Why-are-certain-Plugin-classes-final-tp15891099p15891…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Here's the new concept: as much people as possible in the XWiki
community must spend 1 hour on Wednesday, 5th of March 2008 (today,
sorry for the late announcement) and write documentation for 1 hour on
xwiki.org. This is an effort to improve the quality and content of our
documentation.
Rules:
* 1 hour
* You choose at what time you want to work on the documentation.
However most of us will be starting at 14:00 GMT+1.
* On xwiki.org
* You choose to document what you want. Ideas of missing documentation:
- In JIRA: http://tinyurl.com/3xtn8t
- Improve existing documentation
- XWiki Watch documentation on http://watch.xwiki.org
- XEM Documentation on http://manager.xwiki.org
* Make sure you create a jira issue for the work you're doing and
assign to yourself. The issue should be created in the XWiki Core
project, with a "documentation" component.
* If you can't do it on the 5th, then you can still do it on another
day, as close as possible to the 5th of March ;)
* The idea is to repeat this event every month or every 2 months.
Thanks everyone, let's see what we can do with the power of the
community! :)
-Vincent
Hi,
I've just seen that we have a XWiki.getFlash() method which just
renders a flash.vm template which simply output an <object
classid=...> to display a flash animation.
This has nothing to do in the core proper IMO.
I propose to move this in the macro.vm as a #flash macro.
WDYT?
Here's my +1
Thanks
-Vincent
Hi,
I'm moving our CI build to continuum today. More precisely:
* I've modified the TC build so that it does only "mvn clean install"
instead of "mvn clean deploy". I've left the site deployment for now
though. I've also removed the email notifications.
* I've modified our continuum instance to do "mvn clean deploy". I'm
going to work today on stabilizing the build to ensure all is ok and
when this is the case I'll add the email notifications.
http://continuum.xwiki.org/continuum/projectGroupSummary.action?projectGrou…
Thanks
-Vincent
Hi everyone and Jean-Vivien,
Jean-Vivien has done a lot of good work adding a tutorial on xwiki.org.
See http://platform.xwiki.org/xwiki/bin/view/DevGuide/MetadataLuceneTutorial
However I'm wondering where we should put it. Here's my current
thinking:
* This tutorial reflects Jean-Vivien's point of view only since it's
never been discussed AFAIK and there's no general agreement about its
content with the rest of the xwiki developers. As such I don't think
it can be located in at the same level as the other tutorials which
have been "endorsed" by the xwiki community.
I see 2 solutions:
1) We move it to the draft area and Jean-Vivien submits it for review
to the xwiki dev community. If the community agrees this is the right
way to implement it we put it with the other tutorials/
2) We move it to a contribution area that clearly marks the document
as a contributor's view and not as endorsed by the xwiki development
community. We don't have such a place today so we'll need to create
it. We could create it as a subpage of the Tutorial page in the
DevGuide or we could move it to the code zone to the code snippet
space since what Jean-Vivien has done is basically provide code
snippets to extend xwiki. It's a little bit more than a code snippet
since it's also a tutorial so I'm not sure the code zone is the best
place for it.
WDYT?
Jean-Vivien, some quick comments/questions on the content:
* Jens Karmer was the original author of the Lucene plugin. Since then
it's been worked on by numerous people.
* You shouldn't put ":" in titles
* The tutorial is missing a section at the beginning to explain what
the tutorial is about
* I haven't read the tutorial yet but if what you've done is useful
why not consider improving xwiki's core to support what you need? For
example it seems to me you're asking for a way to add custom metadata
to the lucene plugin. This could easily be added as part of the lucene
plugin API.
Thanks
-Vincent
Hi,
JAVA_HOME points to jdk installation directory.
JRE_HOME points to jre installation directory.
I too have both installed and variables set.
Try removing JRE_HOME for a change and see if this works.
Also do the following:
delete existing mvn folder.
unzip mvn2.1 snapshot zip available on dev.xwiki in c folder.
You can add the path to mvn bin in your system path.
Then try mvn -version
I have been building xwiki from source for quiet some time on windows and it
works fine.
If this still does not work you can connect me on sachin_mittal on skype and
I would try to help you with the same.
Thanks
Sachin
----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 4 Mar 2008 15:55:31 -0600
> From: "Kamna Jain" <kammy.scorpi(a)gmail.com>
> Subject: Re: [xwiki-devs] Building XWiki Core
> To: devs(a)xwiki.org
> Message-ID:
> <fb681d280803041355q1b3dd893uf1769a2ba41156c1(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Yes, I have both JDK and JRE installed in the same location. (is that a
> problem?)
> Sachin, I did add the bin dir. of mvn install to the Path variable but it
> does not seem to help.
> mvn --version also gives the same error as mvn install:
>
> ERROR: JAVA_HOME not found in your environment.
> Please set the JAVA_HOME variable in your environment to match the
> location of your Java installation
>
> This is the error I get.
>
> Thanks
>
Yes, I have both JDK and JRE installed in the same location. (is that a
problem?)
Sachin, I did add the bin dir. of mvn install to the Path variable but it
does not seem to help.
mvn --version also gives the same error as mvn install:
ERROR: JAVA_HOME not found in your environment.
Please set the JAVA_HOME variable in your environment to match the
location of your Java installation
This is the error I get.
Thanks
On Tue, Mar 4, 2008 at 1:45 AM, <devs-request(a)xwiki.org> wrote:
> Send devs mailing list submissions to
> devs(a)xwiki.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.xwiki.org/mailman/listinfo/devs
> or, via email, send a message with subject or body 'help' to
> devs-request(a)xwiki.org
>
> You can reach the person managing the list at
> devs-owner(a)xwiki.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devs digest..."
>
>
> Today's Topics:
>
> 1. Re: Building Xwiki core (Sergiu Dumitriu)
> 2. [proposal] upgrade web-gwt to gwt 1.4 (ancapaula.luca(a)xwiki.com)
> 3. Re: [proposal] upgrade web-gwt to gwt 1.4 (Sergiu Dumitriu)
> 4. Re: GWT 1.4 upgrade (ancapaula.luca(a)xwiki.com)
> 5. Re: [proposal] upgrade web-gwt to gwt 1.4 (Jerome Velociter)
> 6. Re: Building Xwiki core (Kamna Jain) (sachin mittal)
> 7. Re: [xwiki-notifications] r8181 -
> xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki
> (Vincent Massol)
> 8. Re: [xwiki-notifications] r8184 -
> xwiki-platform/core/branches/xwiki-core-1.3
> /xwiki-core/src/main/java/com/xpn/xwiki
> (Vincent Massol)
> 9. Re: GWT 1.4 upgrade (Vincent Massol)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 03 Mar 2008 22:43:48 +0100
> From: Sergiu Dumitriu <sergiu(a)xwiki.com>
> Subject: Re: [xwiki-devs] Building Xwiki core
> To: XWiki Developers <devs(a)xwiki.org>
> Message-ID: <47CC7114.4040006(a)xwiki.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Kamna Jain wrote:
> > Yes,
> > I am setting the JAVA_HOME variable with DOS prompt
> > and after I set it, I log of and then it is available in the list of
> > env. variables after I log back in.
> > But, when I try to run mvn install, it still gives me the same error.
> >
> > Also, although, I set the M2_HOMe variable, I am not able to use mvn
> > command without its location! (I have to write the full path of the
> > mvn.bat file and then say install after a space)
> > I dont know what I am doing wrong.
> >
> > Thanks for your replies.
> >
> >
>
> I remember seeing this on another windows machine. It has something to
> do with that crappy thing they like to call an Operating System and the
> way it executes the maven script.
>
> Do you by any chance have installed both the JDK and the JRE?
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 3 Mar 2008 23:31:15 +0100 (CET)
> From: ancapaula.luca(a)xwiki.com
> Subject: [xwiki-devs] [proposal] upgrade web-gwt to gwt 1.4
> To: devs(a)xwiki.org
> Message-ID: <51105.130.79.213.35.1204583475.squirrel(a)mail.xwiki.com>
> Content-Type: text/plain;charset=iso-8859-1
>
> Hi developers!
>
> I'd like to upgrade the web-gwt module to gwt 1.4, as in the dedicated
> branch
>
> https://svn.xwiki.org/svnroot/xwiki/xwiki-platform/web/branches/xwiki-web-g…
> .
> A stable upgrade will be finalized tomorrow, although there will still
> remain a couple of appearance issues to be solved until the xwiki-web 1.4
> milestone release.
>
> WDYT?
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 03 Mar 2008 23:39:36 +0100
> From: Sergiu Dumitriu <sergiu(a)xwiki.com>
> Subject: Re: [xwiki-devs] [proposal] upgrade web-gwt to gwt 1.4
> To: XWiki Developers <devs(a)xwiki.org>
> Message-ID: <47CC7E28.90507(a)xwiki.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> ancapaula.luca(a)xwiki.com wrote:
> > Hi developers!
> >
> > I'd like to upgrade the web-gwt module to gwt 1.4, as in the dedicated
> > branch
> >
> https://svn.xwiki.org/svnroot/xwiki/xwiki-platform/web/branches/xwiki-web-g…
> > .
> > A stable upgrade will be finalized tomorrow, although there will still
> > remain a couple of appearance issues to be solved until the xwiki-web
> 1.4
> > milestone release.
> >
> > WDYT?
> >
>
> +1
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 3 Mar 2008 23:51:35 +0100 (CET)
> From: ancapaula.luca(a)xwiki.com
> Subject: Re: [xwiki-devs] GWT 1.4 upgrade
> To: "XWiki Developers" <devs(a)xwiki.org>
> Message-ID: <39500.130.79.213.35.1204584695.squirrel(a)mail.xwiki.com>
> Content-Type: text/plain;charset=iso-8859-1
>
> Because from the reliability point of view the native gwt solution is
> better than a third-party library and produces cleaner code while the
> styling drawback can easily be ameliorated, we have chosen it from the two
> and applied it for the gwt 1.4 upgrade branch.
>
> We also didn't get any response from the gwt-tk mailing list regarding a
> future release.
>
> > Hi devs,
> >
> > We have planned the GWT 1.4 upgrade for the next XWatch milestone at the
> > end of march. For this, we need to make a decision regarding the web-gwt
> > dependencies (for the moment, the xwiki gwt dialogs rely on the gwt-tk
> > library that does not yet have a release for gwt 1.4) so we must choose
> > from:
> > - using another library to provide this functionality, particularly the
> > MyGwt library
> > pros: nice looks and good API + the possibility of using the
> library
> > components in including projects.
> > cons: code changes required by the clean switch (updating all
> involved
> > classes to use library API instead of GWT API), the lack of a maven
> > repository with all available MyGwt versions (only 0.5.0 rc). As well,
> > while testing, I experienced a couple of rendering issues (caused,
> > seemingly by the use of the strict or xhtml DTD).
> > - using the native gwt modal dialogs introduced in 1.4:
> > pros: not styled (we totally control the styling process and can
> build an
> > uniform look); widgets consistency, at least at this level. A big
> > advantage is that the web-gwt module will not depend on any other
> library
> > anymore.
> > cons: not styled, the usual GWT API (which can be poor in some
> > situations); GWT also has some problems caused by the standard mode
> > interpretation in browsers (caused by the doctype declaration) but in
> > this situation the code seems to be stable.
> >
> > What do you think?
> >
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 4 Mar 2008 05:34:44 +0100 (CET)
> From: "Jerome Velociter" <jerome(a)xwiki.com>
> Subject: Re: [xwiki-devs] [proposal] upgrade web-gwt to gwt 1.4
> To: "XWiki Developers" <devs(a)xwiki.org>
> Message-ID: <57026.86.124.34.145.1204605284.squirrel(a)mail.xwiki.com>
> Content-Type: text/plain;charset=iso-8859-1
>
> +1,
>
> Jerome.
>
> > Hi developers!
> >
> > I'd like to upgrade the web-gwt module to gwt 1.4, as in the dedicated
> > branch
> >
> https://svn.xwiki.org/svnroot/xwiki/xwiki-platform/web/branches/xwiki-web-g…
> > .
> > A stable upgrade will be finalized tomorrow, although there will still
> > remain a couple of appearance issues to be solved until the xwiki-web
> 1.4
> > milestone release.
> >
> > WDYT?
> >
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 4 Mar 2008 10:19:36 +0530
> From: "sachin mittal" <sjmittal(a)gmail.com>
> Subject: Re: [xwiki-devs] Building Xwiki core (Kamna Jain)
> To: devs(a)xwiki.org
> Message-ID:
> <79d89bcf0803032049r49a43339hf583a9d5f5526d5e(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
> Can you paste the console output.
> You can add the maven bin directory to the path variable so that you dont
> have to type the full path to mvn.bat every time you run the mvn scripts.
>
> Also what do you get when you type mvn -version in the command prompt.
>
> Thanks
> Sachin
>
>
>
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Mon, 3 Mar 2008 15:32:30 -0600
> > From: "Kamna Jain" <kammy.scorpi(a)gmail.com>
> > Subject: Re: [xwiki-devs] Building Xwiki core
> > To: devs(a)xwiki.org
> > Message-ID:
> > <fb681d280803031332y756f2f66g72f65d3b687ca66(a)mail.gmail.com>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Yes,
> > I am setting the JAVA_HOME variable with DOS prompt
> > and after I set it, I log of and then it is available in the list of
> env.
> > variables after I log back in.
> > But, when I try to run mvn install, it still gives me the same error.
> >
> > Also, although, I set the M2_HOMe variable, I am not able to use mvn
> > command
> > without its location! (I have to write the full path of the mvn.bat file
> > and
> > then say install after a space)
> > I dont know what I am doing wrong.
> >
> > Thanks for your replies.
> >
>
Hi devs,
As detailed in another mail
(http://lists.xwiki.org/pipermail/devs/2008-February/005344.html), the
current attachment archive mechanism is very inefficient. We should
write a new one, which stores attachment versions as plain binary data,
and see if the current core is pluggable enough to allow the old
mechanism to be preserved as a plugin, and possibly define other storage
mechanisms, like a filesystem based one.
Artem, do you think you can help, as this is something related to what
you've been working on?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/