- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] Copy page through Restful API

by xManish

Hi, In XWiki, we could copy a page from one space to another space. Is there any thoughts about making a copy of page through RestApi. While copying a page, all of the objects within that page should be copied over too. The only way I can see it can be done now is by getting all objects of that page, iterate through them and create them one by one. Is there a better solution to this? Thanks in advance Regards, Manish -- View this message in context: http://xwiki.475771.n2.nabble.com/Copy-page-through-Restful-API-tp6575262p6… Sent from the XWiki- Dev mailing list archive at Nabble.com.

14 years, 1 month

4
3
0 0

Re: [xwiki-devs] [xwiki-users] [Demo] Wiki3.0 project preview

by Eduard Moraru

Hi Marius, On Wed, Jul 20, 2011 at 8:49 AM, Marius Dumitru Florea < mariusdumitru.florea(a)xwiki.com> wrote: > Hi Eduard, > > On 07/19/2011 11:29 PM, Eduard Moraru wrote: > > Hi community, > > > > If anyone is curious, a demo installation of the current work on the > Wiki3.0 > > [1] research project is available at http://wiki30-demo.xwiki.com > > > > With the Workspaces feature, you can register a user and create > workspaces, > > invite/accept other users and generally manage your workspace. > > > > Interesting sections (or rather a list of features) are: > > > > = In the main wiki = > > > > - Create new Workspace (Add menu or homepage button) > > - Workspace Directory (Top menu, under 'Workspace') > > - 'Workspaces' section in user profile > > - User Directory improvements > > - Join/Leave/Request membership/Accept invitation to join a workspace > > (Workspace Directory or homepage of a workspace) > > - Workspace search suggestions (top-right search box) > > > > = In a workspace = > > > > - Dashboard > > - Workspace information panel (right panels) > > - Main wiki link (Top menu, under 'Workspace') > > - Delete workspace (Top menu, under Workspace, for owner) > > - Workspace Configuration section (Administration, 'Configuration' > category) > > - Workspace Users section; Accept membership requests or invite users > > (Administration, 'Users& Groups' category) > > - User registration redirecting to main wiki (Top-Right register link) > > - Removed local XWiki.Admin user > > > > > > Besides the Workspaces feature, the Real-Time editor is also available > for a > > quick test. You can access it by editing a page in "Real Time" edit mode. > > You can't miss it :) > > The real time editor is quite nice. I haven't tested it before. We > should definitely integrate the line number feature in the wiki edit mode. > > > For quick tests, you can edit the same page in 2 browser windows and see > > changes in one window triggering an update in the second one. It also > works > > with multiple users (obviously) and allows other to join in the editing > > session. > > > > For now it's working real time only for wiki code. Work on the WYSIWYG > > version has already started. > > > > > > Please feel free to report any bugs or suggestions here or (preferably) > at > > http://jira.xwiki.org/jira/browse/WIKITHREEDOTO and do be aware that > it's > > still work in progress. > > The list of users in the Workspace information panel is not right for a > newly created workspace. My user is listed twice and the first avatar in > the list points to the workspace home page. > Fixed. > Also, the Top Active Members section lists 3 users: > > Administrator -> global user (should be hidden IMO) > Admin -> local user, missing (again, should be hidden IMO) > Fixed. my user, but the link points to the corresponding local user which is > obviously missing > AFAIK, this is a bug http://jira.xwiki.org/jira/browse/XWIKI-6103 that has been fixed for XWiki 3.1. The problem is at wiki creation time, because I change the context database and the context user does not change accordingly, making Activity Stream to register the unchanged user, thus, resulting in a local user instead of global. When I will upgrate to 3.1, I hope that this will be fixed too. In practice, the 'ghost' user will disappear as fast as at least 5 users start editing pages :) > > Looks great otherwise. Well done! > Thanks :) and thanks for the feedback as well, Eduard > > Thanks, > Marius > > > > > Thanks, > > Eduard > > > > ----------------- > > References: > > [1] https://wiki30.xwikisas.com/ > > _______________________________________________ > > users mailing list > > users(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users >

14 years, 1 month

1
0
0 0

[xwiki-devs] [PROPOSAL] Introduce begin/end events standard

by Thomas Mortagne

Hi devs, I would like to introduced a standardized (at observation API level) way to indicate that en event represent the beginning or the end of something. The idea is them to use it in things like activity stream to group events/whatever or in my case maintain a stack of states in the Execution context about the current action updated by listening to events. My immediate use case is to filter some modification in automatic watch feature (imported xar, crated wikis, etc.) but I feel that we need that information for a larger audience. In details my proposal is to introduce BeginEvent and EndEvent interface (feel free to suggest better names if you have some in mind). Then pushing the BeginEvent instance in the context in a stack of current events poped when receiving a EndEvent. Note that I don't not plan to put an id in Begin/EndEvent since it should not be needed if they are properly generated (some job can't finish if all it's sub jobs are not finished). WDYT ? -- Thomas Mortagne

14 years, 1 month

4
4
0 0

[xwiki-devs] XWiki Android Client

by Chamika Weerasinghe

Hi all, Thank you all for giving me help to develop xwiki-android-client and passing me in GSOC mid evaluation. Since I've finished most of the xwiki android navigation features now I'm working on adding other features which uses XWiki RESTful POST and PUT methods. There is really big problem here. Because until now I used json objects to communicate with XWiki REST. But REST doesn't support accepting json objects. Please correct me if I'm wrong. If REST doesn't accept "application/json", I have to modify almost all the classes in xwiki-android-rest to be worked with xml. Another drawback is still REST doesn't provide "links" of the elements in json but xml provides it. Fabio described it here ( http://blog.fabiomancinelli.org/2011/03/07/XWikis_RESTful_API.html) I selected json because it can be deserialized using gson which is the smallest json deserializing library specially designed for Android. But now I feel that moving from json to xml is the best option. A light weight xml serialization library named simple-xml ( http://simple.sourceforge.net/) would be a feasible library for Android. Should I proceed with xml using simple-xml or can you suggest me a better option which saves my time from modifying classes? Thank you, Best Regards, Chamika Weerasinghe

14 years, 1 month

2
1
0 0

[xwiki-devs] about documentation of adding a tag to a page via REST API

by Jun Han

Dear all, I am trying to add a tag/tags to a page. However, it seems to me that there is an inconsistency between XWiki REST API document and its implementation. http://platform.xwiki.org/xwiki/bin/view/Features/XWikiRESTfulAPI#HTagresou… The document indicates that PUT method can take <tag> element and will add a tag. However, the implementation only takes <tags> element (via xml/application) and PUT method replaces all the existing tags with the new tags included in the <tags> element. Is there a REST call that only adds a tag to the page without replacing all the existing ones? Best regards Jun Han

14 years, 1 month

2
1
0 0

[xwiki-devs] The plan of GSoC project "Auto-completion in content editors" (7.18 - 7.24)

by 许凌志(Jamesxu)

Hi, Last week I have done following things: 1. Fix most of the bugs Marius had found last week, there are still three left for further discussion with mentors 2. Refine the codes according to the last review by Marius 3. Read the documentation of writing REST service, and design the rest service for link auto-suggestions, I should talk with mentors about the implementation details. In this week, I am going to do the following things: 1. Implement Rest service for link suggestion 2. Implement the whole context for link suggestion, include "attach:", "@", "." and "||". 3. Consider to implement the ctrl+space to re-open the suggestion box according to the different contexts of link suggestion. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 1 month

2
1
0 0

[xwiki-devs] The plan of GSoC project "Auto-completion in content editors" (7.4 - 7.11)

by 许凌志(Jamesxu)

Hi, thanks for Marius' help ,last week, I have done the following work: (1). Implemented the function that logs a message in the firebug console whenever the caret is after [[ (2). Implement the function that requests the list of wiki pages matching some prefix user input. BUT, don't actually query the database, instead simply return a dummy list from the wiki page. (3). Implement the function that displays the list of wiki pages where the caret is, and integrated it with the SuggestionBox I have already implemented. Here is the plan for next week: I will focus on fixing bugs and improving what I have and to make suer by the end of the week the link suggest should work very good. Include (1). Display the suggestion box in right place and at the right time. (2). Close suggestion box in custom, and also when some other keys typed like "esc" "right" and "left" (3). Test to make sure the prototype for link suggestion runs very well. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 1 month

2
8
0 0

[xwiki-devs] a successful integration of XWiki with Sakai

by Adam Hocek

Hello XWiki Developers, I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities. If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests. Cheers, - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948

14 years, 2 months

5
13
0 0

[xwiki-devs] Are there XWiki UI tests?

by Adam Hocek

Hello, Since we have integrated XWiki with Sakai and we are helping to develop test plans for the integration tool. I wanted ask if there are any UI tests available for XWiki? This would be helpful to our goal. Thank you, - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948

14 years, 2 months

2
1
0 0

[xwiki-devs] [Proposal] XE 3.2 Roadmap

by Vincent Massol

Hi devs, Since we're getting close to XE 3.1 final release it's time for defining the roadmap for 3.2. After discussing offline with several XWiki devs (the ones from XWiki SAS) here's a list of items for 3.2 that we came up with. • Features • UI for extension manager + backend extension manager (continued, especially nice XAR upgrades) • Search improvements and especially scoring, French support and wildcard issues (continued from 3.1) • App Within Minutes • Jiras Priority 1 • XWIKI-6504 Convert Panels application into syntax 2.0 • XWIKI-6676 UI does not report failed delete actions of attachments; XWIKI-6623 Attachment upload failure gives no feedback to user • ORACLE fixes • Fixes for HTTPS support • XWIKI-6687 Be able to delete a space from the UI • Jiras Priority 2 • Stats module improvements (Commit code from client projects without changes) • LDAP Admin UI (commit Jerome work without changes) • Clustering bug • XWIKI-6684 Use a predefined Space Template like Dashboard, Livetable when creating a new space • XWIKI-6073 Change stylesheet and javascript extension filename when a modification is done on those • Investigations • Solr • Browser support (IE6, IE7, Safari) • XWiki in 5min • XEM/Workspace features This is of course a minimal list that we're proposing to implement. More could be implemented but we're proposing to guarantee the implementation of the items above. Now we need to put names against each of these items. Can you please volunteer and put your name next to issues you'd like to implement? Thanks -Vincent

14 years, 2 months

13
27
0 0

[xwiki-devs] [Proposal][UX] Application Within Minutes - Fields Parameters (I1)

by Ecaterina Moraru (Valica)

Hi devs, I did some work on the *fields parameter importance* and on the *displayers* we already have: String, TextArea, Static List and Database List integrated into Single Line Text, Paragraph Text, Radio Button, Checkboxes and Drop Down fields. The proposal covers what fields will be displayed in simple and advanced modes for these fields types. http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinM… Thanks, Caty References: [1] [Proposal][UX] Application Within Minutes - Proposal 2: http://markmail.org/thread/beflzm3xeenfpnrh [2] http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AWMListManagement

14 years, 2 months

4
6
0 0

[xwiki-devs] XWiki Android Client Status

by Chamika Weerasinghe

Hi all, I've finished XWiki android client to some extend with following features. Login - HTTP Basic Auth. XWiki navigator - tree style xwiki navigator to explore wikis, spaces and select pages. XWiki Page Viewer - Simply shows the content of a page via accessing Objects and Properties of REST model. This will be developed further XWiki Object Viewer - Explorer objects of a given page. These are the screenshots of the xwiki android client https://picasaweb.google.com/chamikaw/Xwiki?authuser=0&authkey=Gv1sRgCLet4s… Improvements: 1. After modifying XWiki navigator to load dynamically as Thomas requested, it take more time since many http requests are handled. I will improve by reducing number of http requests as soon as possible. Until then xwiki navigator works but it's unstable and take long time to load. 2. xwiki classes view will implement within next week. Issue solved: Although repository can be built using maven it will not produce correct apk file to deploy in android devices. This issue is solved by using Maven Android Plugin 2.9.0-beta-1 release. Now generated .apk file in xwiki-android-client can be deployed in android devices. Please be kind to test it and give your opinions for improving. Best Regards, Chamika Weerasinghe

14 years, 2 months

3
5
0 0

[xwiki-devs] Extension Manager plan for 3.2

by Thomas Mortagne

Hi xwikiers, Here is a quick status of Extension Manager work in progress and what we (Jean-Vincent Drean and me) plan to do for 3.2. = XWiki Repository = 3.1 main target was XWiki Extension Repository and work on it will continue in 3.2 as well Conversion of extensions.xwiki.org as a XWiki Extension Repository slipped a bit but that will hopefully be fixed during 3.2. What makes it complex is that REST URLs are going to be changed during 3.2. I'm still not sure what's the best between use a 3.2 snapshot of XR rest service which wil not work with 3.1 or keep 3.1 which will not work with 3.2 = Virtual extensions = Currently we have an issue when trying to install old stuff depending on extensions for which the name changed like xwiki-core which is now xwiki-platform-oldcore so to take care of that 3.2 will introduce virtual extensions. The id is that an extension can comes will a list of id aliases which will be use as well as its own id to resolve dependency agains already installed extensions. For example org.xwiki.platforms :xwiki-platform-oldcore will declare com.xpn.xwiki.platform:xwiki-core in its virtual extension list so when an old plugin is installed using extension manager it does not try to actually install the version of com.xpn.xwiki.platform:xwiki-core declared by the plugin and make XWiki pretty much unusable. This will also allow to more easily suport several implementations for the same API, all theses implementations would declare the same virtual extension id. This is very similar to Debian virtual packages concept. See http://jira.xwiki.org/jira/browse/XWIKI-6742. = Reporting improvement = A bridge producing events based on log as just been committed, the idea is to have a generic way for component to access application logs easily. This can be used later with activity stream or remote observation manager. For Extension Manager the plan is to use that in the job manager (former task manager) to gather detailed log produce by extension manipulation job like install or uninstall and queue it in the job status. On the same idea a progression system has just been committed in extension manager which update a progress offset during job execution using events. Job Manager and both related progress and log tools are currently "hidden" in extension manager but will be move as common tools when we are happy enough with it to make easier to report progress or long task in XWiki (Lucene indexing, report page rendering log in some tab, etc.). See http://jira.xwiki.org/jira/browse/XWIKI-6781 = Non interactive 3 ways merge of XAR = Xar handler will support full 3 way merge of applications between previous xar, new xar and database. 3.2 will probably be fully non interactive as a first version but we plan to implement a question/answer system allowing to let user do live conflict resolution since there is always corner case where a generic automated system can't find any good solution. See http://jira.xwiki.org/jira/browse/XWIKI-6650. = Stabilized API = Starting with 3.2 most Extension Manager APIs will not be broken without long deprecation phase when possible as any other public API in XWiki. BTW to make sure I'm not lying too much would be great to get as much review as possible on theses ;) = New UI = Last but not least we will start the real (as not just a demo of the framework features) Extension Manager UI in 3.2. The plan is to follow Ecaterina Valica's (awesome) proposal you can see on http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ExtensionManager. To be more precise we should be able to do the following for 3.2: * general UI refactoring based on http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ExtensionManager to some extent * detailed progress and log of extensions manipulation thanks to new framework APIs * extension detailed informations * live table for search result See http://jira.xwiki.org/jira/browse/XWIKI-6775 Thanks, -- Thomas and JV

14 years, 2 months

1
0
0 0

[xwiki-devs] [proposal] Enable CSRF protection by default during the testing phase of 3.2

by Alex Busenius

Hello devs, I'd like to enable CSRF protection by default at least until 3.2-RC1 for testing purposes. The CSRF protection mechanism as been added in 2.5, but is still disabled by default, because many functional tests used to fail with CSRF protection (false positives). I have fixed the tests to work with CSRF protection, so we can try to enable it and test on a larger scale, maybe even on myxwiki.org (with RC1). If no critical bugs will be found during the testing, I'll call a vote to let it enabled in 3.2 final. Implementation note: Enabled CSRF protection puts some restrictions on possible requests that should be respected by the tests. For example, it is not possible to construct a request that logs-in as admin and deletes a page using xredirect, something that is used in UI tests for speedup. We might want to refactor the test utils a bit to discourage doing such things. Commits: * Branch enabling the protection by default https://github.com/xwiki/xwiki-platform/tree/enabled-csrf-protection * Branch with fixes for functional tests https://github.com/xwiki/xwiki-enterprise/tree/enabled-csrf-protection Bugs: http://jira.xwiki.org/jira/browse/XWIKI-6773 http://jira.xwiki.org/jira/browse/XWIKI-5465 Here is my +1 WDYT? Thanks, Alex

14 years, 2 months

5
7
0 0

[xwiki-devs] rest API does not return information by querying /wikis/wiki1/spaces in XEM-3.2-snapshot

by Jun Han

Dear all, After deploying XEM-3.2-snapshot, I created a wiki called wiki2. In XEclipse or browse http://localhost:8080/xwiki/rest/wikis, three wikis can be found, xwiki -> main wiki templatexe -> template wiki2 -> newly created wiki Then I tried to navigate in XEclipse or just use a browser. Information for all the spaces is not fetched via the URL http://localhost:8080/xwiki/rest/wikis/wiki2/spaces However, if I type the URL in the browser 1. http://localhost:8080/xwiki/rest/wikis/wiki2/spaces/Main 2. http://localhost:8080/xwiki/rest/wikis/wiki2/spaces/Main/pages The information for Main space and its pages shows up correctly. I am not sure if this is a bug in REST API. Best regards Jun Han

14 years, 2 months

1
1
0 0

[xwiki-devs] Mechanism to deprecate phrases?

by Paul Libbrecht

Hello XWiki developers, In Curriki, we have about 4000 translation keys... and we're sure there are parts we could deprecate somehow so as to get rid of them one day. They are mostly used in XWiki, a little in JavaScript. Has there been any effort done in this direction? Would it be possible for example to flag the phrases of one page as being deprecated so that it outputs a warning if used which one would collect later? Or... would it be possible to move away already a page of phrases and load it on demand for some legacy pages? thanks for ideas paul

14 years, 2 months

3
3
0 0

[xwiki-devs] [Proposal] Better support for Google Analytics (XWIKI-6579)

by Denis Gervalle

Hi Devs, I would like to answer XWIKI-6579 properly, we had an initial patch that continue tu use the .vm we had before in the core for GA support, filling it properly and providing a configuration page (see https://github.com/dgervalle/xwiki-platform/commit/192753ce97f94baf34aa2a2a… ). Since I do not see it as good as it could be, we have rewritten this patch to use a JSX, in place of the .vm. (I know JSX is loaded defer at the top now, but since the whole GA script is asynchronous, there is no more a requirement to have it in the bottom IMHO). The JSX is activated by the configuration page. Now I am wondering how I should integrate this solution in the existing code base ? 1) location : A) in XWiki B) in GoogleAnalytics space 2) document(s): A) a single document XWiki.GoogleAnalyticsConfig (config page as content, defining a class for config, containing the config object instance, and a JSX) and using translation from the core B) two documents (or more), the same as above or splitted, with a separate XWiki.GoogleAnalyticsTranslations (for just a few string, but how could it be managed with L10N ?) C) same as A, but with translation in the place official extensions will manage their translation for being supported by i10l 3) application nature: A) in the global xar, deployed by default, without anything special B) in the global xar, but with an application definition in XApp.XWikiApplicationGoogleanalytics C) in its own xar, deployable from a xwiki maven repositiory with the new extension manager D) in its own xar, on my own maven, as a private contrib, accessible manually with the new extension manager 4) sources: A) added directly to the administration application B) in xwiki-plateform-core/xwiki-platform-googleanalytics C) in ???, the place to put xar that will be build for 3C above and officially released by the XWIki Development team D) in my own github repository (for 3D) Since the code is ready, and this is just a matter of packaging, fast answer would be nice :) Personally, I felt very annoyed by where to put the translations (to manage them with l10n), so I see only how to do a simple AAAA solution, but thought the best would be AAAC or ACCC, but really do not know how to really implement it, and I feel we are not yet ready for them. WDYT ? What should I do right now ? -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

14 years, 2 months

3
4
0 0

[xwiki-devs] [Proposal][UX] Improvements for the Add menu

by Ecaterina Moraru (Valica)

Hi, This is a proposal regarding the improvement of the Add menu in order to: - specify a template for the newly created entities (space/page); - specify also applications templates; - some improvements for the create page step: the ability to select an existing space or create a non-existing one + position changes. You can see the proposal at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/CreateMenuProposal The "Add" menu could contain just the entries: - Page - Space - Application. In the usability interviews I had, no one used the other shortcuts ('Comment to page; Attachment to page'), but the interviewers were not beginners users, so if someone from the community is using those shortcuts please tell us if you want to keep them. The Create Space step relates to http://jira.xwiki.org/jira/browse/XWIKI-6684 The Create Page step relates to http://jira.xwiki.org/jira/browse/XE-897 For the application homepage http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ApplicationWit… the create action will auto-generate the page name (according to the options) and will preserve the current space [1]. With this proposal we can benefit from the contextual actions (for applicationWithinMinutes inside the designated space) but we are not dependent completely of the space, being able to create application instances in an universal manner from the "Add" menu. Also, the existing behavior for the wiki pages will be preserved. The default option for the template + location will modify accordingly to the context where the "Add" menu was launched. Please provide feedback. Thanks, Caty [1] http://xwiki.markmail.org/thread/mac6a24us4ucmp3j

14 years, 2 months

3
3
0 0

[xwiki-devs] Fwd: [ANN] Maven Release Plugin 2.2 Released

by Vincent Massol

could be good to upgrade. -Vincent Begin forwarded message: > From: Stephen Connolly <stephenc(a)apache.org> > Date: July 1, 2011 12:28:29 PM GMT+02:00 > To: announce(a)maven.apache.org, Maven Users List <users(a)maven.apache.org> > Cc: Maven Developers List <dev(a)maven.apache.org> > Subject: [ANN] Maven Release Plugin 2.2 Released > Reply-To: "Maven Developers List" <dev(a)maven.apache.org> > > The Maven team is pleased to announce the release of the Maven Release > Plugin, version 2.2 > > This plugin is used to release a project with Maven, saving a lot of > repetitive, manual work. Releasing a project is made in two steps: > prepare and perform. > > http://maven.apache.org/plugins/maven-release-plugin/ > > You should specify the version in your project's plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <version>2.2</version> > </plugin> > > Release Notes - Maven 2.x Release Plugin - Version 2.2 > > ** Bug > * [MRELEASE-374] - Snapshot versions unusable in batch mode > * [MRELEASE-622] - Creating label fails for ClearCase with message > 'Unable to determine VOB for pathname ".".' > * [MRELEASE-661] - Exception: String index out of range: -1 > > ** Improvement > * [MRELEASE-591] - release:update-versions: add option to do a checkin > * [MRELEASE-605] - when not pushing changes to remote git repo in > 2.1, the release plugin fails on release:perform > * [MRELEASE-628] - Subversion --trust-server-cert option > * [MRELEASE-641] - upgrade to scm 1.5 (hg plugin insists on 'pushing') > > ** New Feature > * [MRELEASE-159] - Support a pattern to generate the release tag > * [MRELEASE-457] - Non sparse-checkout SCM support > * [MRELEASE-613] - Add a parameter that tells the plugin to wait > for X seconds before tagging > * [MRELEASE-621] - Add a postPrepareGoals > * [MRELEASE-648] - Putting SVN password in settings.xml doesn't > support password encryption > > Enjoy, > > -The Maven team > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe(a)maven.apache.org > For additional commands, e-mail: dev-help(a)maven.apache.org >

14 years, 2 months

1
0
0 0

[xwiki-devs] [Brainstorming] Console Module/Application for logs

by Vincent Massol

Hi devs, I'd like to start brainstorming about implementing a notion of console from within XE. The idea is that most of our current logs that go in the shell console are actually application-level logs that should be visible to wiki developers (developers of applications inside XE). I've started a design page at http://dev.xwiki.org/xwiki/bin/view/Design/ConsoleModule Here are some initial ideas: * centralized logs available from all nodes * idea: use activity stream * UI: a new console tab in pages for all logs for the page * UI: an admin page for all console logs with a livetable for filtering * nice: real time addition of new logs (comet and co) * memory cache (eg last 100 logs) + block save (anti flood protection) * long term logging with compacting * system log vs application log * Requirement: current node id * Console Module / Application with API * idea: appender for slf4j (note: could use MDC for additional data: http://www.slf4j.org/api/org/slf4j/MDC.html) WDYT? Shoot your ideas! Thanks -Vincent

14 years, 2 months

3
2
0 0

[xwiki-devs] Second Commit for the plan of this week .GSoC-"Auto-completion in content editors"

by 许凌志(Jamesxu)

Hi, I have submit my second commit of the project, it contains four small commits: 1. Make patch for the suggestions given by review comments of Marius for my last commit. 2. Add some wiki editor(textarea) related utility functions for WikiEditor object, it is useful when intergate the suggestion box to the editor. 3. Codes for the second and third part of my plan this week: (a). Implement the function that requests the list of wiki pages matching some prefix user input. BUT, don't actually query the database, instead simply return a dummy list from the server. (b). Implement the function that displays the list of wiki pages where the caret is. But I use the suggestion box I have already implemented before this week, instead of writing a plain HTML list inside a DIV. 4. Make a patch for modifying the suggestion json format for link suggestion box Here I want to explain how I Implement the function that displays the list of wiki pages where the caret is. When the suggestor started, I add a mask which duplicate the same content with the same size, position and also same style of the textarea. When user types triggers, for example, type "[[" for link suggestion, the mask will be updated for two things: (1). update the content to syncronized with the values in textarea. And also surround the trigger with a "span" mark, for example, for "[[", it will be surrounded by <span id="suggestion_mark">[[</span>. It is useful for recorde the trigger and get its offset position which is the right place to show the suggestion box. (2). update the position of the mask include the scrollTop of the mask to syncronizied with the textarea. I use the LinkSuggestionBox which I have implemented last week to show the suggestion results, it can be shown in the right place now. But the navigation of the result item by up and down key does not work now, I have found the problem and I will refine it in next commits. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 2 months

1
0
0 0

[xwiki-devs] How to write xwiki servlet

by 许凌志(Jamesxu)

Hi, I want to write some server side codes for ajax response, anyone can tell me how to do it, is there any documents for that? Thank you very much -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 2 months

2
1
0 0

[xwiki-devs] Status: GSOC Xwiki Android Client

by Chamika Weerasinghe

Hi, I modified navigator in xwiki-android-components so that it will communicate to XWiki instance via xwiki-android-rest. But it cannot be tested due to following problems. 1. After building xwiki-android-rest library it doesn't have GSON library. Therefore REST isn't working since GSON classes are not found withing the library. I searched a method to include gson (or any other) jar file to add to my custom library. It is said that if we use scope of the dependency of the maven configuration as "compile" it will include jar files in our build. But it doesn't work for me. 2. Since xwiki-android-component use xwiki-android-rest, I want to import rest library to the component. I've done this in eclipse. But cannot figure it out how should I do this in maven. Due to above issues current repository give build errors. I planned to develop object/class editor component in next few days since xwiki-navigator is almost finish. Eduard suggested, it should be an "open objects and classes (in a separate and configurable object/class editor widget) ". Can you describe about this widget further so that I can get a clear idea about it. Best Regards, Chamika Weerasinghe

14 years, 2 months

3
2
0 0

[xwiki-devs] Commit for the plan of this week .GSoC-"Auto-completion in content editors"

by 许凌志(Jamesxu)

In this commit, I Implemented the function that logs a message in the firebug console whenever the caret is after [[ (but just that, nothing more!). It contains two small commits, one if the codes for LinkSuggestor, and the other is the test codes for it. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years, 2 months

1
0
0 0

[xwiki-devs] XWiki/XEclipse template/form system.

by Karel Gardas

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

14 years, 2 months

4
12
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs