RE: release managment help
Okay, here we are - I need some help to promote the sling explorer release 1.0.0: 1) Which of the files I do have to copy to /x1/www/www.apache.org/dist/sling on people.apache.org? All files which are under [1]? If yes, which is the most efficient way to download them all from there (locally I do not have the md5 and sh1 files). Yeah. You should have all the files in your local Maven repository. All the sha1 and md5 files are missing in the local Maven repository, the other files are present. I downloaded the missing files from [1] which is a bit annoying. Any idea why the sha1 and md5 are not present in the local repo? And some further problem: logged in to https://repository.apache.org but Promote is a disabled action, only Release is possible here. Is the description under [2] correct or do I have to use Release here? [2] http://sling.apache.org/site/release-management.html 2) Should I deploy Sling Explorer also to Sling OBR? Yes. But only after the central sync has happened, which is usually after your Release the staging repository in Nexus. Justin [1] https://repository.apache.org/content/repositories/orgapachesling- 007/org/apache/sling/org.apache.sling.extensions.explorer/1.0.0/ best regards mike
Re: release managment help
On Oct 29, 2010, at 4:33 AM, Mike Müller wrote: Okay, here we are - I need some help to promote the sling explorer release 1.0.0: 1) Which of the files I do have to copy to /x1/www/www.apache.org/dist/sling on people.apache.org? All files which are under [1]? If yes, which is the most efficient way to download them all from there (locally I do not have the md5 and sh1 files). Yeah. You should have all the files in your local Maven repository. All the sha1 and md5 files are missing in the local Maven repository, the other files are present. I downloaded the missing files from [1] which is a bit annoying. Any idea why the sha1 and md5 are not present in the local repo? No. I'll try to pay better attention the next time I cut a release. And some further problem: logged in to https://repository.apache.org but Promote is a disabled action, only Release is possible here. Is the description under [2] correct or do I have to use Release here? [2] http://sling.apache.org/site/release-management.html That may have changed with a recent Nexus upgrade. Try it and if the artifacts are on central a few hours from now, you'll know it worked (and then please change the docs). Thanks, Justin 2) Should I deploy Sling Explorer also to Sling OBR? Yes. But only after the central sync has happened, which is usually after your Release the staging repository in Nexus. Justin [1] https://repository.apache.org/content/repositories/orgapachesling- 007/org/apache/sling/org.apache.sling.extensions.explorer/1.0.0/ best regards mike
Re: release managment help
Justin Edelson wrote On Oct 29, 2010, at 4:33 AM, Mike Müller wrote: Okay, here we are - I need some help to promote the sling explorer release 1.0.0: 1) Which of the files I do have to copy to /x1/www/www.apache.org/dist/sling on people.apache.org? All files which are under [1]? If yes, which is the most efficient way to download them all from there (locally I do not have the md5 and sh1 files). Yeah. You should have all the files in your local Maven repository. All the sha1 and md5 files are missing in the local Maven repository, the other files are present. I downloaded the missing files from [1] which is a bit annoying. Any idea why the sha1 and md5 are not present in the local repo? No. I'll try to pay better attention the next time I cut a release. And some further problem: logged in to https://repository.apache.org but Promote is a disabled action, only Release is possible here. Is the description under [2] correct or do I have to use Release here? [2] http://sling.apache.org/site/release-management.html That may have changed with a recent Nexus upgrade. Try it and if the artifacts are on central a few hours from now, you'll know it worked (and then please change the docs). Yes, it changed - Release is now the new function to use. Regards Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: Server Update.js Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: Server Update.js, SLING-1594.patch SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
This is all spam, right? On Oct 29, 2010, at 5:18 PM, Charles L Fields (JIRA) j...@apache.org wrote: [ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles L Fields updated SLING-1594: Attachment: Server Update.js Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: Server Update.js, SLING-1594.patch SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
