> -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: 16 September 2004 21:25 > To: Avalon framework users > Subject: Re: Repository API query > > On Friday 17 September 2004 02:57, Rajamani Saravanan wrote: > > Thanks a lot, Steve... > > Steve seems to be missing in action today... > > > I tried with a snapshot version as well, but the behaviour is still > > the same, the jar gets downloaded once, but if the file has changed on > > the server, it does not get downloaded again... > > This is something Steve has been fooling around with yesterday. > Unfortunately, > I am not up-to-date with the current status, but there were problems > yesterday that timestamps were checked when not expected.
Specifically - the problem was that somewhere along the line the SNAPSHOT test get changed such that tests for SNAPSHOT artifacts always returned false. This has now been fixed in the trunk version so you should see the proper behavior if your running from a trunk build. > > I think the algorithm should be that artifacts that are declared with > <project> should not check the timestamp, only <resource> artifacts. I am > not sure that this is what currently is the case. Within magic there is no special handling of snapshot artifacts (mainly because the repository management used in magic is different code to the repository system. I'm working on changing this such that the repository bootstrap system loads magic much in the same way that repo loads merlin. > > One other query re. file based repository - if I add a file-based > > repository to the list of hosts to search for, the block installed > > using the code below does NOT get copied to the user's avalon cache... > > ..if the repository is a HTTP server, it gets downloaded... There is special handling of resources in file based repositories due to the different precision of last modification dates between file based resources and http resources. If (assuming you running against a latest build) a file is marked as SNAPSHOT then your local cache will be updated form the file repository. > Is this the current behaviour?? And you want the files always be copied to > the > local cache?? > > > Re. the block.xml file vs. the jar's .meta file : the jar's .meta file > > has the list of dependent jars generated using the artifact:install > > maven goal. The .meta files are managed by the repository system. Blocks are managed by Merlin. The .meta stuff is handled at repository level to establish system services (such as logging, the merlin system, merlin runtime etc.). Once the repository system has constructed everything - merlin kicks in and loads blocks (which are a lot more semantically rich). Cheers, Steve. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
