| Apache Archiva > Index > Archiva FAQ |
Some of the most frequently asked questions about Apache Archiva:
See: http://www.nabble.com/Location-of-index-files-in-1.0--t3901605.html
TODO: Document complete list and improve search results page MRM-130
You must install a Java Development Kit 5 or later. See http://java.sun.com/ for downloads for your platform.
Local file system access by applets is not allowed in some corporate environments. To disable just the applet, or the entire Find Artifact feature, edit this section in ~/.m2/archiva.xml
<webapp>
<ui>
<showFindArtifacts>true</showFindArtifacts>
<appletFindEnabled>true</appletFindEnabled>
</ui>
</webapp>
TODO: Is Find Artifact really disabled, or can you still get there if you construct the URL?
Edit archiva/conf/plexus.xml and change the driverClassName, url, username and password properties.
For a detailed example, see Archiva with MySQL or Archiva User DB on Derby Network Server.
Set the derby.system.home property, as described here.
See Archiva on Jetty.
By default Archiva provides a secure WebDAV URL that needs a user and password. Generally it is expected that users are created and the granted access through the Repository-Observer role. If you want it to be completely open, then you need to add the Repository-Observer role for the repository in question to the Guest user. Access control is handled through the User Management page when logged in as an administrator.
Check out the archiva.xml file in your $M2_HOME/ directory (usually ~/.m2/) and you'll understand how.
Edit the 'guest' user and grant it the repository observer role for that repo. There is also a global repository observer role you can grant, if you want all of your repositories to be visible without logging in.