Hi!,
I am Prateek Bilung, a second-year undergraduate student at B.I.T., Mesra
(India). I am new to open source community and want to contribute to this
organization. I know basics of javascript, DOM manipulation and interested
in the project "Translation in context". Please guide me on this.
Thanks!
Hi devs,
We’ve been using the surefire plugin from the beginning even for functional tests.
However it would be more correct to use the failsafe plugin for functional tests since this allows to perform some actions if a test fails (like stopping XWiki - Note that right now this is not affecting us since we start/stop XWiki from Java so we’ve implemented this behavior ourselves).
I need this for using the fabric8 docker plugin for ex so that if some functional test fails the docker containers will be stopped.
Ok with everyone?
For reference: http://maven.apache.org/surefire/maven-failsafe-plugin/
Thanks
-Vincent
Hi devs,
These are the current code style rules for committed XML wiki pages:
http://dev.xwiki.org/xwiki/bin/view/Community/XWikiXMLFilesCodeStyle
= Proposal 1 =
I was personally not aware we had documented these practices that we had
been applying since forever. It's good that we have them, but there seems
to be no mention about committing changes for the "creationDate", "date"
and "contentUpdateDate" fields.
Part of the committers (including myself) are applying the old practice of
omitting changes to the date fields when committing a change to an XML wiki
page. However, since this practice is not written and agreed upon, its
usage is not consistent.
So, the proposal is to include the rule of not committing changes on the
date fields of XML wiki pages.
The rationale, AFAIR, includes:
* After an upgrade, users should not see "ghost" modifications in their
wiki (e.g. when sorting by date in the Page Index). This affects even more
manual imports with the "as backup" option enabled.
* On release, any date changes of a default translation XML page will
produce N other XML page changes, for each translation of the modified page
(due to the way l10n exports the translations based on the latest version
of the default language of that page).
* others?
= Proposal 2 =
Now, building on this, I would like to make a second proposal (which I
don't believe deserves a separate thread):
1) Let's remove all date fields from committed XML wiki pages in our source
repository
2) Let's make sure that the XAR import properly handles empty or missing
date fields and falls back on the current date
3) Let's update the xar:format goal to remove the date fields
(configurable, since it could they might still be needed by some content
projects, etc.)
4) Let's make the build fail (xar:verify) if the XML wiki pages contain
date fields (again configurable, as above)
Note: All the above still depend on the first proposal of not committing
date changes to XML files (which will be simplified by point 3) above).
The rationale for this is that we have always wanted to fix our "dates
problem", since after installation, the wiki is populated with pages
created in 2009, which is extremely odd to users that have just installed
XWiki. This second proposal sounds to me like a solution for that.
WDYT?
Thanks,
Eduard
Hi guys,
I’m trying to use the Job REST API but the doc is pretty poor at http://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/XWikiR…
For example to execute a job it says that you only need to pass a “jobType” described as "The type of the job to pass to the Job Executor” … errr what’s the type and what are the valid values? Would be nice to have some example too.
Also it doesn’t mention any payload that I have to send but I guess I need to describe the job that I need to execute. What’s the format?
It also says:
“
Since 9.2RC1 jobs started trough the REST API automatically get their runtime context injected with the following REST HTTP request context properties:
• current wiki
• current user
• request URL and parameters
“
What if I want to specify the wiki, user for ex? How do I do that?
At the end there are examples of file format at http://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/XWikiR… but nothing for jobs.
Could someone help improve the doc so that I can try to use it?
Thanks!
-Vincent
Hi devs,
This proposal is related to the following discussion on IRC :
https://botbot.me/freenode/xwiki/2018-01-08/?msg=95495049&page=5
Abstract: We currently have an abstraction of the notion of a
"container" defined in xwiki-platform-container-api [1]. This
abstraction is very basic, but allows XWiki to support two different
types of containers : Servlet and Portlet, and maybe support other types
in the future.
Problem: As those abstractions are very basic, it's quite hard to use
them without downcasting them. A common example is the following: if I
want to send a redirection in a Response object [2], I will need either
to forge my own output that returns the correct HTTP code, with the
correct header, etc … or I can downcast the given Response to all of its
possible implementations and, for each implementation, find the correct
method to use for sending a redirect.
In order to avoid such tricks in the future, we could implement
decorators that will allow Request and Response implementations to
handle certain actions. In my previous example, a Response implementing
RedirectResponse would expose a method `#sendRedirect(String url)`. The
advantage here is that we don't really need to know on which Response
implementation we are working on.
WDYT ?
Thanks,
Clément
[1]
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwi…
[2]
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…