xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [VOTE] Change our default Connection Pooling framework for Hibernate to BoneCP

by Vincent Massol

Hi devs, I was trying to make XEM work with HSQLDB and... I have succeeded :) The only problem I have is that DBCP doesn't seem to work with Hibernate. For some weird reasons when we do a SET SCHEMA it makes calls to fail afterwards. In any case if I configure Hibernate to not use DBCP all work just fine. I've googled around and found that there are lots of people complaining about DBCP. I've googled for what connection pooling library to use and I've found that most people are recommending BoneCP (http://jolbox.com/). See: * http://stackoverflow.com/questions/5640146/java-jdbc-connection-pool-librar… * http://www.jorambarrez.be/blog/2012/04/30/dbcp_vs_c3p0_bonecp/ * http://stackoverflow.com/questions/8057110/java-database-connection-pool-bo… The other thing is that we currently have some 300 line of code that we shouldn't have at all and that we need in XWiki just for handling DBCP (see com.xpn.xwiki.store.DBCPConnectionProvider). The pro of BoneCP is that it seems to be the fastest, see http://jolbox.com/benchmarks.html So here's what I'd like to propose: * We move DBCPConnectionProvider to a legacy module * We bundle the bonecp jar by default * We configure our hibernate.cfg.xml by default to use boneCP: <property name="bonecp.idleMaxAge">240</property> <property name="bonecp.idleConnectionTestPeriod">60</property> <property name="bonecp.partitionCount">3</property> <property name="bonecp.acquireIncrement">10</property> <property name="bonecp.maxConnectionsPerPartition">60</property> <property name="bonecp.minConnectionsPerPartition">20</property> <property name="bonecp.statementsCacheSize">50</property> <property name="bonecp.releaseHelperThreads">3</property> <property name="connection.provider_class">com.jolbox.bonecp.provider.BoneCPConnectionProvider</property> What this means: * Existing users of XWiki will not have to change anything, it'll still work * New users will use bonecp without knowing * Existing users can migrate to bonecp just by changing one line in their hibernate.cfg.xml file I'd love to do this for 4.3 but we're already quite advanced in the 4.x cycle. That said it's just a one line change in hibernate.cfg.xml in case of problem to go back to DBCP so we could do this for 4.3 which leaves us 4.3, 4.4 and 4.5 to test this out. And if later on we find an issue we'll always be able to release a 4.5.1 that has this one line change to go back to DBCP. WDYT? Here's my +1 for this action plan. Thanks -Vincent

12 years, 3 months

[xwiki-devs] [VOTE] Modify the ReleaseNotes page to have Release Notes for the whole platform

by Vincent Massol

Hi devs, Current situation: * on http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ we have separated the RN into 2 parts: XE and XEM. * in the RN for XE we put all platform release notes, even release notes for modules in platform that are not bundled with XE (IRC Bot for ex). * It's normal to have release notes for everything we release, not just XE or XEM Proposal: * Have only a single release note page for each release (ie no more specific XEM release notes + always make sure to document all releases modules in the RN, not just what is bundled with XE). I propose to name this "XWiki" instead of "XWiki Enterprise". So we would have "XWiki 4.3" for ex. * The URL for 4.3M1 would be (for ex): http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki43M1 I propose to do this ASAP for 4.2 final (I can do the refactoring). Here's my +1 Thanks -Vincent

12 years, 3 months

[xwiki-devs] [VOTE] Unit tests must not output anything on the console

by Vincent Massol

Hi devs, It's a best practice that unit tests must not output anything to the console. Rationale: * It pollutes the maven logs unnecessarily. For example imagine that you're expecting an error in your test and that the stacktrace is logged to the console. When looking at the maven console logs the reader will wonder if there was an error or if it was expected. * The test must assert whatever it needs to validate the code under test. So if it expects a log to be printed it should assert it. In order to make this easy I've just added JUnit LogRule to our commons test framework. Here's a usage example: public class RestrictParseLocationEventHandlerTest { private RestrictParseLocationEventHandler handler = new RestrictParseLocationEventHandler(); /** * Capture logs with WARN or higher severity to assert them. */ @Rule public LogRule logRule = new LogRule() {{ record(LogLevel.WARN); recordLoggingForType(RestrictParseLocationEventHandler.class); }}; @Test public void includeEventWhenIllegalPath() { Assert.assertNull("Template shouldn't have been returned", this.handler.includeEvent("../WEB-INF/xwiki.cfg", "xwiki:Main.WebHome", "parse")); Assert.assertEquals(1, this.logRule.size()); Assert.assertTrue(this.logRule.contains( "Direct access to template file [/WEB-INF/xwiki.cfg] refused. Possible break-in attempt!")); } } So this is a vote to agree on this best practice and to document it on dev.xwiki.org. Here's my +1 If you agree then please make sure your tests don't output anything from now on and please try fixing the tests you wrote that do... Thanks -Vincent

12 years, 3 months

Re: [xwiki-devs] [xwiki-users] How to track user activity?

by Ezequiel Scott

Hi All, Thanks for the response. Activity Stream seems to be a great candidate for my purpose, but It doesn't log "view" events. However, I found it: http://jira.xwiki.org/browse/XWIKI-6450 I explored xwiki database scheme and I founded two tables: "xwikistatsvisit" and "activitystream_events". The first one, records view events, recording <user, ip, pages_viewed_counter, timestamp> but it doesn't save WHAT page. The second, records events <user, event, page, url, timestamp> but doesn't recognize VIEW as a event. Have any idea about how to merge this info by querys (if is possible)? Is possible append a column "page" or "url" to "xwikistatsvisits", so that I will see <user, timestamp, PAGE> ? Thanks! 2012/9/24 Sergiu Dumitriu <sergiu(a)xwiki.com> > On 09/20/2012 12:31 PM, Ezequiel Scott wrote: > >> 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!! >> >> > You can implement your own component [1] that listens [2] for action > events [3]. You could then see what's the current user [4] and the current > action [5] and do whatever you want with that information. > > [1] http://platform.xwiki.org/**xwiki/bin/DevGuide/**WritingComponents<http://platform.xwiki.org/xwiki/bin/DevGuide/WritingComponents> > [2] http://extensions.xwiki.org/**xwiki/bin/Extension/** > Observation+Module+Local<http://extensions.xwiki.org/xwiki/bin/Extension/Observation+Module+Local> > [3] https://github.com/xwiki/**xwiki-platform/blob/** > 489f4f7c2d3dd6255f8f8ea32ffe8f**d98c9e5b57/xwiki-platform-** > core/xwiki-platform-bridge/**src/main/java/org/xwiki/**bridge/event/** > ActionExecutedEvent.java<https://github.com/xwiki/xwiki-platform/blob/489f4f7c2d3dd6255f8f8ea32ffe8f…> > [4] https://github.com/xwiki/**xwiki-platform/blob/** > ff8bc0ee9f22f5e7f4ee0bab6d9437**f53e0b3f1f/xwiki-platform-** > core/xwiki-platform-bridge/**src/main/java/org/xwiki/** > bridge/DocumentAccessBridge.**java#L603<https://github.com/xwiki/xwiki-platform/blob/ff8bc0ee9f22f5e7f4ee0bab6d9437…> > [5] https://github.com/xwiki/**xwiki-platform/blob/** > 79ec59265415fd89a8b251abe447e0**8b76de1f02/xwiki-platform-** > core/xwiki-platform-bridge/**src/main/java/org/xwiki/**bridge/event/** > AbstractActionExecutionEvent.**java#L65<https://github.com/xwiki/xwiki-platform/blob/79ec59265415fd89a8b251abe447e0…> > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > > ______________________________**_________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/**mailman/listinfo/users<http://lists.xwiki.org/mailman/listinfo/users> > -- *Ezequiel Scott** * ezequielscott(a)gmail.com

12 years, 3 months

[xwiki-devs] [ANN] XWiki Enterprise and XWiki Enterprise Manager 4.2 Release Candidate 1 released

by Eduard Moraru

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

12 years, 3 months

[xwiki-devs] [Contrib] Open a project - DBListManager Application

by Guillaume "Louis-Marie" Delhumeau

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

12 years, 3 months

[xwiki-devs] Tracking user activity

by Ezequiel Scott

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

12 years, 3 months

[xwiki-devs] Running groovy code in the background

by Paul Libbrecht

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

12 years, 4 months

[xwiki-devs] Re : [Contrib] xwiki-application-mailarchive

by jeremie.bousquet＠gmail.com

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

12 years, 4 months

[xwiki-devs] Is solr ready yet?

by Jones, Dan

: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.

12 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs