Hi,
JIRA says XEM 1.0M1 should be released on 14th of June and 1.0M2 on
29th of June. Obviously JIRA is lying! :)
JV, you're the Release Manager for XEM. Could you please let us know
the new dates and update JIRA accordingly? (or remove any date if we
don't know...)
Thanks
-Vincent
I am a big proponent of the principles of this bug:
http://jira.xwiki.org/jira/browse/XWIKI-1021
I don't think the whole ID scheme currently used should be thrown out,
however, as it might break anyone with an existing XWiki installation
of any size (which I have).
I would like to see the following:
a) go ahead and use a hash of the name to find an initial ID
b) increment the number if necessary to ensure it's unique.
c) stay with that ID, period. Don't change it when something is renamed, etc.
I've been seeing some issues with renames where the name hash
collides, or all of the attachments associated with an ID aren't
updated correctly (so the attachments effectively "disappear"..)
There is no reason to keep the ID associated with a hash of the name,
as the initial lookup is almost always based on the document's name...
I think this is pretty important, especially with document renaming
now possible...
--
'Waste of a good apple' -Samwise Gamgee
Hi,
Just to inform you that I have released the following packages:
- XWiki Top Level POM in version 1
- XWiki Platform Tools in version 1.0
All using Maven2 (a first for XWiki ;)).
They are available in our new release repo at
http://maven.xwiki.org/releases/
Thanks
-Vincent
I've been told that the Google Docs functionality should be built as a
plugin, yet there is no documentation about building plugins for xwiki. I
need to start adding code to the build to test it, but I need to know how I
should go about it. Also, what was the decision regarding the migration to
JDK 1.5? I need to add some libs to the build that require it. The libs are
provided by google as source that is supposed to be built, and then the jars
imported, which I'm told Maven can handle... how? I'd like it if somebody
could take the time guide me through the process.
Thanks,
Radu
Sorry about all these failures. This is the first time we're doing
releases and the first run is always a bit chaotic. I'll get better.
Anyway, I have everything under control now and all should be fixed
and working by now ;)
Thanks
-Vincent
On Jul 5, 2007, at 2:40 PM, teamcity(a)xwiki.org wrote:
> Build XWiki Platform Tools::Maven2 #16 failing
> Agent: Default agent
> Build results: http://teamcity.xwiki.org/viewLog.html?
> buildId=481&buildTypeId=bt4
>
> Changes included (1 change)
> ====================================================
> Change 3824 by vmassol (1 file):
> Prepare for the XWiki Tools 1.0 release
>
> see more information about changed files: http://teamcity.xwiki.org/
> viewLog.html?tab=buildChangesDiv&buildId=481&buildTypeId=bt4
>
>
> ======================================================================
> ======
> Configure email notifications: http://teamcity.xwiki.org/
> profile.html?init=1#notifications
Updated my SVN this morning and got
Updated to revision 3814.
Macintosh:~/Desktop/xWiki Sandbox/SVN/trunks-users rhadoo$ mvn install
[INFO] Scanning for projects...
[INFO] snapshot com.xpn.xwiki.platform:xwiki:1-SNAPSHOT: checking for
updates from xwiki
[INFO] snapshot
com.xpn.xwiki.platform:xwiki-build-xar-handlers:1.0-SNAPSHOT: checking for
updates from xwiki
[INFO] snapshot
com.xpn.xwiki.platform:xwiki-build-tools:1.0-SNAPSHOT:checking for
updates from xwiki
[WARNING] POM for '
com.xpn.xwiki.platform:xwiki-build-xar-handlers:pom:1.0-SNAPSHOT' is
invalid. It will be ignored for artifact resolution. Reason: Failed to
validate POM
[WARNING] POM for '
com.xpn.xwiki.platform:xwiki-build-xar-handlers:pom:1.0-SNAPSHOT' is
invalid. It will be ignored for artifact resolution. Reason: Failed to
validate POM
[WARNING] POM for '
com.xpn.xwiki.platform:xwiki-build-xar-handlers:pom:1.0-SNAPSHOT' is
invalid. It will be ignored for artifact resolution. Reason: Failed to
validate POM
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: com.xpn.xwiki.platform:xwiki-web-standard
POM Location: /Users/rhadoo/Desktop/xWiki
Sandbox/SVN/trunks-users/xwiki-platform-web/standard/pom.xml
Validation Messages:
[0] 'dependencies.dependency.artifactId' with value '${
xwiki.db.jdbc.artifactId}' does not match a valid id pattern.
[1] 'dependencies.dependency.groupId' with value '${
xwiki.db.jdbc.groupId}' does not match a valid id pattern.
Reason: Failed to validate POM
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Jul 05 10:42:49 EEST 2007
[INFO] Final Memory: 2M/6M
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Jul 05 10:42:49 EEST 2007
[INFO] Final Memory: 2M/6M
[INFO]
------------------------------------------------------------------------
Can somebody please look into it?
Cheers,
Radu
Sorry for this but we actually need a third remote repository for
external dependencies...
I'm working on it and I've updated http://www.xwiki.org/xwiki/bin/
view/Community/Building to what you'll need to have (it'll be ready
within 1 hour).
Thanks and sorry
-Vincent
On Jul 4, 2007, at 11:07 AM, Vincent Massol wrote:
> Hi developers,
>
> In preparation for our upcoming releases using Maven2, I'm
> separating our maven repo into 2:
> - one for snapshots
> - one for releases
>
> This is required as I'd like then to sync our releases repo onto
> the maven central repo.
>
> This means that you need to modify your settings.xml file as
> described on:
> http://www.xwiki.org/xwiki/bin/view/Community/Building
>
> Thanks and sorry for the inconvenience
> -Vincent
>
Hi,
In preparation for the upcoming 1.1M3 release of XWiki Platform Core,
XWiki Panels App and XWiki Enterprise, I'd like to perform the
releases of the following modules:
- Version 1 of xwiki-platform/pom
- Version 1.0 of xwiki-platform/xwiki-tools/ for build-tools and
packager
Note: I'll create a JIRA project for XWiki platform tools before
doing the release.
Here's my +1
Thanks
-Vincent
Hello all,
What is $msg variable, and where can I read more about it? (is not in xwikivars.vm...) And how does $msg.get() works?
Please, I really need some help. I want to include support for languages in my datepicker and Sergiu told me to put the strings in ApplicationRessources.properties and now I'm trying to get them in a js file with $msg.get("core.datepicker.somethingdefinedbymehere"), but it seems that the server does not know how $msg is, but it knows who $xwiki, $context and all other are....
So please, please, I would like to know more about this variable or how to get the strings from ApplicatonRessources.
I'd really appreciate some help because I'm stuck on this....
Thank you very much,
Evelina
Hi developers,
In preparation for our upcoming releases using Maven2, I'm separating
our maven repo into 2:
- one for snapshots
- one for releases
This is required as I'd like then to sync our releases repo onto the
maven central repo.
This means that you need to modify your settings.xml file as
described on:
http://www.xwiki.org/xwiki/bin/view/Community/Building
Thanks and sorry for the inconvenience
-Vincent
Hi Sergiu and all committers,
On Jul 4, 2007, at 12:06 AM, Sergiu Dumitriu wrote:
> Author: sdumitriu
> Date: 2007-07-04 00:06:46 +0200 (Wed, 04 Jul 2007)
> New Revision: 3800
>
> Modified:
> xwiki-products/xwiki-enterprise/trunk/wiki/src/main/resources/
> XWiki/Treeview
> Log:
> Changing line endings from Win to Linux, as this is the default.
What's important is that each SVN is configured properly. We
shouldn't consider linux as the default. This is not a good practice
AFAIK. Everyone should use line ending for his platform but make sure
to configure his subversion client to use native line endings:
http://www.apache.org/dev/version-control.html#https-svn
You should put this in your subversion config file:
http://www.apache.org/dev/svn-eol-style.txt
See also http://svnbook.red-bean.com/en/1.0/svn-book.html#svn-ch-7-
sect-2.3.5
I've put that up at http://www.xwiki.org/xwiki/bin/view/Community/
DevelopmentPractices
Thanks
-Vincent
Hi Stephane,
Maybe a quick word of what this is so that others know? Maybe a
README dropped in there would be good too.
Thanks
-Vincent
On Jun 22, 2007, at 4:05 PM, St??phane Lauri??re wrote:
> Author: slauriere
> Date: 2007-06-22 16:05:06 +0200 (Fri, 22 Jun 2007)
> New Revision: 3720
>
> Added:
> xwiki-sandbox/org.xwiki.model/
> Log:
> Initial import.
Hi All
I am new to XWiki and want to set it up on my local workstation (using
MySQL as the DB) , then modify the code and re-build it. I have the copy
of the code taken from the following SVN
URL:(**svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki/trunk**)
.Please suggest the methods for the following:
1. Ant targets for building XWiki (in all the modes)
2. deploy targets for XWiki
3. Changes in the code for MySQL other than the db properties in the
hibernate config (if any).
4. any other suggestions/precautions
Thanks
Gaurav
Hi,
I've started doing the exercise of breaking up XWiki Enterprise (aka
the default wiki) into applications. Here's what I came up with:
- Administration Application
User and Group management, etc
- Blog Application
- Calendar Application
- Class Wizard Application
- Help Application
Wiki Syntax Sheet and potentially other pages to help the user with
his wiki.
- Navigation Application
All pages that make it easy to navigate in a Wiki.
Includes What's New, Orphaned Pages, All Docs, Space Index,
Dashboard, RSS feeds for new pages/modified pages/comments.
- Photo Album Application
- Presentation Application
- Search Application
- Tag Application
Of course there also some documents in the Enterprise wiki that don't
belong to an application as they are specific (for example the
Main.WebHome page).
I have created these components in JIRA for the http://jira.xwiki.org/
jira/browse/XE project. In the future the idea is to move these
applications in SVN (as it's currently done for the Panels and
Selenium applications) and to create separate JIRA project for them.
Have I missed an application? WDYT?
Thanks
-Vincent
I think this was because I had a wrong dependency defined in TeamCity
(the Web module wasn't depending on the platform POM one).
-Vincent
On Jul 3, 2007, at 10:01 AM, teamcity(a)xwiki.org wrote:
> Build XWiki Platform Web::Maven2 #44 failing
> Agent: Default agent
> Build results: http://teamcity.xwiki.org/viewLog.html?
> buildId=311&buildTypeId=bt7
>
> Changes included (1 change)
> ====================================================
> Change 3798 by vmassol (1 file):
> XWIKI-1417: Functional tests for all databases
> Patch submitted by Artem Melentev
> Reviewed by Vincent Massol (with minor modifications)
>
> see more information about changed files: http://teamcity.xwiki.org/
> viewLog.html?tab=buildChangesDiv&buildId=311&buildTypeId=bt7
>
>
> ======================================================================
> ======
> Configure email notifications: http://teamcity.xwiki.org/
> profile.html?init=1#notifications
Interesting discussion related to this commit below.
2 points:
1) I think application translations shouldn't go in XWiki main JAR
2) At the level of the wiki it's easy to imagine a document holding
the translations. However as we want each application (blog, search,
panels, etc) to be independant, we need a solution at the level of
each applications.
If we have a document for each application, it's going to be too
painful to have to register each page in the admin.
Thus I think a better solution would be to modify XWikiMessageTool to
automatically look for documents having a Translation object attached
to them and to use the content of that object to resource properties.
Only issue is that this Translation class has to exist in all wikis...
Any idea?
Thanks
-Vincent
On Jun 30, 2007, at 11:45 AM, Sergiu Dumitriu wrote:
> Author: sdumitriu
> Date: 2007-06-30 11:45:13 +0200 (Sat, 30 Jun 2007)
> New Revision: 3776
>
> Modified:
> xwiki-platform/core/trunk/src/main/resources/
> ApplicationResources.properties
> Log:
> XWIKI-918: Cleanup/refactor the ApplicationResources* files
> Panels.EditTranslation
>
>
>
> Modified: xwiki-platform/core/trunk/src/main/resources/
> ApplicationResources.properties
> ===================================================================
> --- xwiki-platform/core/trunk/src/main/resources/
> ApplicationResources.properties 2007-06-30 09:30:16 UTC (rev 3775)
> +++ xwiki-platform/core/trunk/src/main/resources/
> ApplicationResources.properties 2007-06-30 09:45:13 UTC (rev 3776)
> @@ -736,3 +736,11 @@
> core.delete.backlinksWarning=The following documents contain links
> to the current page:{0}After deleting this document, those links
> will point to an empty page.
> core.delete.confirm=The deletion of a document is not reversible.
> Are you sure you wish to continue?
> core.delete.confirmWithBacklinks=In addition, the deletion of a
> document is not reversible. Are you sure you wish to continue?
> +
> +panels.translation.title=Document translations
> +panels.translation.editingOriginal=You are editing the original
> document ({0}).
> +panels.translation.editingTranslation=You are editing the
> following translation: {0}.
> +panels.translation.originalLanguage=The original language of the
> document is <a href="{0}">{1}</a>.
> +panels.translation.translate=Translate this document in:
> +panels.translation.otherTranslations=Other translations:
> +panels.translation.existingTranslations=Existing translations:
>
>
>
> --
> You receive this message as a subscriber of the xwiki-
> commits(a)objectweb.org mailing list.
> To unsubscribe: mailto:xwiki-commits-unsubscribe@objectweb.org
> For general help: mailto:sympa@objectweb.org?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/
> wws
Hello all,
I wanted to update the xwiki pre 1.0 version I am using to the final 1.0
but first I have to patch it with the patch attached to XWIKI-865 to
make it work with the ldap server over SSL.
However there does not seem to have a source tarball available and I
don't see what I need to checkout from subversion to get the XWIKI_1_0
branch.
Can anyone give me a clue ?
Thanks,
Philippe
Hi,
I think we need an easy way for everyone to build only the product
he's working on. Thus I'd like to propose the creation of a new
svn:externals for the platform only and to move externals in a
specific dir:
/svnroot/xwiki
|_ externals/
|_ trunks-devs/
|_ trunks-users/
|_ trunks-platform-devs/
|_ trunks-platform-users/
This will achieve the following use cases:
Use case 1: I'm working on product XX and I'm not making any change
to the platform
- checkout just the product's trunk. For example /svnroot/xwiki/xwiki-
products/xwiki-watch/trunk
Use case 2: I'm working on both the platform and XWiki Enterprise but
not the other products
- checkout /svnroot/xwiki/externals/trunks-platform-devs/
- checkout XWiki Enterprise: /svnroot/xwiki/xwiki-products/xwiki-
enterprise/trunk
Caveat: you can't build both at the same time but you can build each
one with a single command.
Use case 3: I'm working on everything
- checkout /svnroot/xwiki/externals/trunks-devs/
Another option would be to create one externals per product but it's
a little bit of a pain to maintain. It's possible though. Actually
this would allow to fine tune the build to that only platform
components required for the product are built. For example, only the
plugin used by the product and only the applications built by the
product would be built. Actually this probably makes sense. In that
case we would have:
/svnroot/xwiki
|_ externals/
|_ trunks-devs/
|_ trunks-users/
|_ trunks-platform-devs/
|_ trunks-platform-users/
|_ trunks-enterprise-devs/
|_ trunks-enterprise-users/
|_ trunks-enterprise-manager-devs/
|_ trunks-enterprise-manager-users/
|_ trunks-watch-devs/
|_ trunks-watch-users/
|_ trunks-curriki-devs/
|_ trunks-curriki-users/
A last option would be to put the full platform under the same trunk/
but I don't think this is right as we should be able to release
platform modules separately.
WDYT?
Thanks
-Vincent
Hello,
AFAIK, XWiki APIs should be public wrappers around a hidden
full-fledged java object, which can only be accessed directly by PR
users. Certainly, this is not the case with plugins, which return the
inner Plugin object without any check.
I'd propose to change this method, so that it behaves as all the other
API classes, and checks for programming rights before returning this
object. Is there any reason why this change shouldn't be performed?
Sergiu
--
http://purl.org/net/sergiu
Hi,
As you've seen we have moved to Maven2 now and you might be wondering
how to quickly run XWiki Enterprise now. Here are some notes about
doing that:
http://www.xwiki.org/xwiki/bin/view/Community/
Building#HExecutingtheStandardWebWARquicklyindevelopmentmode
Thanks
-Vincent
Hello all,
I'm having the following problem in xwiki:
I have a document, which contains an input with autosuggest feature enabled. I create the document and I try to write something in the input but the query that should be executed is not, resulting in "Nothing found!" message for my suggest. If I SAVE the document and then edit it, and write something in the input, that query IS executed, and the suggest feature works fine.
I'm guessing that before being saved a document doesn't have the proper rights and that's why the query cannot be executed.
Any ideas what I should do in this case?
Thanks a lot for your help.
Evelina
On Jun 27, 2007, at 3:06 PM, Vincent Massol wrote:
> Author: vmassol
> Date: 2007-06-27 15:06:20 +0200 (Wed, 27 Jun 2007)
> New Revision: 3739
>
> Added:
> xwiki-products/curriki/trunk/plugins/
> xwiki-products/curriki/trunk/plugins/mimetype/
> xwiki-products/curriki/trunk/plugins/mimetype/src/
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> curriki/
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> curriki/xwiki/
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> curriki/xwiki/plugin/
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> curriki/xwiki/plugin/mimetype/
> Removed:
> xwiki-platform/web/trunk/gwt/src/main/resources/
> xwiki-products/curriki/trunk/gelcv1/gelcplugins/src/main/java/
> org/gelc/xwiki/plugins/mime/MimeType.java
> xwiki-products/curriki/trunk/gelcv1/gelcplugins/src/main/java/
> org/gelc/xwiki/plugins/mime/MimeTypePluginAPI.java
> Modified:
> xwiki-platform/web/trunk/gwt/pom.xml
> xwiki-platform/web/trunk/pom.xml
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> curriki/xwiki/plugin/mimetype/MimeType.java
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> curriki/xwiki/plugin/mimetype/MimeTypeConstant.java
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> curriki/xwiki/plugin/mimetype/MimeTypePlugin.java
> xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/
> curriki/xwiki/plugin/mimetype/MimeTypePluginAPI.java
> Log:
> CURRIKI-759: Create a Maven2 build
>
> * Fixed the build for xwiki-platform-web/gwt. It nows generates a
> JAR and a source JAR that can be depended upon by GWT modules doing
> the GWT compilation (Watch & Curriki for example).
> * I have added the GWT TK jar to our custom remote repo as I
> couldn't find it elsewhere
> * Removed some resource files in gwt/ module as I couldn't
> understand what they were for...
Ouch... The curriki/ commits were a mistake. I wasn't ready to commit
it them yet. It doesn't really matter though. Only thing is that
nobody has agreed yet to my previous email about the new package name
for plugins so this is jumping the gun a bit... :)
Let me know and I'll revert if necessary.
Thanks
-Vincent
Hi Curriki developers,
The Curriki build is still using Ant and it was calling the Ant build
script from XWiki core. However as I haven't put back an Ant build
for XWiki core the Curriki build is currently not working.
I'm proposing to update Curriki's build to use Maven2.
I'm proposing the following directory structure:
xwiki-product-curriki/
|_ gwt/
|_ web/
|_ wiki/
|_ plugins/
|_ asset/
|_ framework/
|_ license/
|_ metadata/
|_ mimetype/
|_ distribution/
where:
* gwt/ contains GWT Java sources that have to be compiled with GWT to
generate Java classes + JS files
* wiki/ contains the curriki wiki
* distribution/ contains a runnable version of curriki (equivalent to
the XWiki standalone distribution for XWiki Enterprise).
If that's ok with you I can start working on this as soon as tomorrow
morning. I think I need 1 day at most to get it to build again.
David, we can work on this together if you want. I'll probably have
question for you as I progress. It would be great if you could be on
IRC (irc.freenode.net, channel #xwiki) so that we can talk easily.
Thanks
-Vincent