[
https://issues.apache.org/jira/browse/STANBOL-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618029#comment-13618029
]
Reto Bachmann-Gmür commented on STANBOL-897:
--------------------------------------------
Ok, so the new patch has a different base than the old ones (the old ones where
created in commons/security/usermanagement), still it doesn't work. Did you
update your svn version (svn up) before creating the patch?
reto@mufu-desktop-hp:~/projects/apache/stanbol$ patch -p0 <
commons/security/usermanagement/patch_2013-03-30.txt
patching file
commons/security/usermanagement/src/main/resources/templates/html/org/apache/stanbol/commons/usermanagement/webConsole.ftl
Hunk #2 FAILED at 54.
Hunk #3 FAILED at 65.
Hunk #7 FAILED at 266.
Hunk #8 FAILED at 310.
Hunk #9 succeeded at 368 (offset -1 lines).
4 out of 9 hunks FAILED -- saving rejects to file
commons/security/usermanagement/src/main/resources/templates/html/org/apache/stanbol/commons/usermanagement/webConsole.ftl.rej
The next patch would empty out the file
commons/security/usermanagement/src/main/resources/templates/html/org/apache/stanbol/commons/usermanagement/resource/rolesCheckboxes.ftl,
which is already empty! Assume -R? [n]
Before committing the next patch please check that you can apply it on a fresh
svn version with patch -p0 < your-file.patch
> Usermanager broken
> ------------------
>
> Key: STANBOL-897
> URL: https://issues.apache.org/jira/browse/STANBOL-897
> Project: Stanbol
> Issue Type: Bug
> Components: Commons
> Reporter: Reto Bachmann-Gmür
> Attachments: patch_2013-03-22.txt, patch_2013-03-26.txt,
> patch_2013-03-30.txt, UserManagement_2013-02-21.patch,
> UserManagementApiTest.java, UserManagement.patch,
> UserManagement_svn_2013-02-21.patch, usermanagement-tests.tar.gz
>
>
> The current usermanager is severly broken. It should allo adding and removing
> users and roles, assigning roles to user and adding individual permission
> both to users and roles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
