开发者

Indexed repositories within Artifactory

开发者 https://www.devze.com 2023-04-04 16:00 出处:网络
Apologies if this is obvious to everyone else... I\'ve deployed the Artifactory war file within tomcat6 and started the server: all looks great.

Apologies if this is obvious to everyone else...

I've deployed the Artifactory war file within tomcat6 and started the server: all looks great.

Now, I want to navigate around the preconfigured repositories, for instance repro1-cache. However, it appears it's empty, there are no tree elements to expand. This appears to be the story for all the listed repositories. Cons开发者_如何学编程equently I cant run any searches for particular artifacts.

Am I missing a stage here? Do I need to force it to index itself? What should I be expecting once I've deployed the war file and when I first log in?

I guess my expectation was that once having deployed the war file, Artifactory would automatically index the remote repositories. I'd then configure Eclipse to point at the Artifactory install, so that it can index the repositories within the IDE. Then when I declare a new dependency, Artifactory would download and cache it locally, allowing for faster resolution next time. Is this a valid expectation?

Any feedback will be most appreciated, particularly any pointers to user documentation that covers this that I've overlooked.


Your repositories are all empty because they aren't populated.
Once you deploy artifacts to the local repositories or request artifacts from remote repositories, you'll see them in the browser.

If you'd like to browse through artifacts not yet cached in remote repositories, you can use Artifactory's simple browser (see the Remote Browsing section).

Maven Indexes can be created and retrieved manually or as a recurring task; the Indexer can be configured in Artifactory's admin UI in Admin->Services->Indexer (also see the Indexer's wiki page).

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号