Hello,
I'm currently reading about XWiki and XEclipse and would like to ask if
there is any consensus about XWiki pages templates which might also be
usable from XEclipse probably after some code hacking on its plugins.
I'm currently working on some project for my client (source code will be
contributed/available later in the project stage) where there is a need
to use XEclipse and enhance it to support some predefined
forms/templates for web pages creation. So far I've found just XWiki FAQ
tutorial on
http://platform.xwiki.org/xwiki/bin/view/DevGuide/FAQTutorial which
tries to deals with some kind of templates. However this looks quite
general at least so far to me and so I would like to ask the question
above about consensus where and how to go with templates in xwiki/xeclipse.
My current idea is to stick with the XWiki server as a provider of
templates to preserve ability to use templates from both browser and
xeclipse and to enhance xeclipse new page creation wizard to provide a
list of available templates on the server side...
Thanks for any idea where to start or where to look for more information
with regarding to this project task.
Karel
Hi,
According to the feedback received I've made another proposal for the
Application Within Minutes
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinM…
Changes:
- Wizard style creation
- Structure in a form editor style (drag&drop, refresh preview on change)
Remarks:
- "Create application" could be part of the action menu's "Add" submenu and
act as a wizard for the creation process.
As a result we will have a space for each application that will list on it's
homepage the entries livetable.
The structure will be changed by entering again the wizard.
Thanks,
Caty
References:
[Proposal][UX] Application Within Minutes - Proposal 1:
http://xwiki.markmail.org/thread/tvxnoabhbwfcpwmk
Hi dev,
I would like to introduce class property entity type and related
reference and syntax separator.
For the separator syntax I propose to use the same thing as object
separator since you can't have both in the same reference and it's
always a pain to find a new separator.
Note that I'm inly talking about class property and not class since
class reference is exactly the same thing as document reference I
don't think we really need to have a specific one.
WDYT ?
--
Thomas Mortagne
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The XWiki development team is proud to announce the release of XWiki Enterprise 3.1 Milestone 2.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This is the second and final milestone in the 3.1 development cycle, you can review the changes made
and bugs
fixed since 3.0 by going to:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris…
Thanks
- -The XWiki development team
If you would like to download the new release now, you can using these links:
- ---- XWiki Enterprise for Servers ----
xwiki-enterprise-web-3.1-milestone-2.war
SHA1: 1e903ab1bb230e6823597db2c6034ecd27a4275a
http://forge.ow2.org/project/download.php?group_id=170&file_id=16712
xwiki-enterprise-wiki-3.1-milestone-2.xar
SHA1: c82aa727bf6a81929d91c1e9182921eac9e0ea7e
http://forge.ow2.org/project/download.php?group_id=170&file_id=16713
- ---- XWiki Enterprise Standalone ----
xwiki-enterprise-installer-windows-3.1-milestone-2.exe
SHA1: 9f71d54eeff3b136454d15164e94b5484815ebf3
http://forge.ow2.org/project/download.php?group_id=170&file_id=16711
xwiki-enterprise-jetty-hsqldb-3.1-milestone-2.zip
SHA1: fa04ee328387ab48bbf5a8f5b2fab22e4684858e
http://forge.ow2.org/project/download.php?group_id=170&file_id=16719
xwiki-enterprise-installer-generic-3.1-milestone-2-standard.jar
SHA1: b93969196e73e30ffc6a65cd6033b03ebdfc1a85
http://forge.ow2.org/project/download.php?group_id=170&file_id=16710
- ---- XWiki Manager for Servers ----
xwiki-manager-web-3.1-milestone-2.war
SHA1: 12f514ddd2913378b07b8b43b5654dbb6ad33ed8
http://forge.ow2.org/project/download.php?group_id=170&file_id=16714
xwiki-manager-wiki-administrator-3.1-milestone-2.xar
SHA1: 9183f4f069c388ff9963e2ce877b6d75799fe4fa
http://forge.ow2.org/project/download.php?group_id=170&file_id=16716
- ---- XWiki Manager Standalone ----
xwiki-manager-jetty-mysql-3.1-milestone-2.zip
SHA1: 63a7d30511931fb10569fb4a82c5c42f367f9467
http://forge.ow2.org/project/download.php?group_id=170&file_id=16718
- ---- XWiki Manager Extension for XWiki Enterprise Installations ----
xwiki-manager-application-xem-3.1-milestone-2.xar
SHA1: d5381326b71057182256d6aa9eec777b647739aa
http://forge.ow2.org/project/download.php?group_id=170&file_id=16717
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQIcBAEBAgAGBQJN3LFoAAoJECYAmptlsgnWjikP/2dVAZyyWcFzh9paefuqwAXm
NDvW6VA/0nHVOhMhzlvyjjpBKW4tAujQqIT2eL9dn5SG2tCygQ6lLE7r6zwFJY0t
LHkOtqtK4lRiFJfu7+h/f3/yYRi3mKwht0d8z0lc74w+ACB6VKSfIdcIwh1u7Klm
UXNh43lbIJNABGYapGe/aLwr3q7qFZp+sKaO3aVW5cVVzup3KnQPHV9BqgRYfqDd
fWip1zZCixJ/yOOQ8VNpNRvr8mVST9pettKmDb6HlLjqvrV+qrX306zIvhcPFoKk
tkHZQJaFsf9Sg8pv+U+tBVgvJIcWbf+PeAJKhIU1MPz8wc54bvDGhqBpH1VwLGUD
8W8vhzPs4rnP/w5nKWz15R4KEPBHuzUMx6oEcwPx7G7L8f+tnlAifWJLzQJP1A1U
JTADeQ7GnIZ/Jg6ycWeDIIgZLOl6TrzEaDYMTWF6sXElvYfUilrdhJZ1Upbv2aul
R2bWqF7Ia//FQxMGNPhwTwF7fsPExJaFQ/OEeoSumusZIl/NGc4gjrytZA2VY2t0
c3zW2CAd8JryJujFuQtbj51rYvKMnDtp3+419pkfmbs5Vg33hFKrKB30xV7nrsm5
zN9itvj7APKy3tndUph2YXaNYlXkrAe2o1B6R8gXw0M8qV/0gVmL2G0DN5d3Vu6x
BG460gFTusnCwQXW8TYG
=XTgI
-----END PGP SIGNATURE-----
Hi devs,
Here's the situation:
* We've been having a hard time releasing on time and the main issue is test stability. We lag by at least a week and we even release with failing tests, causing regressions.
* It's not the role of the release manager to fix tests before releasing
* It's not normal that some people spend time fixing issues caused by others and that others continue to work on the next thing they are working on. Everyone needs to help.
Here's what I propose as a drastic and temporary measure till we get better:
1) It's forbidden to commit anything till all tests are passing (unit AND functional tests), unless what is committed is about fixing tests. On the exceptional case when a committer absolutely needs to commit even though tests are failing he needs to ask the permission explicitly.
2) When tests are failing, everyone should stop what they're doing and help stabilize again. We synchronize on IRC.
3) Flickering tests can be marked as @Ignore and a jira issue created to stabilize the build.
4) Release Manager creates a release branch 1 week before the release to let everyone stabilize the build
On a long term we need to work on improving our CI so that functional tests are built faster. One idea is: more agents and functional tests spread on several agents.
Here's my +1 to apply this now for master (3.2-SNAPSHOT leading to 3.2M1), which means not committing anything more till we have all functional tests passing.
Thanks
-Vincent
Dear all,
Down below is the working plan for this week and the next one.
Time Period
Tasks
Deliverable
May 24 -- May 28
use xwiki-platform-rest-model library and replace
xwiki-core-xmlrpc-model-1.4; develop RemoteXWikiDataStorage.java which
uses REST instead of XML-RPC
complete all the current methods in IDataStorage.java interface
May 30 -- June 3
extend IDataStorage.java with new functionality and resources provided
in rest-model library
complete all the functionalities in rest-model library, provide test
case plugin (xwiki.eclipse.test)
I have a question about restlet library, is there any plan to upgrade it
to v2.0+?
Or we will stick with v1.1?
Best regards
Jun Han
Hello,
To keep schedule we would need to have a release today and I am ready to release but we have some outstanding issues which need to be addressed.
1. An blocker was discovered today:
http://jira.xwiki.org/jira/browse/XWIKI-6654 Multiple backslash are not properly handled in reference resolvers
tmortagne is assigned so he can report back when this is finished.
2. vmassol wanted to evaluate each test to make sure that all test failures were indeed test errors and not software bugs.
Unfortunately this has been severely delayed because of:
http://jira.xwiki.org/jira/browse/XE-928 broken tests because jmx control port is in use
3. sburjan discovered what seems to be a blocker in the watchlist functionality
http://jira.xwiki.org/jira/browse/XWIKI-6656 Unable to watch a page/space/wiki
We need someone to confirm this and find out what's happening.
For release I would like somebody to help me with publicity management, I will handle Wikipedia where I have an account and the announcement mail where
I will use my signature but I would like somebody to help with Freshmeat, Wikimatrix, XWiki.org blog, and OW2 news. By spreading out the effort we can put
a little bit more time into adding some quality to the writeup. Can I get a volunteer?
Caleb