xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

by Paul Libbrecht

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

14 years, 2 months

[xwiki-devs] [proposal] Promote xwiki-reporting-tool out of the sandbox and start sending periodic reports.

by Caleb James DeLisle

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

14 years, 2 months

Re: [xwiki-devs] [xwiki-notifications] r32928 - platform/skins/trunk/colibri/src/main/resources/colibri

by Ecaterina Moraru (Valica)

Marius please revert this commit because ie-all means IE6, IE7 and IE8. * hacks are supposed to go for the IE6, IE7 part, while the non-affected property goes for IE8. for example: .xwikiintracontent legend { margin: -5px 0 5px 0; - *margin: 5px 0 10px -7px; + margin: 5px 0 10px -7px; } even if you made this clean - you supposed to delete the overridden margin property, but all these properties are needed to display correctly. Thanks, Caty On Wed, Nov 17, 2010 at 09:52, mflorea <platform-notifications(a)xwiki.org>wrote: > Author: mflorea > Date: 2010-11-17 08:52:49 +0100 (Wed, 17 Nov 2010) > New Revision: 32928 > > Modified: > platform/skins/trunk/colibri/src/main/resources/colibri/ie-all.css > Log: > XSCOLIBRI-251: ie-all.css uses color theme variables without importing the > color theme template > * Also removed useless * hack since it's a IE dedicated stylesheet. > > > Modified: > platform/skins/trunk/colibri/src/main/resources/colibri/ie-all.css > =================================================================== > --- platform/skins/trunk/colibri/src/main/resources/colibri/ie-all.css > 2010-11-17 07:43:03 UTC (rev 32927) > +++ platform/skins/trunk/colibri/src/main/resources/colibri/ie-all.css > 2010-11-17 07:52:49 UTC (rev 32928) > @@ -1,3 +1,4 @@ > +#template('colorThemeInit.vm') > body { > behavior: url("$xwiki.getSkinFile('/htc/csshover3.htc')"); > } > @@ -7,7 +8,7 @@ > } > > #docextrapanes { > - *display: inline-block; > + display: inline-block; > } > > .minwidth, .minwidthb, .minwidthc, .minwidthd { > @@ -29,7 +30,7 @@ > > .xwikiintracontent legend { > margin: -5px 0 5px 0; > - *margin: 5px 0 10px -7px; > + margin: 5px 0 10px -7px; > } > > #commentscontent #AddComment .commentcontainer label { > @@ -37,7 +38,7 @@ > } > > input.button { > - *padding: 0 0 1px; > + padding: 0 0 1px; > } > > fieldset.xwikimessage { > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications >

14 years, 2 months

[xwiki-devs] maven error when trying to write my own component

by Mark Wallace

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"?> <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>  </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>  </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

14 years, 2 months

[xwiki-devs] [VOTE] Release Cycles (a.k.a Major Releases)

by Vincent Massol

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

14 years, 2 months

[xwiki-devs] Using XInclude for parsing XAR documents?

by Paul Libbrecht

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

14 years, 2 months

[xwiki-devs] [ANN] XWiki Enterprise 2.6 RC2 Released

by Vincent Massol

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

14 years, 2 months

[xwiki-devs] [VOTE] Make XE 2.7 the last minor release of the 2.x cycle

by Vincent Massol

Hi devs, Now that we've agreed to have major release cycles we need to define what we do for the current cycle (see http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HRelease…). I'm proposing here to make XE 2.7 the last minor release of the 2.x cycle. Here's my +1 Thanks -Vincent

14 years, 2 months

[xwiki-devs] [Test] XE 2.6 RC2 Ready for testing

by Vincent Massol

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

14 years, 2 months

[xwiki-devs] [Proposal] Add xwiki-archetype-component module in tools

by Vincent Massol

Hi, I'm planning to add a xwiki-archetype-component module in tools, in the same manner that we have a xwiki-archetype-macro module. Thanks -Vincent

14 years, 2 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