Community
Participate
Working Groups
If an artifact repository location is added through the Install New Software dialog the user is given an error indicating a repository was not found. (It is however used for artifacts.) Perhaps the easiest method to reproduce this is to remove the content jar/xml from a zipped repository and drag this to the UI. If the content file removed from the zip is placed in a directory which is also added to the UI the software can be installed.
I think this is expected behavior (for now). I don't see fixing this in 3.5. The UI assumes "colocated" metadata and artifact repos, so it adds both. It sounds like you are getting the failure because there is no metadata repository available at the location (but it so happens that the artifact repo was there). The user is never expected to add an artifact repo separately, although it obviously can be done as you did. In practice I don't see this causing a big problem for end users. If the intention was to add the directory above the artifact repo, and they make this correction, then they will end up adding the right artifact repo anyway. I'm going to mark this a dup of 222838 and add a note there that this situation can occur. *** This bug has been marked as a duplicate of bug 222838 ***
