Details
-
New Feature
-
Resolution: Fixed
-
Major
-
3.1 RC1
-
Unit
-
High
-
Medium
-
Pull Request accepted
-
-
Code
Description
If it's your first Google Code-In task it's highly recommended to start with Become a community member.
Prerequisites
- The student will need to have a Jira account, if it's not the case you can signup here
- The student will also need a https://www.github.com account. You might also want to take a look at Git and GitHub interface documentations.
- Assign yourself to the Jira issue
Issue
The idea is that there is code which are linking resources to specific document and would like to know when a document has been renamed.
For example when you watch some document and that someone move it you are not watching it anymore.
The best place to put this event for now is probably along with the document events in https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwiki-platform-bridge/src/main/java/org/xwiki/bridge/event.
Of course you also need to make sure the standard move code will send those events. See https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-refactoring/xwiki-platform-refactoring-api/src/main/java/org/xwiki/refactoring/internal/job/MoveJob.java.
Expected Outcome
- The student must commit the changes and create a pull request on https://github.com/xwiki/xwiki-platform
- The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue
- Add a comment in the jira issue mentioning your pull request and provide a link to it
Links
- The student might want to read the observation module documentation before starting this task http://extensions.xwiki.org/xwiki/bin/view/Extension/Observation%20Module
Getting help
If you have any question you should use the Chat (faster answer, but when there is someone around) or the Forum (more people available, but slower answer).
Attachments
Issue Links
- blocks
-
XWIKI-3548 When renaming a user or a group document, access rights are not correct
- Closed
-
XWIKI-16165 Oldcore should trigger the document copy/rename events
- Open
-
XWIKI-1660 Renaming a document containing a class should offer to update all the objects
- Closed
-
XWIKI-13721 Rename related xobjects when renaming a page with a class definition
- Closed
- causes
-
XWIKI-19633 Renaming a document renames its content links twice
- Closed
- is duplicated by
-
XWIKI-6451 Create rename event
- Closed
-
XWIKI-13722 Introduce DocumentRenaming/edEvent
- Closed
- relates to
-
XWIKI-16110 Introduce DocumentCopyingEvent and DocumentCopiedEvent events
- Closed