Joakim,
How much disruption is this going to cause? I know we want to do this
at some point, but if it turns into something big or risky, I'd
rather we just put the security in the browse action for now and take
this on in 1.1.
- Brett
On 27/10/2007, at 10:21 AM, Joakim Erdfelt (JIRA) wrote:
archiva-security/ needs to move from archiva-webapp/ to archiva-base/
---------------------------------------------------------------------
Key: MRM-570
URL: http://jira.codehaus.org/browse/MRM-570
Project: Archiva
Issue Type: Task
Components: Users/Security
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Since we need to implement backend security around the browse
(MRM-569) and search (MRM-516) facilities, the archiva-security
module needs to be decoupled from archiva-webapp and brought into
archiva-base for the general use of all archiva-base modules.
Leaving archiva-security like it is now will result in pulling in
many webapp specific libraries and concepts that are not needed in
the archiva-base heirarchy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/
software/jira
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
