The XWiki development team is proud to announce the availability of XWiki
Enterprise 4.2 Release Candidate 1.
This is the first and hopefully final release candidate of the 4.2 release
cycle. Being a release candidate, this release contains bugfixes and
polishing, most of them focused on the new distribution wizard.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris…
Thanks
-The XWiki dev team
Hi devs,
Some time ago, I wrote a usefull extension:
http://extensions.xwiki.org/xwiki/bin/view/Extension/DBListManager+Applicat…
Some developers need it for clients, so it could be great to have it on
maven.
So please, would you like to add this project on "contribs" (github +
maven) ?
Thanks.
Louis-Marie
Hello,
Since XWiki support user accounts, enabling visitors to create an account
and sign in to the site, Can you tell me if It's possible with a little bit
of effort track the activity of logged users? This can include recording
activities such as what pages were visited as well as what actions were
performed. May be it is possible implementing a plugin with Velocity or
extracting the data from database. Have any idea how to do it?
Thanks!!
--
*Ezequiel Scott**
*
ezequielscott(a)gmail.com
Hello developers,
I've been experimenting a little bit into running things in the background on our xwiki 3.5: as part of a velocity delivered page, I am calling groovy code. That code launches a thread in the background which runs for 1000 seconds checking if it can:
- use the context's toString
- call context.getContext()
- use the xwiki object that was passed around
My current conclusion is that context.getContext() fails (with an NPE trying to check programming rights) but others work.
Is this the intended behavior?
Is there a way for me to get another context to run in the background?
thanks in advance
Paul
Hi,
Thanks for the fix,
@vincent: you can test it, or wait for 0.2 that should fix many UI bugs. I've started working on it and should deliver it in 1 or 2 weeks.
Envoyé depuis mon HTC
----- Reply message -----
De : "Thomas Mortagne" <thomas.mortagne(a)xwiki.com>
Pour : "XWiki Developers" <devs(a)xwiki.org>
Objet : [xwiki-devs] [Contrib] xwiki-application-mailarchive
Date : mer., sept. 19, 2012 16:23
The download link was wrong, just fixed it.
On Wed, Sep 19, 2012 at 4:17 PM, Vincent Massol <vincent(a)massol.net> wrote:
> Hi Jeremie,
>
> Should I start testing your mailarchive app? I see on http://extensions.xwiki.org/xwiki/bin/view/Extension/MailArchive+Application that it's not installable with the EM. Is that "normal"?
>
> Thanks
> -Vincent
>
> On Sep 18, 2012, at 11:11 AM, Vincent Massol <vincent(a)massol.net> wrote:
>
>> Hi Jeremie,
>>
>> For the next version of the MailArchive app you may want to add a Application Panel UIExtension object so that the mailarchive application appears in the new Application panel automagically when it's installed. It would be very nice.
>>
>> See http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris…
>>
>> Note that it requires XWiki 4.2M3+ but if the XClass isn't there it's not going to fail on older XWiki versions (it just won't do anything).
>>
>> Thanks
>> -Vincent
>>
>> On Sep 14, 2012, at 4:16 PM, Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com> wrote:
>>
>>> Hum, thanks ...
>>> As it's not a so big issue I think what I'll prefer to do, is fastly
>>> deliver a new 0.2 version with fixed page, and leave the 0.1 as it is,
>>> or ask for its deletion later.
>>>
>>>
>>> 2012/9/14 Thomas Mortagne <thomas.mortagne(a)xwiki.com>:
>>>> On Fri, Sep 14, 2012 at 3:04 PM, Jeremie BOUSQUET
>>>> <jeremie.bousquet(a)gmail.com> wrote:
>>>>> I was almost sure I would make a mistake, and I did...
>>>>> In the documentation embedded in the .xar, the user guide is not
>>>>> correct, because it has screenshots coming from the app as used in my
>>>>> organization ...
>>>>> Not that there are things so confidential, but still not something I'm fond of.
>>>>>
>>>>> Do you think it would be possible to either:
>>>>> - replace delivered 0.1 with a new 0.1 version with fixed
>>>>> documentation ? (hideously ugly, but as it impacts only documentation
>>>>> ...)
>>>>> - deliver a new 0.2 and remove 0.1 from nexus ?
>>>>
>>>> It's not yet Maven central rules ( ;) ) so we can remove things if you
>>>> absolutely need to. Note that it also mean delete the current 0.1 tag
>>>> from git. As you prefer, it's recent enough to be deleted even if it's
>>>> a pain on your side to do.
>>>>
>>>>>
>>>>> Anyway for sure I will not put the same on e.x.o ...
>>>>>
>>>>> Br,
>>>>> Jeremie
>>>>>
>>>>>
>>>>>
>>>>> 2012/9/14 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>> 2012/9/14 Thomas Mortagne <thomas.mortagne(a)xwiki.com>:
>>>>>>> On Fri, Sep 14, 2012 at 12:57 PM, Jeremie BOUSQUET
>>>>>>> Note that the id are wrong (one of the reason to use the import UI
>>>>>>> instead of creating from scratch ;)). You can change it in edit
>>>>>>> object, it's important have the same id that the one on maven
>>>>>>> repository which mean
>>>>>>> org.xwiki.contrib.mailarchive:xwiki-contrib-mailarchive-ui for the ui
>>>>>>> for example otherwise Extension Manager will see two different
>>>>>>> extensions in extensions.xwiki.org and maven repositories while it's
>>>>>>> actually exactly the same thing.
>>>>>>
>>>>>> This is fixed, thanks !
>>>>>> That "import" button, I noticed it, and still can't understand why I
>>>>>> didn't click on it ! :D
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> 2012/9/14 Thomas Mortagne <thomas.mortagne(a)xwiki.com>:
>>>>>>>>> On Fri, Sep 14, 2012 at 9:13 AM, Jeremie BOUSQUET
>>>>>>>>> <jeremie.bousquet(a)gmail.com> wrote:
>>>>>>>>>> I guess I have to create an extension page for each artifact ? (mail
>>>>>>>>>> extension, mailarchive api extension, mail archive ui extension)
>>>>>>>>>> Didn't had time to test within extension repository manager locally,
>>>>>>>>>> so I hope it'll work ! :)
>>>>>>>>>
>>>>>>>>> Actually since it's released on maven repository you can import it and
>>>>>>>>> then complete the description.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2012/9/13 Vincent Massol <vincent(a)massol.net>:
>>>>>>>>>>> I guess the next step is to create the extension page on e.x.o.
>>>>>>>>>>>
>>>>>>>>>>> That'll be awesome and I'll start testing it when it's there! :)
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> -Vincent
>>>>>>>>>>>
>>>>>>>>>>> On Sep 13, 2012, at 1:39 PM, Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Thanks !
>>>>>>>>>>>> No problem ...
>>>>>>>>>>>>
>>>>>>>>>>>> 2012/9/13 Vincent Massol <vincent(a)massol.net>:
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sep 13, 2012, at 10:13 AM, Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2012/9/2 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>>>>>>>>>>>> I could successfully deploy mail archive artifacts to nexus staging !
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Would someone kindly promote it ? :)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi, just to recall that to you ... :)
>>>>>>>>>>>>>> (I know, seems a bit of a rush on 4.2 cycle and there is no urgency on
>>>>>>>>>>>>>> my side, just want to avoid moving too deep in the mailing-list)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Done! Sorry for the lag…
>>>>>>>>>>>>>
>>>>>>>>>>>>> -Vincent
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2012/9/2 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>>>>>>>>>>> (groupId : org.xwiki.contrib.mailarchive, version : 0.1, artifacts
>>>>>>>>>>>>>>> xwiki-contrib-mail, xwiki-contrib-mailarchive-api,
>>>>>>>>>>>>>>> xwiki-contrib-mailarchive-ui)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Jeremie
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Jeremie
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2012/9/1 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>>>>>>>>>>>>> Wow, eventually, it worked ... Had to switch to using
>>>>>>>>>>>>>>>>> maven-release-plugin last version (2.3.2) instead of the one from
>>>>>>>>>>>>>>>>> xwiki.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Now I'm ... back to the initial issue with the enforcer :
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [WARNING] Rule 0:
>>>>>>>>>>>>>>>>> org.apache.maven.plugins.enforcer.EvaluateBeanshell failed with
>>>>>>>>>>>>>>>>> message:
>>>>>>>>>>>>>>>>> Couldn't evaluate condition: ("pom" != "jar") || ("pom" == "jar"
>>>>>>>>>>>>>>>>> && new java.io.File("C:\PRIVATE\Dropbox\MAILARCHIVE\target\checkout\target/xwiki-contrib-mailarchive-0.1-javado
>>>>>>>>>>>>>>>>> c.jar").exists())
>>>>>>>>>>>>>>>>> [INFO] ------------------------------------------------------------------------
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Grrrr !
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 2012/9/1 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>>>>>>>>>>>>>> I eventually was able to use push to git from maven with release
>>>>>>>>>>>>>>>>>> plugin (had to reinstall git with more preservative options).
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> But previous issue is still there: when checking-out my tag from local
>>>>>>>>>>>>>>>>>> clone in target/checkout, pom.xml files are not there so there's
>>>>>>>>>>>>>>>>>> nothing to build for maven ...
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2012/9/1 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>>>>>>>>>>>>>>> Progressing but still failing ...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> ... it's like a nightmare.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I gave up pushing to github from maven, I think there's something
>>>>>>>>>>>>>>>>>>> wrong with windows/mysysgit/cygwin somehow.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Now trying to release tag "xwiki-contrib-mailarchive-0.1":
>>>>>>>>>>>>>>>>>>> - it's pushed on github
>>>>>>>>>>>>>>>>>>> - if I download the related zip (in "tag" tab on github), it's complete
>>>>>>>>>>>>>>>>>>> - if I "release:perform" from maven, target/checkout folder contains
>>>>>>>>>>>>>>>>>>> everything except pom.xml files ... of course release fails
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> How can my pom.xml files be deleted when running "git checkout
>>>>>>>>>>>>>>>>>>> xwiki-contrib-mailarchive-0.1", while I can see them in my local
>>>>>>>>>>>>>>>>>>> history and on github ???
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 2012/8/31 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>>>>>>>>>>>>>>>> I tried both, but not tried exhaustively possible combinations
>>>>>>>>>>>>>>>>>>>> (ssh/https, maven/git conf, and my network proxy that comes in the way
>>>>>>>>>>>>>>>>>>>> ...)
>>>>>>>>>>>>>>>>>>>> BTW I'm not sure about how credentials for github should be fed to
>>>>>>>>>>>>>>>>>>>> maven depending on SSH/HTTPS url connection used.
>>>>>>>>>>>>>>>>>>>> Authentication with keys works from git command-line to push to
>>>>>>>>>>>>>>>>>>>> github, but I think I miss some configuration maven-side.
>>>>>>>>>>>>>>>>>>>> Actually from maven "git push" time-outs, or freezes forever,
>>>>>>>>>>>>>>>>>>>> depending on protocol used.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> 2012/8/31 Thomas Mortagne <thomas.mortagne(a)xwiki.com>:
>>>>>>>>>>>>>>>>>>>>> On Fri, Aug 31, 2012 at 9:17 AM, Jeremie BOUSQUET
>>>>>>>>>>>>>>>>>>>>> <jeremie.bousquet(a)gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>> Hi Community,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I'm trying to release my contrib project to nexus staging but having
>>>>>>>>>>>>>>>>>>>>>> difficulties.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Couldn't manage to "git push" correctly from maven to github (though
>>>>>>>>>>>>>>>>>>>>>> "git push" command-line works), so I use "-DpushChanges=false" during
>>>>>>>>>>>>>>>>>>>>>> release:prepare and release:perform, and do a "git push" manually
>>>>>>>>>>>>>>>>>>>>>> after release:prepare.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> You sure you <scm> is right ? I see you indicated the https in
>>>>>>>>>>>>>>>>>>>>> <developerConnection>, you should probably use the ssh one instead.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Now getting that during release:perform (***** were added, it's a
>>>>>>>>>>>>>>>>>>>>>> correct path behind) :
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> [INFO] --- maven-enforcer-plugin:1.0.1:enforce
>>>>>>>>>>>>>>>>>>>>>> (enforce-javadoc-exists) @ xwiki-contrib-mailarchive ---
>>>>>>>>>>>>>>>>>>>>>> [WARNING] Rule 0:
>>>>>>>>>>>>>>>>>>>>>> org.apache.maven.plugins.enforcer.EvaluateBeanshell failed with
>>>>>>>>>>>>>>>>>>>>>> message:
>>>>>>>>>>>>>>>>>>>>>> Couldn't evaluate condition: ("pom" != "jar") || ("pom" == "jar"
>>>>>>>>>>>>>>>>>>>>>> && new java.io.File("C:\*****\target\checkout\target/xwiki-contrib-mailarchive-0.1-javadoc.jar").exists())
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Of course javadoc does not exist at this level, as I'm trying to
>>>>>>>>>>>>>>>>>>>>>> release from root aggregator. What I don't understand is why the
>>>>>>>>>>>>>>>>>>>>>> enforcer rule fails ? Aggregator is of type "pom" as expected.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> My command-line was:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> mvn release:perform -DpushChanges=false
>>>>>>>>>>>>>>>>>>>>>> -DconnectionUrl=scm:git:https://github.com/xwiki-contrib/xwiki-application-mailarchive.git
>>>>>>>>>>>>>>>>>>>>>> -Dtag=xwiki-contrib-mailarchive-0.1
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>> Jeremie
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> 2012/8/17 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>>>>>>>>>>>>>>>>>>> Hi Vincent,
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> I saw that, no problem I'll update the groupId before doing the release :)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Br,
>>>>>>>>>>>>>>>>>>>>>>> Jeremie
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> 2012/8/16 Vincent Massol <vincent(a)massol.net>:
>>>>>>>>>>>>>>>>>>>>>>>> Hi Jeremie,
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> In case you haven't followed we've updated the contrib rule for the maven group id, see
>>>>>>>>>>>>>>>>>>>>>>>> http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> It would be great if you could update your groupid before you do the first release :)
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>> -Vincent
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Aug 16, 2012, at 9:50 AM, Jeremie BOUSQUET wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Vincent & Sergiu,
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> So, is it ok if I put docs to
>>>>>>>>>>>>>>>>>>>>>>>>> http://extensions.xwiki.org/xwiki/bin/view/MailArchive/Documentation
>>>>>>>>>>>>>>>>>>>>>>>>> (and others in same space) ?
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> By now I've almost finished writing first versions of:
>>>>>>>>>>>>>>>>>>>>>>>>> * MailArchive.Documentation (home page)
>>>>>>>>>>>>>>>>>>>>>>>>> * MailArchive.UserGuide
>>>>>>>>>>>>>>>>>>>>>>>>> * MailArchive.AdminGuide
>>>>>>>>>>>>>>>>>>>>>>>>> * MailArchive.OperationsGuide
>>>>>>>>>>>>>>>>>>>>>>>>> * MailArchive.TroubleShooting
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> I should be able to release 0.1 soon ...
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Br,
>>>>>>>>>>>>>>>>>>>>>>>>> Jeremie
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> 2012/8/13 Thomas Mortagne <thomas.mortagne(a)xwiki.com>:
>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Aug 13, 2012 at 3:23 PM, Vincent Massol <vincent(a)massol.net> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 13, 2012, at 3:17 PM, Vincent Massol wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Jeremie and all,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Back from holidays too :) Cool to see progress on this!
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ok I've parsed this thread and here's my take:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> * JIRA: I'll create a dedicated JIRA project since the project seems large enough to warrant it
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> ok, Thomas is doing it ATM, should be ready real soon :)
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Done, http://jira.xwiki.org/browse/XMAILARCH. You should have the
>>>>>>>>>>>>>>>>>>>>>>>>>> rights to do pretty much anything in this project.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> * Documentation: our rule is currently to have pages on extensions.xwiki.org and if the project becomes too large to create a dedicated wiki for it, as we've done for rendering.xwiki.org, commons.xwiki.org, enterprise, etc for example (see http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome). IMO it's ok ATM to have several pages on e.x.o for the MailArchive application and we can decide later on to move it to its own wiki (after we have a 1.0 released IMO).
>>>>>>>>>>>>>>>>>>>>>>>>>>>> * Nexus: I'll create an account for you.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> I see you already have a user, cool.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>>>>> -Vincent
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Is that ok?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>>>>>>>>>>>>>>> -Vincent
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 10, 2012, at 9:51 AM, Jeremie BOUSQUET wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So I'd say that:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - There should be some documentation on the extension page, at least a
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> description of the project, some usage scenarios, some screenshots, and a
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> list of the features
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - I agree that the full documentation should be included in the application
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> itself
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - The same full documentation should also be available online, and the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> contrib wiki seems to be the right place (in a dedicated space)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I think it's the best solution.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Since the space I currently use for the main pages of my app is
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "MailArchive", I would propose to use the same for the documentation
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> space and put pages under:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://contrib.xwiki.org/xwiki/bin/view/MailArchive/
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> That way publishing the doc online to contrib wiki would be
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> straightforward with selective import.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Br,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Jeremie
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2012/8/9 Sergiu Dumitriu <sergiu(a)xwiki.com>:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 08/09/2012 10:38 AM, Jerome Velociter wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On 08/09/2012 04:34 PM, Jeremie BOUSQUET wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Humm ... Just thinking I might put that directly inside my app xar ...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> WDYT ?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm a big fan of self-documenting applications. It has the great
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> advantage of always offering documentation matching the version in use.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> But you might also want to offer the latest released version
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> documentation online. I think there are some extensions that have
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> documentation that spans several pages, but honestly I don't know if
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> this is something we want/we agreed upon. I'll leave it to others to
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> bring more information on this subject. There is the contrib wiki also
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> which could be a candidate.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I've seen extensions with a lot of documentation on their extension page,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> and I've seen things documented in several places. Personally, I don't like
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> huge extension pages.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So I'd say that:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - There should be some documentation on the extension page, at least a
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> description of the project, some usage scenarios, some screenshots, and a
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> list of the features
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - I agree that the full documentation should be included in the application
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> itself
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - The same full documentation should also be available online, and the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> contrib wiki seems to be the right place (in a dedicated space)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2012/8/9 Jeremie BOUSQUET <jeremie.bousquet(a)gmail.com>:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks Jerome,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Another thing about this project: I'd like to prepare things, and
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> particularly the user guide part, so it's available when I'll publish
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the extension.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> For this particular use-case though, I'd like to extend the user/admin
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> guide part on more than one page, as it may be quite large.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Where should I put these pages ?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Jeremie
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> devs mailing list
>>>>>>>>>>> devs(a)xwiki.org
>>>>>>>>>>> http://lists.xwiki.org/mailman/listinfo/devs
>>>>>>>>>> _______________________________________________
>>>>>>>>>> devs mailing list
>>>>>>>>>> devs(a)xwiki.org
>>>>>>>>>> http://lists.xwiki.org/mailman/listinfo/devs
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thomas Mortagne
>>>>>>>>> _______________________________________________
>>>>>>>>> devs mailing list
>>>>>>>>> devs(a)xwiki.org
>>>>>>>>> http://lists.xwiki.org/mailman/listinfo/devs
>>>>>>>> _______________________________________________
>>>>>>>> devs mailing list
>>>>>>>> devs(a)xwiki.org
>>>>>>>> http://lists.xwiki.org/mailman/listinfo/devs
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thomas Mortagne
>>>>>>> _______________________________________________
>>>>>>> devs mailing list
>>>>>>> devs(a)xwiki.org
>>>>>>> http://lists.xwiki.org/mailman/listinfo/devs
>>>>> _______________________________________________
>>>>> devs mailing list
>>>>> devs(a)xwiki.org
>>>>> http://lists.xwiki.org/mailman/listinfo/devs
>>>>
>>>>
>>>>
>>>> --
>>>> Thomas Mortagne
>>>> _______________________________________________
>>>> devs mailing list
>>>> devs(a)xwiki.org
>>>> http://lists.xwiki.org/mailman/listinfo/devs
>>> _______________________________________________
>>> devs mailing list
>>> devs(a)xwiki.org
>>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
:D
I left off with Xwiki/Solr a few weeks ago.
Are there plans to move it into the main project any time soon?
________________________________
This communication (including all attachments) is intended solely for
the use of the person(s) to whom it is addressed and should be treated
as a confidential AAA communication. If you are not the intended
recipient, any use, distribution, printing, or copying of this email is
strictly prohibited. If you received this email in error, please
immediately delete it from your system and notify the originator. Your
cooperation is appreciated.
Hi devs,
Just wanted to share my vision of how we should tackle migrating to the new Model. I see the following steps:
* Step 1: Define new model interfaces (status: in progress)
* Step 2: Implement a "bridged" version which uses the oldcore (status: in progress).
* Step 3: Start moving code to use the new API as the new API and its implementation progress. Note: we should start using the produce of step1 and step2 ASAP to tune the details (status: not started)
* Step 4: At the same time, start a new implementation based on a RDBMS (probably hibernate-based, to be decided) (status: not started). I'd also like that we start other implementations not based on a RDBMS just to prove that it works with other storages. Ideally I'd like some NoSQL impl (Caleb maybe?) and I'd also like to try a Git-based implementation (using jgit)
* Step 5: Deprecate all our search apis located in XWikiHibernateStore and make everyone use the new QueryManager module. This needs some tuning on the QueryManager for missing stuff but that's doable (I need to send some proposal on missing stuff). (status: in progress). The idea here is to decouple search from storage. Note that we'll need to write some translator from HQL to XWQL or the new search query language.
* Step 6: As we progress in step 2, 3, 4, introduce a configuration parameter to decide which implementation to use ("bridged", etc) so that users can start playing with new implementations (status: not started)
* Step 7: Rewrite a new Importer/Exporter that exports everything (all the data in the current DB) + all configuration files/data. To see what we are currently not exporting, see http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Backup#HUsingtheXWikiEx… This new exporter should probably be based on the XWiki Streams module being developed here: https://github.com/xwiki-contrib/wiki-stream (status: in progress but not active)
* Step 8: When users want to migrate from one implementation ("bridged" for ex) to a new implementation they export their wiki, set the new implementation in the configuration file and reimport. (status: not started)
For me Step3 can almost begin (I probably need one or 2 more weeks to be ready to have some use cases implemented and I'll send a vote to merge my work in feature-newmodel branch in master - Would be good if you guys start looking at it and give comments to be ready for this).
Then we need volunteer for Step 4 for:
* new RDBMS implementation. Who?
* noSQL impl. Cassandra? other? Who?
* git implementation. Vincent
WDYT about the plan?
In term of time required it's probably going to take us about a year to have a first working version for all the steps by working at a leisurely pace.
Thanks
-Vincent
Hello devs,
we are having a very very weird bug: the two nodes of our cluster are made of A and B and saved objects sync into B when written on A but fail to do sync into A when written on B.
What could be the cause?
thanks in advance
Paul
Hi devs,
We've been talking about this for a long time already. We've even seen what Jenkins does (go to http://ci.xwiki.org and click on the bottom left link).
Today I've seen an article showing a cool new plugin for JIRA to help localize JIRA:
http://blogs.atlassian.com/2012/09/inproduct-translation-plugin-beta/
Since XWiki allows overriding translation in wiki pages we have almost the same features OOB as those touted on the JIRA plugin page:
* "Access Management: control which groups can translate JIRA". We have that too with wiki right management
* "Instant updates: translations are saved automatically and appear immediately for all users". Same for us
• "Mouse-hover: items turn green to let you know they are translatable". This is the cool part we're missing. It would be awesome to be able to do this. We should brainstorm about how to be able to do that.
* "Translate Page: select from your username drop-down". We don't have that either and it would be cool to write/bundle in XE a Translation app to let users write translations in their wiki and then to contribute them with one click to l10n.xwiki.org (we'd need to put l10n on SCM too at the same time).
WDYT? Any idea about how to do the "mouse-over" feature? Anyone interested by this topic?
Thanks
-Vincent