[jira] Commented: (VELOCITY-521) please do not force to use JDK 1.4 for running the package target in build.xml
[ https://issues.apache.org/jira/browse/VELOCITY-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478428 ] Will Glass-Husain commented on VELOCITY-521: ok, I'll pull it out. it seemed like a good idea at the time. I'd assumed that ant dist was only used by the release manager. please do not force to use JDK 1.4 for running the package target in build.xml -- Key: VELOCITY-521 URL: https://issues.apache.org/jira/browse/VELOCITY-521 Project: Velocity Issue Type: Bug Components: Build Affects Versions: 1.6 Environment: all Reporter: Antoine Levy-Lambert Assigned To: Will Glass-Husain Priority: Minor Fix For: 1.6 Attachments: patch.txt build.xml target package forces to use exactly JDK 1.4. Would it not be better to build with target=1.4, source=1.4 and to simply check that the JDK version is = 1.4 I will attach a patch to this effect. Regards, Antoine -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Velocity 1.5 Release - SVN Revision?
I've got to rush out the door to a meeting, but i'll be back in an hour or so. Then i'll comment further, tally the votes and get things moving. And yes, i'm all for a 1.5.1. no shame in that. On 3/6/07, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote: Nathan Bubna [EMAIL PROTECTED] writes: My vote is reluctantly +1, because the I want to get it out weights more for me than the issues that I have found: BTW: Strictly spoken are the references in the POM wrong because they should not reference .../branches/VELOCITY_1.5_BRANCH/ but .../tags/VELOCITY_1.5/ They aren't wrong unless/until we do further dev on the branch, in which case, we should do a 1.5.x release. So, it hardly matters. Yes, it does. If we do further development, then trying to rebuild the site from the release package will give different results. Which probably does not matter much, but it would matter to me. IMHO we will at least have an 1.5.1 to fix the issues listed below: This means that rebuilding 1.5 from source will actually be difficult, once we think about 1.5.1. This is my bad and I intended to fix it before the 1.5 release; however Nathan CfV'ed before I returned from holidays and the voting period is already over. Not too late to vote. 72 hours was the minimum voting period. I'm managing this release, the vote is over when i send a result. Uhm. Don't tempt me. While I'm fed up with delaying and want to have that bugger out, here is what I've found: a) The link problem with the maven site. I have a patch for the guides which will go into trunk shortly. b) The checksum thing. Fixed on the trunk c) The package build thing (restrict on 1.4). I've put a patch on the trunk which might need more discussion. d) The POM references to the branch, not the tag. Considering the fact that Will -1'ed the last release attempt for a documentation issue, personally I'd weight at least d) much more than that. However, I believe that we can release a 1.5.1 4-6 weeks after 1.5 to amend that, so I will not block this vote. I would very much suggest that we target the next tuesday for the official release announcement. This gives us and the mirrors a few days to get our acts together. Lets push this out. Now! Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person|eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fürth, HRB 7350|a s Sitz der Gesellschaft: Buckenhof. Geschäftsführer: Henning Schmiedehausen |n Save the cheerleader. Save the world. - 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]
Re: Velocity 1.5 Release - SVN Revision?
On 3/6/07, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote: Nathan Bubna [EMAIL PROTECTED] writes: My vote is reluctantly +1, because the I want to get it out weights more for me than the issues that I have found: BTW: Strictly spoken are the references in the POM wrong because they should not reference .../branches/VELOCITY_1.5_BRANCH/ but .../tags/VELOCITY_1.5/ They aren't wrong unless/until we do further dev on the branch, in which case, we should do a 1.5.x release. So, it hardly matters. Yes, it does. If we do further development, then trying to rebuild the site from the release package will give different results. Which probably does not matter much, but it would matter to me. i don't see why rebuilding using the source in the release would produce a result different than itself. and what does the site have to do with this? just trying to understand... IMHO we will at least have an 1.5.1 to fix the issues listed below: This means that rebuilding 1.5 from source will actually be difficult, once we think about 1.5.1. This is my bad and I intended to fix it before the 1.5 release; however Nathan CfV'ed before I returned from holidays and the voting period is already over. Not too late to vote. 72 hours was the minimum voting period. I'm managing this release, the vote is over when i send a result. Uhm. Don't tempt me. While I'm fed up with delaying and want to have that bugger out, here is what I've found: a) The link problem with the maven site. I have a patch for the guides which will go into trunk shortly. b) The checksum thing. Fixed on the trunk c) The package build thing (restrict on 1.4). I've put a patch on the trunk which might need more discussion. d) The POM references to the branch, not the tag. Considering the fact that Will -1'ed the last release attempt for a documentation issue, personally I'd weight at least d) much more than that. However, I believe that we can release a 1.5.1 4-6 weeks after 1.5 to amend that, so I will not block this vote. thank you. it's about time we stopped fretting over minor issues in the build and documentation. the goal is always perfection, but the requirement is merely high quality (especially, higher quality than the previous GA release, which we achieved ages ago). I would very much suggest that we target the next tuesday for the official release announcement. This gives us and the mirrors a few days to get our acts together. Will or you can do the official announcement whenever you like. in the meantime, i'll do the result, the push to the mirrors, and the site update ASAP. Lets push this out. Now! Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person|eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fürth, HRB 7350|a s Sitz der Gesellschaft: Buckenhof. Geschäftsführer: Henning Schmiedehausen |n Save the cheerleader. Save the world. - 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]
Re: Velocity 1.5 Release - SVN Revision?
The site uses the given parameters from the pom to e.g. generate the activity and changes report. These will change over time as the branch moves forward. The tag will never move and thus always report the same activity and changes report. As I said, this is more of a this is not really correct than a user visible issue. Best regards Henning On Tue, 2007-03-06 at 08:38 -0800, Nathan Bubna wrote: On 3/6/07, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote: Nathan Bubna [EMAIL PROTECTED] writes: My vote is reluctantly +1, because the I want to get it out weights more for me than the issues that I have found: BTW: Strictly spoken are the references in the POM wrong because they should not reference .../branches/VELOCITY_1.5_BRANCH/ but .../tags/VELOCITY_1.5/ They aren't wrong unless/until we do further dev on the branch, in which case, we should do a 1.5.x release. So, it hardly matters. Yes, it does. If we do further development, then trying to rebuild the site from the release package will give different results. Which probably does not matter much, but it would matter to me. i don't see why rebuilding using the source in the release would produce a result different than itself. and what does the site have to do with this? just trying to understand... IMHO we will at least have an 1.5.1 to fix the issues listed below: This means that rebuilding 1.5 from source will actually be difficult, once we think about 1.5.1. This is my bad and I intended to fix it before the 1.5 release; however Nathan CfV'ed before I returned from holidays and the voting period is already over. Not too late to vote. 72 hours was the minimum voting period. I'm managing this release, the vote is over when i send a result. Uhm. Don't tempt me. While I'm fed up with delaying and want to have that bugger out, here is what I've found: a) The link problem with the maven site. I have a patch for the guides which will go into trunk shortly. b) The checksum thing. Fixed on the trunk c) The package build thing (restrict on 1.4). I've put a patch on the trunk which might need more discussion. d) The POM references to the branch, not the tag. Considering the fact that Will -1'ed the last release attempt for a documentation issue, personally I'd weight at least d) much more than that. However, I believe that we can release a 1.5.1 4-6 weeks after 1.5 to amend that, so I will not block this vote. thank you. it's about time we stopped fretting over minor issues in the build and documentation. the goal is always perfection, but the requirement is merely high quality (especially, higher quality than the previous GA release, which we achieved ages ago). I would very much suggest that we target the next tuesday for the official release announcement. This gives us and the mirrors a few days to get our acts together. Will or you can do the official announcement whenever you like. in the meantime, i'll do the result, the push to the mirrors, and the site update ASAP. Lets push this out. Now! Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fürth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschäftsführer: Henning Schmiedehausen |n Save the cheerleader. Save the world. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Velocity 1.5 Release - SVN Revision?
The non-working links on the dev-guide and user-guide page have already been mentioned by at least one user. If one builds the release web site from the source, then these will be very prominently visible. I will doctor the links for the release, though. :-) Best regards Henning On Tue, 2007-03-06 at 08:40 -0800, Will Glass-Husain wrote: Good catches. A missing doc page and bad link would have been immediately visible to the casual user, while you are pointing more subtle flaws. Likely no one will actually notice the POM issue, especially if we follow with a 1.5.1 release. Looking forward to starting a discussion about future Road Map. I made some edits on the Wiki a few weeks ago. WILL On 3/6/07, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote: Nathan Bubna [EMAIL PROTECTED] writes: My vote is reluctantly +1, because the I want to get it out weights more for me than the issues that I have found: BTW: Strictly spoken are the references in the POM wrong because they should not reference .../branches/VELOCITY_1.5_BRANCH/ but .../tags/VELOCITY_1.5/ They aren't wrong unless/until we do further dev on the branch, in which case, we should do a 1.5.x release. So, it hardly matters. Yes, it does. If we do further development, then trying to rebuild the site from the release package will give different results. Which probably does not matter much, but it would matter to me. IMHO we will at least have an 1.5.1 to fix the issues listed below: This means that rebuilding 1.5 from source will actually be difficult, once we think about 1.5.1. This is my bad and I intended to fix it before the 1.5 release; however Nathan CfV'ed before I returned from holidays and the voting period is already over. Not too late to vote. 72 hours was the minimum voting period. I'm managing this release, the vote is over when i send a result. Uhm. Don't tempt me. While I'm fed up with delaying and want to have that bugger out, here is what I've found: a) The link problem with the maven site. I have a patch for the guides which will go into trunk shortly. b) The checksum thing. Fixed on the trunk c) The package build thing (restrict on 1.4). I've put a patch on the trunk which might need more discussion. d) The POM references to the branch, not the tag. Considering the fact that Will -1'ed the last release attempt for a documentation issue, personally I'd weight at least d) much more than that. However, I believe that we can release a 1.5.1 4-6 weeks after 1.5 to amend that, so I will not block this vote. I would very much suggest that we target the next tuesday for the official release announcement. This gives us and the mirrors a few days to get our acts together. Lets push this out. Now! Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fürth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschäftsführer: Henning Schmiedehausen |n Save the cheerleader. Save the world. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Releasing it (was: Re: Velocity 1.5 Release - SVN Revision?)
On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/, but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH \ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. - Deploy the release to the maven repo. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing it (was: Re: Velocity 1.5 Release - SVN Revision?)
On 3/6/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. that'd be good. if you haven't noticed, i've had to disable the news macro and roughly mimic it's results by hand. if you can make it work properly, i think that would be preferable. of course, i do want us to figure out how to make it work fully for others besides you, but we can do that later. :) - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? yep. updated the download page, the doap descriptor, the front page and the menu sidebar thing. - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/, but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. let me give this part a try. i haven't done this yet and would like to see it work for me. - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH \ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 yeah, i saw that. thanks. for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. that's to be expected. revision numbers are only updated in files which are changed and which have the $Id$ thingy in 'em. - Deploy the release to the maven repo. another thing i've never done. i presume there's a magic maven command for this too? Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing it (was: Re: Velocity 1.5 Release - SVN Revision?)
On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. that'd be good. if you haven't noticed, i've had to disable the news macro and roughly mimic it's results by hand. if you can make it work properly, i think that would be preferable. of course, i do want us to figure out how to make it work fully for others besides you, but we can do that later. ok, i deployed the site using the site module as it is in svn (with the news macro disabled and hand-mimicked). you're of course still quite welcome to re-update with the news macro working, and to fix and bad in-page anchors or whatever. so, the public now has access to Velocity 1.5 from our download page, if they happen to visit the web site before the announcements go out by email. - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? yep. updated the download page, the doap descriptor, the front page and the menu sidebar thing. - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/, but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. let me give this part a try. i haven't done this yet and would like to see it work for me. it appears to have worked just fine... - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH \ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 yeah, i saw that. thanks. for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. that's to be expected. revision numbers are only updated in files which are changed and which have the $Id$ thingy in 'em. - Deploy the release to the maven repo. another thing i've never done. i presume there's a magic maven command for this too? i think this last item and the email announcements are all that's left to be done. Will said he'd handle the PR. Anyone who wants to deploy 1.5 to the maven repo or tell me how to do it is welcome to do so. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing it (was: Re: Velocity 1.5 Release - SVN Revision?)
By the way, this is tremendously exciting. WILL On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. that'd be good. if you haven't noticed, i've had to disable the news macro and roughly mimic it's results by hand. if you can make it work properly, i think that would be preferable. of course, i do want us to figure out how to make it work fully for others besides you, but we can do that later. ok, i deployed the site using the site module as it is in svn (with the news macro disabled and hand-mimicked). you're of course still quite welcome to re-update with the news macro working, and to fix and bad in-page anchors or whatever. so, the public now has access to Velocity 1.5 from our download page, if they happen to visit the web site before the announcements go out by email. - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? yep. updated the download page, the doap descriptor, the front page and the menu sidebar thing. - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/, but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. let me give this part a try. i haven't done this yet and would like to see it work for me. it appears to have worked just fine... - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH\ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 yeah, i saw that. thanks. for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. that's to be expected. revision numbers are only updated in files which are changed and which have the $Id$ thingy in 'em. - Deploy the release to the maven repo. another thing i've never done. i presume there's a magic maven command for this too? i think this last item and the email announcements are all that's left to be done. Will said he'd handle the PR. Anyone who wants to deploy 1.5 to the maven repo or tell me how to do it is welcome to do so. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
Re: Releasing it (was: Re: Velocity 1.5 Release - SVN Revision?)
I don't mind much either way, but i was given the impression from previous discussion that first thing Tuesday morning (presumably east coast time) was the ideal time for that. On 3/6/07, Will Glass-Husain [EMAIL PROTECTED] wrote: Do you want me to send the email announcements? I can do this tonight. WILL On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. that'd be good. if you haven't noticed, i've had to disable the news macro and roughly mimic it's results by hand. if you can make it work properly, i think that would be preferable. of course, i do want us to figure out how to make it work fully for others besides you, but we can do that later. ok, i deployed the site using the site module as it is in svn (with the news macro disabled and hand-mimicked). you're of course still quite welcome to re-update with the news macro working, and to fix and bad in-page anchors or whatever. so, the public now has access to Velocity 1.5 from our download page, if they happen to visit the web site before the announcements go out by email. - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? yep. updated the download page, the doap descriptor, the front page and the menu sidebar thing. - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/, but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. let me give this part a try. i haven't done this yet and would like to see it work for me. it appears to have worked just fine... - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH\ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 yeah, i saw that. thanks. for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. that's to be expected. revision numbers are only updated in files which are changed and which have the $Id$ thingy in 'em. - Deploy the release to the maven repo. another thing i've never done. i presume there's a magic maven command for this too? i think this last item and the email announcements are all that's left to be done. Will said he'd handle the PR. Anyone who wants to deploy 1.5 to the maven repo or tell me how to do it is welcome to do so. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing it (was: Re: Velocity 1.5 Release - SVN Revision?)
Fair enough. Let's do the internal and external announcements at the same time then. WILl On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: I don't mind much either way, but i was given the impression from previous discussion that first thing Tuesday morning (presumably east coast time) was the ideal time for that. On 3/6/07, Will Glass-Husain [EMAIL PROTECTED] wrote: Do you want me to send the email announcements? I can do this tonight. WILL On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. that'd be good. if you haven't noticed, i've had to disable the news macro and roughly mimic it's results by hand. if you can make it work properly, i think that would be preferable. of course, i do want us to figure out how to make it work fully for others besides you, but we can do that later. ok, i deployed the site using the site module as it is in svn (with the news macro disabled and hand-mimicked). you're of course still quite welcome to re-update with the news macro working, and to fix and bad in-page anchors or whatever. so, the public now has access to Velocity 1.5 from our download page, if they happen to visit the web site before the announcements go out by email. - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? yep. updated the download page, the doap descriptor, the front page and the menu sidebar thing. - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/, but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. let me give this part a try. i haven't done this yet and would like to see it work for me. it appears to have worked just fine... - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH\ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 yeah, i saw that. thanks. for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. that's to be expected. revision numbers are only updated in files which are changed and which have the $Id$ thingy in 'em. - Deploy the release to the maven repo. another thing i've never done. i presume there's a magic maven command for this too? i think this last item and the email announcements are all that's left to be done. Will said he'd handle the PR. Anyone who wants to deploy 1.5 to the maven repo or tell me how to do it is welcome to do so. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
Re: Releasing it (was: Re: Velocity 1.5 Release - SVN Revision?)
By which I mean, the Apache announcement lists and the press release together early next week. We should tell the user list right away. WILL On 3/6/07, Will Glass-Husain [EMAIL PROTECTED] wrote: Fair enough. Let's do the internal and external announcements at the same time then. WILl On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: I don't mind much either way, but i was given the impression from previous discussion that first thing Tuesday morning (presumably east coast time) was the ideal time for that. On 3/6/07, Will Glass-Husain [EMAIL PROTECTED] wrote: Do you want me to send the email announcements? I can do this tonight. WILL On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. that'd be good. if you haven't noticed, i've had to disable the news macro and roughly mimic it's results by hand. if you can make it work properly, i think that would be preferable. of course, i do want us to figure out how to make it work fully for others besides you, but we can do that later. ok, i deployed the site using the site module as it is in svn (with the news macro disabled and hand-mimicked). you're of course still quite welcome to re-update with the news macro working, and to fix and bad in-page anchors or whatever. so, the public now has access to Velocity 1.5 from our download page, if they happen to visit the web site before the announcements go out by email. - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? yep. updated the download page, the doap descriptor, the front page and the menu sidebar thing. - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/ , but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. let me give this part a try. i haven't done this yet and would like to see it work for me. it appears to have worked just fine... - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH\ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 yeah, i saw that. thanks. for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. that's to be expected. revision numbers are only updated in files which are changed and which have the $Id$ thingy in 'em. - Deploy the release to the maven repo. another thing i've never done. i presume there's a magic maven command for this too? i think this last item and the email announcements are all that's left to be done. Will said he'd handle the PR. Anyone who wants to deploy 1.5 to the maven repo or tell me how to do it is welcome to do so. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Forio Business Simulations Will Glass-Husain
Re: Releasing it (was: Re: Velocity 1.5 Release - SVN Revision?)
Hi, thanks for doing this! It seems that this process is still a bit rough and it is one of my top priorities to get this smoother and that we can run it from the zone. I've did a minor update on the main page, there was still 1.4 as release and 1.5 beta 2 as beta listed. I noticed that for the site, the pages that go through the velocity/doxia renderer did not get updated (they still had 1.4 as release), so I assume that this is one of the rough edges. Will look into this. Also for the Engine site, the JIRA report listed only a few issues, this might be a problem with the jira report plugin (I've contributed lots of fixes here). I've deployed both sites again, they should be fine now. Best regards Henning On Tue, 2007-03-06 at 17:27 -0800, Nathan Bubna wrote: On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. that'd be good. if you haven't noticed, i've had to disable the news macro and roughly mimic it's results by hand. if you can make it work properly, i think that would be preferable. of course, i do want us to figure out how to make it work fully for others besides you, but we can do that later. ok, i deployed the site using the site module as it is in svn (with the news macro disabled and hand-mimicked). you're of course still quite welcome to re-update with the news macro working, and to fix and bad in-page anchors or whatever. so, the public now has access to Velocity 1.5 from our download page, if they happen to visit the web site before the announcements go out by email. - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? yep. updated the download page, the doap descriptor, the front page and the menu sidebar thing. - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/, but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. let me give this part a try. i haven't done this yet and would like to see it work for me. it appears to have worked just fine... - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH \ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 yeah, i saw that. thanks. for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. that's to be expected. revision numbers are only updated in files which are changed and which have the $Id$ thingy in 'em. - Deploy the release to the maven repo. another thing i've never done. i presume there's a magic maven command for this too? i think this last item and the email announcements are all that's left to be done. Will said he'd handle the PR. Anyone who wants to deploy 1.5 to the maven repo or tell me how to do it is welcome to do so. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy
