Hello fellow developers,
there seems to be some magic in creating a new, simple, login page.
I tried making my own Main/Login with the usage of checkAuth in case the params are found but that seems not to work.
Should the form post to loginsubmit? To view?
Is there something "against me doing that" ?
XWiki.XWikiLogin sounds to have content generated by some magic I cannot edit.
thanks in advance
paul
I would like to get reports going out so that we can get a feel for the periodic reports, and work
out bugs and make improvements in real time.
I'm +1 to getting reports going.
A technical challenge is that unless one of the build agents has access to a mail relay, it will not
be able to send mail. If this is a problem, it can be fixed by signing up with an email service and
placing the password in a file on the filesystem of the agent which the job is bound to. The file
can be loaded by the configuration script.
Caleb
Hi all,
It's my first time trying to develop my own component per this page:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents
I ran the maven create component steps as follows:
C:\dev\xwiki\xwiki-enterprise-2.5-rc-1> mvn install:install-file
-Dfile="C:/Downloads/xwiki-archetype-component-1.0-SNAPSHOT.jar"
-DartifactId=xwiki-archetype-component
-DgroupId=com.xpn.xwiki.platform.tools -Dversion=1.0-SNAPSHOT
-Dpackaging=jar
. . .
C:\dev\xwiki\xwiki-enterprise-2.5-rc-1>mvn archetype:generate
-DarchetypeGroupId=com.xpn.xwiki.platform.tools
-DarchetypeArtifactId=xwiki-archetype-component
-DarchetypeVersion=1.0-SNAPSHOT
-DgroupId=com.modusoperandi.xwiki.extentions
-DartifactId=xwiki-marktest -Dpackage=com.modusoperandi.xwiki.ext
-Dversion=0.1 -Dpackaging=jar
. . .
Now I have an xwiki-marktest project.
Had to comment out the "1.8-SNAPSHOT" property value, making my pom.xml
look like this:
C:\dev\xwiki\xwiki-enterprise-2.5-rc-1\xwiki-marktest> type pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<!--
*
* See the NOTICE file distributed with this work for additional
. . .
*
--><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.
0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<artifactId>xwiki-enterprise-parent</artifactId>
<groupId>com.xpn.xwiki.products</groupId>
<version>2.5-rc-1</version>
</parent>
<groupId>com.modusoperandi.xwiki.extentions</groupId>
<artifactId>xwiki-marktest</artifactId>
<version>0.1</version>
<properties>
<!-- TODO: remove this if you inherit a project that has the core
version set
<platform.core.version>1.8-SNAPSHOT</platform.core.version>
-->
</properties>
<dependencies>
<dependency>
<groupId>org.xwiki.platform</groupId>
<artifactId>xwiki-core-component</artifactId>
<version>${platform.core.version}</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
<!-- Add here all your other dependencies -->
</dependencies>
</project>
But when I try to compile I get the "Failure to find..." error shown below.
C:\dev\xwiki\xwiki-enterprise-2.5-rc-1\xwiki-marktest>mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building xwiki-marktest 0.1
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 0.188s
[INFO] Finished at: Fri Nov 12 16:24:05 EST 2010
[INFO] Final Memory: 2M/254M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal on project xwiki-marktest: Could not
resolve dependencies for project
com.modusoperandi.xwiki.extentions:xwiki-marktest:jar:0.1:
Failure to find org.xwiki.platform:xwiki-core-component:jar:2.5-rc-1
in http://maven.xwiki.org/externals was cached in the local
repository, resolution will not
be reattempted until the update interval of xwiki-externals has
elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible
solutions, please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExcept…
C:\dev\xwiki\xwiki-enterprise-2.5-rc-1\xwiki-marktest>
What do I do now?? Any help would be greatly appreciated.
-Mark
Hi committers,
I've started a thread recently on this list about the Roadmap leading to the 3.0 release. The outcome of this thread is that we need a global strategy for our major releases (e.g. the "2" in the "2.N" releases).
First here's the rationale for doing major releases:
* It's a way to mark progress to the outside world and to be able to do open source marketing
* It's a milestone in the project's life and it feels good to do it. It makes us developers feel proud of our achievements too.
* It allows us to move forward since it's a good time to think back about what the xwiki project is and where it wants to go
I've tried to capture all arguments from the past discussion to come up with a Release Cycle strategy that take them into account without changing our core values which is to do timeboxing (rather than featuritis).
So here goes the proposal:
1) Introduce the notion of "Release Cycle".
- A release cycle means all the release of the type X.N where X is the major and represent the cycle (and N is a non constrained number 0 <= N < infinity)
- Duration: 6 minor releases (e.g. 2.0 till 2.5). That's approximatively 1 year since each minor release is about 2.5 months. <fun>For the geeks in us, six is a unitary perfect number, a harmonic divisor number and a highly composite number (see http://en.wikipedia.org/wiki/6_(number)).</fun>
2) When we release the last minor of the cycle we announce it:
- Send mail mentioning that the cycle is over and that version X.N is the last minor release of that cycle (but there can still be bugfix releases: X.N.P)
- In that mail, explain all the major features that were implemented during that release cycle (make a special Release Notes for a Cycle)
Advantages:
* Users are satisfied since it means X.0 is the first release of a cycle (this was one of the major comment in our past discussion thread)
* For developers, we have a notion of "work done", ie when a cycle is over.
* We have 2 points of communication:
** When a cycle is finished (with the last minor release of the cycle)
** When a new cycle begins (to describe the rough directions of the new cycle and internally to decide where the project is heading)
Note: The rule about 6 minor releases is really important for several reasons:
* It implements timeboxing our core tenet regarding releases
* It allows us to not have to rediscuss when is the major going to happen every time
* It allows us to know well in advance when the major release is going to happen and thus to adjust our commits during the whole cycle
* It prevents featuritis
Note 2: Having rule doesn't mean we'll never have good reasons to do things differently. It may happen that from time to time we need one more release for a cycle for example but this will be treated as an exception and will need to be justified. What's important is to have defined rules in order to give a stable rythm to the dev process.
Here's my +1.
Thanks
-Vincent
Hello fellow developers,
in order for the current source file to be a real source file outside of the XML of the xar, e.g. a .properties, a .vm, a .groovy, it would be enough to enable XInclude on the parser that reads the XML document.
Which source should I look into?
Also, where for xwiki 1.5?
thanks in advance
paul
The XWiki development team is pleased to announce the release of XWiki Enterprise 2.6 RC2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
Changes from 2.5:
• Revamped Recent Activity Dashboard, which is now called Activity Stream
• Share page by mail feature
• Icon/Emoticon Support
• Auto linking of WikiWords
• New Recent Activity Macro
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise26RC2
Thanks
-The XWiki dev team
Hi guys,
If you can please test XE 2.6 RC2:
http://maven.xwiki.org/releases/org/xwiki/enterprise/
Once I get a few confirmations that it works well, I'll finish the release
and publish it.
Thanks for your help!
-Vincent
Acting Release Manager for XE 2.6 RC2
Hi devs !
I thought about adding some changes in Events and Activity Stream.
First of all, I want to remove all the listeners from Activity Stream
and make this class listen to AllEvent, making it capable of cathcing
all events that occur in the wiki (and this way, when adding a new
event, you wouldn't need any modifications to this class in order to
catch it).
Secondly, I would like to modify onEvent function in the class so that
it uses the simpleClassName of the event occurred in order to log the
event (the eventType would be this simpleClassName...for example
DocumentSavedEvent, AnnotationAddedEvent and so on).
And thirdly i thought about adding one field in AbstractFilterableEvent
called /identifier/ and make all events extend directly this class. And
that /identifier/ would be used in a different way by the events
themselves. But it would be used to retrieve infos about that events.
And so, when logging an event, we could use classname + identifier.
For example
AnnotationAddedEvent + "This is my annotation" .
CommentAddedEvent + "This is my comment" or the number of the comment.
WDYT ?
Stefan
Hi,
On Nov 12, 2010, at 2:19 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2010-11-12 02:19:09 +0100 (Fri, 12 Nov 2010)
> New Revision: 32741
>
> Modified:
> platform/web/trunk/standard/src/main/webapp/templates/menuview.vm
> Log:
> XE-750: Ability to send a link to a page by email
> Enabled the Share menu entry in non-Colibri skins
>
> Modified: platform/web/trunk/standard/src/main/webapp/templates/menuview.vm
> ===================================================================
> --- platform/web/trunk/standard/src/main/webapp/templates/menuview.vm 2010-11-12 01:14:31 UTC (rev 32740)
> +++ platform/web/trunk/standard/src/main/webapp/templates/menuview.vm 2010-11-12 01:19:09 UTC (rev 32741)
> @@ -136,6 +136,10 @@
> #if($canImport)
> #submenuitem($xwiki.getURL('XWiki.OfficeImporter', 'view') $msg.get('core.menu.create.pageFromOffice') 'tmActionImport')
> #end
> + #if (!$isGuest)
> + #submenuitem($doc.getURL('view', 'viewer=share') $msg.get('core.menu.share') 'tmActionShare', '')
> + $xwiki.jsx.use('XWiki.SharePage')
> + #end
Again the share this page should be an extension of the platform and thus the menu entry should be there only if the share application (or whatever app it's included with) is available.
WDYT?
Thanks
-Vincent
> #xwikitopmenuentryend()
> #if($canDelete && $keyboardShortcutsEnabled)
> <script type="text/javascript">
Hi,
I've worked on a livetable generator and livetable macro which allows to
generate the livetable configuration directly from the XWiki class.
http://code.xwiki.org/xwiki/bin/view/Macros/LiveTableMacro20Macro
It would be great if some devs could look at it, as it could be a good
candidate for inclusion in the platform as it would ease creating
livetables.
The current problematic parts are:
1/ A hack was made for translations as changes to the livetable macros
were necessary to allow to use the Pretty Names automatically instead of
translations
2/ It would be great to not even have to give the fields to use in the
LiveTable and use the information from the class where a checkbox could
be added for each field saying "include in default livetable"
This would be a good step towards full CRUD in XWiki. Now that we have
Templates, we could add a place in the Wiki where all documents can be
browser per class (using this livetable). We would just need a slightly
simpler Class Editor which hide the more difficult configurations from
classes.
The more important work is to support Class Sheets that don't need the
include macro to be used for documents that have an object of this
class, and a modification of the inline mode which could disappear.
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
On Nov 11, 2010, at 8:25 PM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2010-11-11 20:25:14 +0100 (Thu, 11 Nov 2010)
> New Revision: 32725
>
> Added:
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/ExternalServletURLFactory.java
> Log:
> XWIKI-5681: New URLFactory that always generates external URLs
> Done.
>
> Added: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/ExternalServletURLFactory.java
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/ExternalServletURLFactory.java (rev 0)
> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/ExternalServletURLFactory.java 2010-11-11 19:25:14 UTC (rev 32725)
> @@ -0,0 +1,55 @@
> +/*
> + * See the NOTICE file distributed with this work for additional
> + * information regarding copyright ownership.
> + *
> + * This is free software; you can redistribute it and/or modify it
> + * under the terms of the GNU Lesser General Public License as
> + * published by the Free Software Foundation; either version 2.1 of
> + * the License, or (at your option) any later version.
> + *
> + * This software is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * Lesser General Public License for more details.
> + *
> + * You should have received a copy of the GNU Lesser General Public
> + * License along with this software; if not, write to the Free
> + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
> + * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
> + *
> + */
> +package com.xpn.xwiki.web;
> +
> +import java.net.URL;
> +
> +import com.xpn.xwiki.XWikiContext;
> +
> +/**
> + * URL Factory which always prints the absolute (external) form of URLs.
> + *
> + * @version $Id$
Missing @since tags.
Thanks
-Vincent
[snip]
Hi XWiki Devs,
I've been performing some XWiki demos recently and it came to my attention
that when adding a comment to a page and then going back to the homepage, my
comments didn't show up in the recent activity section of the dashboard.
This is due to the fact that adding a comment is considered a minor event.
This behavior is still taking place in the most recent versions of XWiki
Enterprise (I tested a XE 2.7 snapshot this morning). I believe that
comments should be treated as major events, the same way that adding an
object or an annotation to a page is.
Therefore I propose making adding a comment a major event instead of a minor
one.
Here's my +1 for this.
Thanks,
Guillaume
Apology for cross posting.
Can someone point me to where in the XWiki code I could implement an
extended XWiki link syntax? E.g. if I'd like to handle something like
this:
Berlin is a city in [[locatedIn::Germany>>Germany]]
where I'm adding the double-colon syntax before the usual link info.
--
Mark Wallace
Principal Engineer, Semantic Applications
Modus Operandi, Melbourne, FL, USA
Hi all,
In order to allow XWikiAttachment to reference data in multiple places, we need XWikiAttachment to
know the location of it's content. XWikiAttachmentContent uses an id which is identical to the
XWikiAttachment id meaning XWikiAttachmentContent has no id of it's own, only a foreign key which
points to the content.
To remedy this I propose the addition of a UUID hibernate UserType. This type will store a UUID as a
16 byte VARBINARY entry (little endian encoding) in order to minimize the size and database load.
Note: I discovered that a UUID type was added in a later version of hibernate so when we upgrade we
can decide whether to begin using their implementation.
I would like to add the UUID type as the first class in a new module xwiki-store (in a submodule
called xwiki-store-hibernate).
I think the best approach is to add new database code to xwiki-store slowly until eventually the
storage drivers in the core are no longer used thus "moving a mountain one shovel full at a time".
The UUID implementation:
http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-store/xwiki-store-…
How it works:
Add this to the xwiki.hbm.xml where you want to add a UUID:
<property name="contentUUID" type="org.xwiki.store.hibernate.types.UUIDToBinaryType">
<column name="contentuuid" />
</property>
(type can be mapped to a shorter name such as "UUID")
Add this to the bean class:
public UUID getContentUUID()
public void setContentUUID(final UUID contentUUID)
Hibernate takes care of the rest.
WDYT?
Caleb
Sergiu,
You are in charge of the email this page feature for 2.6. Is there a
design page for it ? I wanted to suggest some additional functionnality
to that feature if you have time for it.
When sending the page or when saving (the email this page feature could
be just under the save button), the user would have the ability to ask
for an automatic email this page on every change (content and comments).
The user would be able to say:
[ ] All Contributors
Additional users or groups: [ ]
Additional manual emails: [ ]
[ ] email all changes
Then automatically the email this page would be activated on each change.
A required feature would be an exclude list and a way for the user to
unsubscribe.
Finally we could add an email box so that we can load comments sent as a
reply to an email sent by the wiki.
The rationale for this feature is that when working on a document that
requires some discussion and validation, the email discussion is not
captured and the changes in the wiki are not triggering a fast enough
reaction thus slowing down the discussion around the document (I know
the Watch List exists, but since it requires manual subscription, most
participants won't do it and the speed of notification of the watch list
is not fast enough for discussion).
WDYT ?
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
We planned the mail to page feature for XE 2.6 and Sergiu won't be able to commit it before Monday 8th. We also need to fix several critical issues found in RC1:
- import wiki macros in XAR when wiki is empty
- XWikiGuest in recent activity
- security issue re XWikiGuest
- first time display which shows the user as logged out
Thus I'm proposing to postpone the release to the 11th. We'll need to start the release on the 11th morning sharp or we won't have time to do any more work before the final release in case we find some blockers.
Here's my +1
Thanks
-Vincent
Hi Caleb,
Nice start. Some questions/feedback:
* Is this replacing the standard hudson emails or does it come as an additional report? When is it sent?
* I'd like to see an email whenever someone commits something that makes one of the modules fail to build and in that mail the title should be short and explicit about whom has made the build fail + the mail should contain the log of the failure (in order to understand why it fails directly from the email).
IMO in general we need:
* less emails from hudson (only mails when builds are failing IMO, not needed when they're not)
* separate flickering from non flickering
* shorter email titles
* know how broke the build in the email and very visible
* console logs in the mail (not the full log, just the module that fails to build and only the part around the failure: let's say the last 100 lines)
Thanks
-Vincent
On Nov 9, 2010, at 4:02 AM, Caleb James DeLisle wrote:
> Trying out a new test reporter, tell me what you think.
>
> Statistics Report:
> 22 tests failed out of a total of 3026
> The total time taken to run the tests was 1853.3518 seconds,
> and the average time taken by a test was 0.6124758 seconds.
> The fastest test ran in 0.0 seconds,a record held by
> http://hudson.xwiki.org/job/concerto/org.xwiki.contrib.concerto$xwoot-conte…
> The slowest test ran in 120.414 seconds,and that one was
> http://hudson.xwiki.org/job/concerto/org.xwiki.contrib.concerto$jxta/5/test…
> and the average speed of a webstandards test (a good indication of page load speed) was 0.0 seconds.
> -------------------------------------------------------------------------------
> Detailed Failure Report:
> 0 Regressions,
> 0 Tests are Probably Flickering,
> 22 Failures
> -------------------------------------------------------------------------------
>
> Failures:
> These tests have failed multiple times in a row.
>
> Failing for the past 164 builds.
> Name: Blog/Archive.xml [month, year, comment, space, language] testParametersInColibri
> Details: Escaping test failed. * Parameter: "year" Tested file: Blog/Archive.xml URL:
> http://127.0.0.1:8080/xwiki/bin/view/Blog/Archive?skin=colibri&year=aaa%22b…
> List of validation errors: line 305 column 133 WARNING: Macro execution exception in the
> response. line 531 column 0 WARNING: Possible SQL error trace. line 563 column 0
> WARNING: Possible SQL error trace.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: Blog/CreatePost.xml [category, comment, entrySpace, form_token, language, entryTitle]
> testParametersInColibri
> Details: Escaping test failed. * Parameter: "entrySpace" Tested file: Blog/CreatePost.xml URL:
> http://127.0.0.1:8080/xwiki/bin/view/Blog/CreatePost?skin=colibri&entrySpac…
> List of validation errors: line 308 column 62 ERROR: Unescaped < character line 308
> column 58 ERROR: Unescaped > character * Parameter: "entryTitle" Tested file:
> Blog/CreatePost.xml URL:
> http://127.0.0.1:8080/xwiki/bin/view/Blog/CreatePost?skin=colibri&entryTitl…
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: Panels/PanelWizard.xml [forceLeftPanels, section, queryString, place, forceRightPanels,
> comment, space, language] testParametersInColibri
> Details: Escaping test failed. * Parameter: "place" Tested file: Panels/PanelWizard.xml URL:
> http://127.0.0.1:8080/xwiki/bin/view/Panels/PanelWizard?skin=colibri&place=…
> List of validation errors: line 341 column 95 ERROR: Unescaped < character line 341
> column 91 ERROR: Unescaped > character
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: XWiki/ExtensionManager.xml [extensionid, actioninstall, actionresolve, confirm,
> extensionversion, comment, actionuninstall, language, editor] testParametersInColibri
> Details: Escaping test failed. * Parameter: "actioninstall" Tested file:
> XWiki/ExtensionManager.xml URL:
> http://127.0.0.1:8080/xwiki/bin/view/XWiki/ExtensionManager?skin=colibri&ac…
> List of validation errors: line 321 column 140 WARNING: Macro execution exception in the
> response. * Parameter: "actionresolve" Tested file: XWiki/ExtensionManager.xml URL:
> http://127.0.0.1:8080/xwiki/bin/view/XWiki/ExtensionManager?skin=colibri&ac…
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: XWiki/LiveTableResults.xml [classname, orphaned, collist, comment, space, language]
> testParametersInColibri
> Details: Escaping test failed. * Parameter: "classname" Tested file: XWiki/LiveTableResults.xml
> URL:
> http://127.0.0.1:8080/xwiki/bin/view/XWiki/LiveTableResults?classname=aaa%2…
> List of validation errors: line 304 column 133 WARNING: Macro execution exception in the
> response. line 408 column 0 WARNING: Possible SQL error trace. line 423 column 0
> WARNING: Possible SQL error trace. * Parameter: "space" Tested file: XWiki/LiveTab
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: testClassEditor
> Details: Escaping test for XWIKI-5404 failed. Tested file: templates/editclass.vm URL:
> http://127.0.0.1:8080/xwiki/bin/edit/aaa%22bbb%27ccc%3Eddd%3Ceee/aaa%22bbb%…
> List of validation errors: line 332 column 71 WARNING: Unescaped ' character line 336
> column 77 WARNING: Unescaped ' character line 338 column 78 WARNING: Unescaped ' character
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: templates/editattachments.vm [] testPageEscaping
> Details: Escaping test for page name failed. Tested file: templates/editattachments.vm URL:
> http://127.0.0.1:8080/xwiki/bin/view/Main/aaa%22bbb%27ccc%3Eddd%3Ceee?skin=…
> List of validation errors: line 1 column 42 ERROR: Unescaped < character line 1
> column 38 ERROR: Unescaped > character
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: templates/editgroup.vm [classname] testPageEscaping
> Details: Escaping test for page name failed. Tested file: templates/editgroup.vm URL:
> http://127.0.0.1:8080/xwiki/bin/view/Main/aaa%22bbb%27ccc%3Eddd%3Ceee?skin=…
> List of validation errors: line 0 column 0 WARNING: Unexpected empty response
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: templates/editgroup.vm [classname] testParameterEscaping
> Details: Escaping test failed. * Parameter: "classname" Tested file: templates/editgroup.vm URL:
> http://127.0.0.1:8080/xwiki/bin/view/Main/WebHome?classname=aaa%22bbb%27ccc…
> List of validation errors: line 0 column 0 WARNING: Unexpected empty response
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 164 builds.
> Name: templates/editgroup.vm [classname] testSpaceEscaping
> Details: Escaping test for space name failed. Tested file: templates/editgroup.vm URL:
> http://127.0.0.1:8080/xwiki/bin/view/aaa%22bbb%27ccc%3Eddd%3Ceee/WebHome?sk…
> List of validation errors: line 0 column 0 WARNING: Unexpected empty response
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 177 builds.
> Name: testDocumentCacheSync
> Details: null expected:<[modified ]content> but was:<[]content>
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 177 builds.
> Name: testDocumentCacheSyncForAttachments
> Details: Name: PUT URI:
> http://localhost:8081/xwiki/rest/wikis/xwiki/spaces/Test/pages/AttachementC…
> Status code: 404 Status text: Not Found Response: <html> <head> <title>Status page</title>
> </head> <body> <h3>The server has not found anything matching the request URI</h3><p>You can get
> technical details <a
> href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5">here</a>.<br> Please
> continue your visit at our <a href="/">home page</a>. </p> </body> </html>
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 177 builds.
> Name: org.xwiki.test.ui.AllTests
> Details: Failed to connect to binary FirefoxBinary(/home/hudsonagent/firefox/firefox) on port 7055;
> process output follows: Error: cannot open display: :1.0 System info: os.name: 'Linux', os.arch:
> 'i386', os.version: '2.6.27.10-grsec-xxxx-grs-ipv4-64', java.version: '1.5.0_15' Driver info:
> driver.version: firefox
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 177 builds.
> Name: org.xwiki.test.ui.AllTests
> Details: Failed to connect to binary FirefoxBinary(/home/hudsonagent/firefox/firefox) on port 7055;
> process output follows: Error: cannot open display: :1.0 System info: os.name: 'Linux', os.arch:
> 'i386', os.version: '2.6.27.10-grsec-xxxx-grs-ipv4-64', java.version: '1.5.0_15' Driver info:
> driver.version: firefox
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 177 builds.
> Name: WYSIWYG Selenium Tests
> Details: Could not start Selenium session: Failed to start new browser session: Error while
> launching browser
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 180 builds.
> Name: junit.framework.TestSuite@6b3fc7
> Details: Could not start Selenium session: Failed to start new browser session: Error while
> launching browser
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 180 builds.
> Name: junit.framework.TestSuite@1d85f79
> Details: Could not start Selenium session: Failed to start new browser session: Error while
> launching browser
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests/org.xwiki.enterp…
>
> Failing for the past 828 builds.
> Name: Validating Dutch Web Guidelines validity for: space=Main, page=WebHome executed with
> credentials Admin:admin
> Details: Validation errors in space=Main, page=WebHome ERROR: At least one style attribute has been
> found on the page.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests/org.xwik…
>
> Failing for the past 828 builds.
> Name: Validating Dutch Web Guidelines validity for: space=WikiManager, page=CreateNewWiki executed
> with credentials Admin:admin
> Details: Validation errors in space=WikiManager, page=CreateNewWiki ERROR: An input field has been
> found with no label association.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests/org.xwik…
>
> Failing for the past 828 builds.
> Name: Validating Dutch Web Guidelines validity for: space=Main, page=WebHome executed with
> credentials Admin:admin
> Details: Validation errors in space=Main, page=WebHome ERROR: At least one style attribute has been
> found on the page.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests/org.xwik…
>
> Failing for the past 828 builds.
> Name: Validating Dutch Web Guidelines validity for: space=Main, page=WebHome executed with
> credentials Admin:admin
> Details: Validation errors in space=Main, page=WebHome ERROR: At least one style attribute has been
> found on the page.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests/org.xwik…
>
> Failing for the past 839 builds.
> Name: junit.framework.TestSuite@2a4983
> Details: Could not start Selenium session: Failed to start new browser session: Error while
> launching browser
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests/org.xwik…
> -------------------------------------------------------------------------------
Hello,
I am working on http://jira.xwiki.org/jira/browse/XE-741 and I would
need a final list of macro and parameter names. These would be the
current namings:
Macro name:
* recentactivity
-> to be replaced with 'activity'
Parameter names:
* 'showRss' (boolean: false by default) - Whether to show activity
rss links or not.
-> to be replaced with 'rss'
* 'showMinor' (boolean: false by default): - Whether to show
modifications that create minor versions or not.
-> to be replaced with 'minor'
* 'tag' (comma separated list): - Comma separated list of tags to
display activity for.
-> to be replaced with 'tags'
* 'space' (comma separated list): - Comma separated list of spaces
to display the recent activity for.
-> to be replaced with 'spaces'
-> also remove 'recent' from the macro description
* 'space' (comma separated list): - Comma separated list of spaces
to display the recent activity for.
-> to be replaced with 'spaces'
-> also remove 'recent' from the macro description
* 'author' (comma separated list): - Comma separated list of authors
whose modifications to show.
-> to be replaced with 'authors'
* 'changesNb' (number: 30 by default): - Number of activity to show.
-> to replace the description with 'Number of pages to display the activity of.'
-> to be replaced with 'pages' or 'entries' or some other name that
would fit better; you are welcome to add naming proposals.
-> to replace '30' with '20', now that each entry (page) contains a
number of sub-entries (activity events) and there will be a way to
'show more' entries (Facebook style)
New macro parameters to be added:
* 'events' (number: 10 by default): - Number of events to show for
each page entry.
-> you are welcome to add naming proposals.
* 'modifications' (boolean: false by default) - Whether to show 'see
modifications' link on 'edited the page' events.
-> other naming proposals: 'diff', 'differences', 'actions'
Raluca.
>On Oct 20, 2010, at 4:05 PM, Anca Luca wrote:
>
>>Hi devs,
>>
>>I've been working on http://jira.xwiki.org/jira/browse/XE-721 and it's done on my local. This is the recent changes macro based on the current implementation (not the activity stream one), but the idea is that we'll rewrite it to display recent activity in the future. I will commit it for the moment, in the 2.6 trunk, as is, but I would like to discuss here the name of the macro and its parameters:
>>Macro name:
>>recentchanges, changes, activity, recentactivity
>+1 for "activity" to be in line with the upcoming recent activity feature
planned for 2.6.
>
>No need for "recent", "activity" is enough. It's about the activity of the wiki.
>>Parameters:
>>* rss link should be shown at the bottom of the changes table (boolean): showRss, rss
>+1 rss (default true)
>
>>* minor changes are shown or not (boolean, default false): showMinor, minor
>+1 minor
>
>>* shows "see modifications" link next to entries (boolean, default true): showDiff, showDifferences, diff, differences
>I don't like too much diff*
>What about "actions"? It's more than just the difference link, there could be
other actions, as in the {{spaces/}} macro for example.
>>* number of changes to show (number, 0 means "all", defaults to 30): changesNb, changesCount, number, count, limit
> +1 count
>
>>* tags of documents to show chages for (comma separated list): tag, tags
>+1 tags
>
>>* spaces of documents to show changes for (comma separated list): space, spaces
> +1 spaces
>
>>* authors of documents to show changes for (comma separated list): author, authors
>+1 authors
>
>Note that the types cannot be enforced since it's a wiki macro, I put them there just for orientation.
>I'd go for activity rss minor diff count tags spaces authors .
>
> Thanks -Vincent