On 8/15/06, Brett Porter <[EMAIL PROTECTED]> wrote:
Hi Milos,
I'm a bit lost as to what you need.
So, say you have a repository manager at http://localhost:8080/
Then you have managed repositories called "snapshots" and "releases".
ok, these names are the ones defined in the repository manager.
You will be able to access those repositories at:
http://localhost:8080/snapshots/ and http://localhost:8080/releases/
respectively.
let's say in the user's project I call those "my-localhost-snapshot",
and "my-locahost-releases"
<repository>
<id>my-localhost-releases</id>
<name>My local repository</name>
<url>http://localhost:8080/releases/</url>
</repository>
The index will just be one (say,
http://localhost:8080/retrieveMinimalIndex.action). Inside that, each
record has an ID that will be able to determine whether it is releases
or snapshots.
1.http://localhost:8080/retrieveMinimalIndex.action URL has no
relationship whatsover to the repository URLs defined in the user
project, so on the client side I cannot guess it just by looking at
the repository URL in the project.
2. I make the user to fill in the URL for the index. Fine. But then
the names (ids) for the repository don't match anyway .. the local one
("my-localhost-releases") != repository index one ("releases")
Is that more clear on this example now?
Milos
At present, we are not tracking where it came from if it was via a proxy
or a synced repo. I inted to add that, but I don't think it is important
for the purposes you are describing.
Once this works, we will need to look at other ways of making the index
updates more efficient (Eugene has had some thoughts on that and has
posted them to JIRA).
So, does this fit what you needed or am I still missing something?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
