Hi Kesler, In future, please send your questions to [email protected] instead of issues@ since that mailing list is specifically for JIRA notifications only :)
Regarding the error 500, can you paste the exception/error you got in http://pastie.org/ and send the link? Attachments are disabled in the mailing lists IIRC.. Regarding the roles, there are only two roles available in Archiva by default: Repository Manager or Repository Observer. The manager role allows users to read and write (upload/delete) to the repository while the observer role gives users read-only access to the repository. I think it's possible to define your own role (with custom permissions) but that would involve hacking through the redback.xml file in archiva-security jar file. That's where the roles and permissions are defined. If you'll look into the sources of archiva-security/ in 1.3.x branch, you can look at how the roles and permissions are configured and mapped. Thanks, Deng On Wed, Mar 7, 2012 at 5:14 PM, kesler wang <[email protected]> wrote: > Hi Archiva Team, > There is 500 ERROR when I use Archiva 1.3.5, please have a look. > I did following operations: > 1. Start archiva service with command: archiva console (win7 64bit OS) > 2. Visit localhost:8080/archiva and login successful. > 3. Upload artifact : Group Id : test > Artifact Id : test > Version： 1 > Packaging： com > Classifier： empty > Artifact File： is any jar file > Repository Id ： Internal > click submit， there is a message notice me Artifact 'test:test:1' > was successfully deployed to repository 'internal' > 4. I can find file "test-1.com" file under archiva folder. > 5. Try to delete artifact with same property value, there is an > exception, please get it from attachment. > > > And there is other question: May I define a role by myself ? Like I > want a user has permissions to upload and read artifacts, but can't delete > any artifact. Could you let me know how to do that? Thanks a lot. > > Looking forward your reply. > > Cheers > > Kesler >
