[
http://jira.codehaus.org/browse/MRM-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121359
]
Brett Porter commented on MRM-668:
----------------------------------
this could certainly explain the difference! In the first one, I retained my
repositories and user database. In the second one, I used the pre-defined
internal repo. So both would work.
This would seem to be a pre-existing bug with a simple workaround (assign
yourself the observer role). Does that work?
> Repo browse and search isn't working in trunk and in archiva 1.0.1 release
> candidate
> ------------------------------------------------------------------------------------
>
> Key: MRM-668
> URL: http://jira.codehaus.org/browse/MRM-668
> Project: Archiva
> Issue Type: Bug
> Components: browser
> Affects Versions: 1.0.1
> Reporter: Maria Odea Ching
> Priority: Blocker
>
--
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
