I just made some changes to the way the VLE handles bundle files that 
were saved to disk. This change won't really affect any of the SAIL/TELS 
stuff, since it's a solution to a problem that doesn't exist anymore.

You may recall that I made some changes to the bundle uploading process 
back in September. One of those changes was that the bundle file on disk 
would be deleted on exit if the bundle was successfully uploaded. Prior 
to that point, all bundle files on the disk were left there forever. So 
any project that has used a jnlp more recent than then probably doesn't 
have a whole lot of old bundle files sitting around on the disk. 
However, some of the DIY sites have been using a jnlp from before then, 
which means all of those DIY users have a folder full of 
probably-uploaded bundle files.

The change I just made now checks the maven.jnlp.version of the bundle 
before uploading it, and if it is from a version older than today, it 
skips (but doesn't delete) the file and moves on. (In the future, it may 
compile a list of the curnit uuid and session uuid for each bundle file, 
and then ask the sds which ones to upload, but that functionality isn't 
there yet.) It also will now process the bundle files in order from 
newest to oldest, so that even if a user has a huge folder of old 
bundles, any new bundles that get created and weren't uploaded will be 
processed first.

I don't expect it really to affect most of you, but I wanted to put the 
info out for your information. I rebuilt the jnlps just a bit ago, so 
anything using a snapshot jnlp will start using this feature. If you see 
anything strange happening with bundle uploads, let me know.

Thanks-
-- Aaron

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to