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 > > > > > >
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 > > > > >
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] > > > > > > > -- > Fori
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?)
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?)
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
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?)
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]
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: Velocity 1.5 Release - SVN Revision?
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: - 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. - 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. then, once the site is fully updated, i'll remove the old releases (1.4 and 1.5-beta2) from http://www.apache.org/dist/velocity/engine/, and we'll be ready to announce it all. On 3/6/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote: 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 C
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]
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]
[RESULT] [VOTE] Release Velocity Engine 1.5
Ok, i think 12 days is a sufficiently long voting period. Geir & Marino, i can only assume you have no objections. :) +1's from: Nathan Bubna Claude Brisson Malcolm Edgar Will Glass-Husain mailmur Henning Schmiedehausen No other votes were recorded, and there were enough PMC +1s to approve the release. I will push the files out for mirroring and update the site as soon as most mirrors have picked it up. It sounds like the official announcement will not happen until Tuesday, but i believe Velocity Engine 1.5 should be available for download off most mirrors by tomorrow evening. On 2/22/07, Nathan Bubna <[EMAIL PROTECTED]> wrote: Ok, Will has fixed the doc issues that made him -1 the last test build, as well as a minor bug in the new SecureUberspect. All the tests pass, the build looks solid to me, and the included velocity-1.5.jar works just dandy with the VelocityTools example apps. The test build for this release is available at: http://people.apache.org/~nbubna/velocity/engine/1.5/ Please check out the build to make sure i haven't missed anything important and vote regarding your support for releasing this test build as the long-awaited Velocity 1.5: [ ] +1 Let's do it [ ] +0 Have fun; i don't care. [ ] -0 Not sure about this, but i won't stop you. [ ] -1 No, because __ The voting period is typically 72 hours, putting its close time as roughly 10am PST on Saturday, Feb 24th. If i do not find time amidst yardwork that day to finish the release process, then i will do so first thing Monday morning (assuming the vote passes), with the hope that we can announce the release Tuesday morning. My vote is +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Velocity 1.5 Release - SVN Revision?
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] -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (VELOCITY-522) Remove Anakia and Texen from Engine distribution
[ https://issues.apache.org/jira/browse/VELOCITY-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478471 ] Will Glass-Husain commented on VELOCITY-522: I like your plan -- seems a good way of balancing compatibility such a spin-off. No need to screw anyone over. A separate release cycle would probably be good for such dependent projects. If a Torque user has a patch they can create it without having to get involved with the full Velocity . > Remove Anakia and Texen from Engine distribution > > > Key: VELOCITY-522 > URL: https://issues.apache.org/jira/browse/VELOCITY-522 > Project: Velocity > Issue Type: New Feature > Components: Anakia, Build, Texen >Reporter: Will Glass-Husain >Priority: Minor > Fix For: 1.6 > > > I'd like to see us create separate builds and release cycles for Texen and > Anakia now that we are TLP. > ((I thought an issue already existed for this, but couldn't find it) > In particular, Texen seems to have a minimal user base at this point. Be > nice to have a separate release that is stable and mature, take it out of the > Velocity upgrade cycle. If the user community gets excited about it again in > the future, it'll be easy to add features and issue a new release. -- 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?
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?
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]
[jira] Commented: (VELOCITY-522) Remove Anakia and Texen from Engine distribution
[ https://issues.apache.org/jira/browse/VELOCITY-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478429 ] Nathan Bubna commented on VELOCITY-522: --- All that you suggest is how i planned/hoped/wanted to do this from the get-go, with the one exception that i wonder if we really want to remove them in 1.7. If 1.7 is far removed from 1.6, then i think this is fine, but if it follows close on 1.6's heels (e.g. less than 6 months later), then i think it would be kinder to wait until 1.8 to remove them. Of course, we can worry about that when we get there. > Remove Anakia and Texen from Engine distribution > > > Key: VELOCITY-522 > URL: https://issues.apache.org/jira/browse/VELOCITY-522 > Project: Velocity > Issue Type: New Feature > Components: Anakia, Build, Texen >Reporter: Will Glass-Husain >Priority: Minor > Fix For: 1.6 > > > I'd like to see us create separate builds and release cycles for Texen and > Anakia now that we are TLP. > ((I thought an issue already existed for this, but couldn't find it) > In particular, Texen seems to have a minimal user base at this point. Be > nice to have a separate release that is stable and mature, take it out of the > Velocity upgrade cycle. If the user community gets excited about it again in > the future, it'll be easy to add features and issue a new release. -- 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]
[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]
[jira] Resolved: (VELOCITY-517) anchors do not appear in user guide
[
https://issues.apache.org/jira/browse/VELOCITY-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen resolved VELOCITY-517.
-
Resolution: Fixed
Fix Version/s: 1.6
Patch committed to trunk
> anchors do not appear in user guide
> ---
>
> Key: VELOCITY-517
> URL: https://issues.apache.org/jira/browse/VELOCITY-517
> Project: Velocity
> Issue Type: Bug
> Components: Documentation
>Reporter: Will Glass-Husain
> Assigned To: Henning Schmiedehausen
>Priority: Minor
> Fix For: 1.6
>
>
> Note from Will: this is correct in the xdoc source and docs generated with
> "ant docs" -- maybe this is an issue with the Maven build of the site?
> -- Forwarded message --
> From: Egorov Aleksey <[EMAIL PROTECTED]>
> Date: Jan 31, 2007 8:24 AM
> Subject: anchors in doc
> To: dev@velocity.apache.org
> High Developers!
> Strangely.. Relative anchors ("About this Guide", "What is Velocity?",
> "What can Velocity do for me?", etc...) in document
> (http://velocity.apache.org/engine/devel/user-guide.html) don't work at
> all in Firefox 2.0.0.1
> :-\
> Could you please fix this annoying little bug.
> Thanks
> WBR,
> Egorov Alex.
> -- Forwarded message --
> From: Gonzalo Diethelm <[EMAIL PROTECTED]>
> Date: Jan 31, 2007 12:57 PM
> Subject: Re: anchors in doc
> To: Velocity Developers List
> I don't think this is limited to any specific browser / version. I
> viewed the source for that page, and the anchors appear only once in the
> document, in the index. Oops.
> Regards.
> On Wed, 2007-01-31 at 19:24 +0300, Egorov Aleksey wrote:
> > High Developers!
> >
> > Strangely.. Relative anchors ("About this Guide", "What is Velocity?",
> > "What can Velocity do for me?", etc...) in document
> > (http://velocity.apache.org/engine/devel/user-guide.html) don't work at
> > all in Firefox 2.0.0.1
> > :-\
> > Could you please fix this annoying little bug.
> > Thanks
> >
> > WBR,
> > Egorov Alex.
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
--
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]
[jira] Resolved: (VELOCITY-514) Rendering a template with inline macro concurrently causes VM error : Null AST
[
https://issues.apache.org/jira/browse/VELOCITY-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen resolved VELOCITY-514.
-
Resolution: Fixed
Issue is fixed.
> Rendering a template with inline macro concurrently causes VM error : Null AST
> --
>
> Key: VELOCITY-514
> URL: https://issues.apache.org/jira/browse/VELOCITY-514
> Project: Velocity
> Issue Type: Bug
> Components: Engine
>Affects Versions: 1.3.1, 1.4
>Reporter: Sam Chang
> Assigned To: Henning Schmiedehausen
> Fix For: 1.5
>
> Attachments: macroSlammer-1.4.jar, macroSlammer-1.5.jar,
> macroSlammer.jar, nullAST.log, slammer.vm
>
>
> If a template with inline macro is rendered concurrently it prints the
> following errors in the log:
> ERROR [velocity] VM #myInlineMacro: error : too few arguments to macro.
> Wanted 3 got 0
> ERROR [velocity] VM error : myInlineMacro. Null AST
> and where the expected output of the inline macro is, it has the string
> values of the arguments passed to the macro in brackets
> eg:
> #myInlineMacro('Arg1' 'arg2' 'arg3')
> gives the following on above error
> (Arg1 arg2 arg3)
--
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]
[jira] Commented: (VELOCITY-514) Rendering a template with inline macro concurrently causes VM error : Null AST
[
https://issues.apache.org/jira/browse/VELOCITY-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478395
]
Henning Schmiedehausen commented on VELOCITY-514:
-
Ok, so this _is_ VELOCITY-24 . The fix went in between beta-1 and beta-2 and if
he can not reproduce it with beta-2, then it is good. Resolving it for good.
> Rendering a template with inline macro concurrently causes VM error : Null AST
> --
>
> Key: VELOCITY-514
> URL: https://issues.apache.org/jira/browse/VELOCITY-514
> Project: Velocity
> Issue Type: Bug
> Components: Engine
>Affects Versions: 1.3.1, 1.4
>Reporter: Sam Chang
> Assigned To: Henning Schmiedehausen
> Fix For: 1.5
>
> Attachments: macroSlammer-1.4.jar, macroSlammer-1.5.jar,
> macroSlammer.jar, nullAST.log, slammer.vm
>
>
> If a template with inline macro is rendered concurrently it prints the
> following errors in the log:
> ERROR [velocity] VM #myInlineMacro: error : too few arguments to macro.
> Wanted 3 got 0
> ERROR [velocity] VM error : myInlineMacro. Null AST
> and where the expected output of the inline macro is, it has the string
> values of the arguments passed to the macro in brackets
> eg:
> #myInlineMacro('Arg1' 'arg2' 'arg3')
> gives the following on above error
> (Arg1 arg2 arg3)
--
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]
[jira] Resolved: (VELOCITY-524) MD5 files have incorrect format
[ https://issues.apache.org/jira/browse/VELOCITY-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Schmiedehausen resolved VELOCITY-524. - Resolution: Fixed Fix Version/s: 1.6 Fix is in 1.6. Thanks for pointing this out. > MD5 files have incorrect format > --- > > Key: VELOCITY-524 > URL: https://issues.apache.org/jira/browse/VELOCITY-524 > Project: Velocity > Issue Type: Bug > Components: Build >Affects Versions: 1.4, 1.5 beta1, 1.5 beta2 >Reporter: Sebb > Fix For: 1.6 > > > The MD5 files for the Velocity downloads don't have the standard format. > V1.4 > MD5 (velocity-1.4.zip) = 22cbd895f81dd4a6f17665b20b1cbcf71 > V1.5B2 > 5f148e43c1f7c647ec73af0b26ea5ebe > The standard format is: > 5f148e43c1f7c647ec73af0b26ea5ebe *velocity-1.5-beta2.zip > and can readily be autogenerated from Ant using the following snippet: > > > > -- 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]
[jira] Commented: (VELOCITY-522) Remove Anakia and Texen from Engine distribution
[ https://issues.apache.org/jira/browse/VELOCITY-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478377 ] Henning Schmiedehausen commented on VELOCITY-522: - You might want to reconsider this, given the fact that e.g. Torque is a heavy Texen user (actually I think that Texen was specifically invented to be the base of the O/R layer in Turbine that later became Torque). Torque has a big user base and screwing them over would be a Bad Thing (TM). I thought about this for a while and I would suggest the following: - Deprecate all the Texen and Anakia related classes from the main velocity tree. - Factor this code out into org.apache.texen and org.apache.anakia (the package change is intentional to allow them to be used in parallel with all Velocity Releases) - Release these tools immediately (without any further code changes) as anakia-1.0 and texen-1.0. Make it clear to all depending sub-projects that they *must* move to these releases ASAP. - Keep the deprecated classes around for any 1.5.x relase and 1.6 - Remove them in 1.7 and 2.0 - Keep developing Texen and Anakia on their own trees and release early, release often. > Remove Anakia and Texen from Engine distribution > > > Key: VELOCITY-522 > URL: https://issues.apache.org/jira/browse/VELOCITY-522 > Project: Velocity > Issue Type: New Feature > Components: Anakia, Build, Texen >Reporter: Will Glass-Husain >Priority: Minor > Fix For: 1.6 > > > I'd like to see us create separate builds and release cycles for Texen and > Anakia now that we are TLP. > ((I thought an issue already existed for this, but couldn't find it) > In particular, Texen seems to have a minimal user base at this point. Be > nice to have a separate release that is stable and mature, take it out of the > Velocity upgrade cycle. If the user community gets excited about it again in > the future, it'll be easy to add features and issue a new release. -- 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]
[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_12478373 ] Henning Schmiedehausen commented on VELOCITY-521: - Enforcing the version of the compiler might be good to catch errors on the release manager side, however it makes a PITA for anyone that wants to build the release for internal purposes. There are good reasons (we actually recommend it in the README IIRC) to rebuild with 1.3 if you are stuck in a legacy environment. I'd suggest to back that patch out from build.xml and add an internal, non-commented (so that it does not show up in "ant -p") target, e.g. dist-package, that is used by the release manager to build the distribution. I also would like to see this clearly documented in the velocity docs. That is the kind of "last minute rush" patches, that I did want to avoid. That patch should IMHO not have been in the 1.5 release, that would have been good for 1.5.1 or 1.6 > 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]
[jira] Commented: (VELOCITY-517) anchors do not appear in user guide
[
https://issues.apache.org/jira/browse/VELOCITY-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478368
]
Henning Schmiedehausen commented on VELOCITY-517:
-
I already have a patch to fix this for the trunk. Will commit it shortly.
> anchors do not appear in user guide
> ---
>
> Key: VELOCITY-517
> URL: https://issues.apache.org/jira/browse/VELOCITY-517
> Project: Velocity
> Issue Type: Bug
> Components: Documentation
>Reporter: Will Glass-Husain
> Assigned To: Henning Schmiedehausen
>Priority: Minor
>
> Note from Will: this is correct in the xdoc source and docs generated with
> "ant docs" -- maybe this is an issue with the Maven build of the site?
> -- Forwarded message --
> From: Egorov Aleksey <[EMAIL PROTECTED]>
> Date: Jan 31, 2007 8:24 AM
> Subject: anchors in doc
> To: dev@velocity.apache.org
> High Developers!
> Strangely.. Relative anchors ("About this Guide", "What is Velocity?",
> "What can Velocity do for me?", etc...) in document
> (http://velocity.apache.org/engine/devel/user-guide.html) don't work at
> all in Firefox 2.0.0.1
> :-\
> Could you please fix this annoying little bug.
> Thanks
> WBR,
> Egorov Alex.
> -- Forwarded message --
> From: Gonzalo Diethelm <[EMAIL PROTECTED]>
> Date: Jan 31, 2007 12:57 PM
> Subject: Re: anchors in doc
> To: Velocity Developers List
> I don't think this is limited to any specific browser / version. I
> viewed the source for that page, and the anchors appear only once in the
> document, in the index. Oops.
> Regards.
> On Wed, 2007-01-31 at 19:24 +0300, Egorov Aleksey wrote:
> > High Developers!
> >
> > Strangely.. Relative anchors ("About this Guide", "What is Velocity?",
> > "What can Velocity do for me?", etc...) in document
> > (http://velocity.apache.org/engine/devel/user-guide.html) don't work at
> > all in Firefox 2.0.0.1
> > :-\
> > Could you please fix this annoying little bug.
> > Thanks
> >
> > WBR,
> > Egorov Alex.
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
--
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]
[jira] Assigned: (VELOCITY-517) anchors do not appear in user guide
[
https://issues.apache.org/jira/browse/VELOCITY-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen reassigned VELOCITY-517:
---
Assignee: Henning Schmiedehausen
> anchors do not appear in user guide
> ---
>
> Key: VELOCITY-517
> URL: https://issues.apache.org/jira/browse/VELOCITY-517
> Project: Velocity
> Issue Type: Bug
> Components: Documentation
>Reporter: Will Glass-Husain
> Assigned To: Henning Schmiedehausen
>Priority: Minor
>
> Note from Will: this is correct in the xdoc source and docs generated with
> "ant docs" -- maybe this is an issue with the Maven build of the site?
> -- Forwarded message --
> From: Egorov Aleksey <[EMAIL PROTECTED]>
> Date: Jan 31, 2007 8:24 AM
> Subject: anchors in doc
> To: dev@velocity.apache.org
> High Developers!
> Strangely.. Relative anchors ("About this Guide", "What is Velocity?",
> "What can Velocity do for me?", etc...) in document
> (http://velocity.apache.org/engine/devel/user-guide.html) don't work at
> all in Firefox 2.0.0.1
> :-\
> Could you please fix this annoying little bug.
> Thanks
> WBR,
> Egorov Alex.
> -- Forwarded message --
> From: Gonzalo Diethelm <[EMAIL PROTECTED]>
> Date: Jan 31, 2007 12:57 PM
> Subject: Re: anchors in doc
> To: Velocity Developers List
> I don't think this is limited to any specific browser / version. I
> viewed the source for that page, and the anchors appear only once in the
> document, in the index. Oops.
> Regards.
> On Wed, 2007-01-31 at 19:24 +0300, Egorov Aleksey wrote:
> > High Developers!
> >
> > Strangely.. Relative anchors ("About this Guide", "What is Velocity?",
> > "What can Velocity do for me?", etc...) in document
> > (http://velocity.apache.org/engine/devel/user-guide.html) don't work at
> > all in Firefox 2.0.0.1
> > :-\
> > Could you please fix this annoying little bug.
> > Thanks
> >
> > WBR,
> > Egorov Alex.
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
--
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]
[jira] Resolved: (VELOCITY-516) SecureUberspector doesn't work with #foreach (iterators)
[
https://issues.apache.org/jira/browse/VELOCITY-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen resolved VELOCITY-516.
-
Resolution: Fixed
Nah, better use a sub-issue.
> SecureUberspector doesn't work with #foreach (iterators)
>
>
> Key: VELOCITY-516
> URL: https://issues.apache.org/jira/browse/VELOCITY-516
> Project: Velocity
> Issue Type: Bug
> Components: Engine
>Affects Versions: 1.5 beta2
>Reporter: Vincent Massol
> Assigned To: Henning Schmiedehausen
>Priority: Critical
> Fix For: 1.5
>
>
> When using a #foreach iterating over strings I get: "Cannot retrieve iterator
> from object of class [Ljava.lang.String; due to security restrictions."
> The reason is that in the SecureUberspector class there's a call to
> checkObjectExecutePermission() with the second parameter being null. And in
> checkObjectExecutePermission() there's:
> {code}
> if (methodName == null)
> {
> return false;
> }
> {code}
--
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]
[jira] Created: (VELOCITY-525) Clean up the logic in SecureIntrospectorImpl to be more readable.
Clean up the logic in SecureIntrospectorImpl to be more readable. - Key: VELOCITY-525 URL: https://issues.apache.org/jira/browse/VELOCITY-525 Project: Velocity Issue Type: Sub-task Components: Engine Reporter: Henning Schmiedehausen Assigned To: Henning Schmiedehausen Priority: Minor Fix For: 1.6 Clean up the logic in SecureIntrospectorImpl to be more readable. -- 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]
[jira] Reopened: (VELOCITY-516) SecureUberspector doesn't work with #foreach (iterators)
[
https://issues.apache.org/jira/browse/VELOCITY-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen reopened VELOCITY-516:
-
Assignee: Henning Schmiedehausen
I have to admit that I do not like the patch. It works, yes, but the addition
of random "methodName != null" into if-statements leads to unreadable code in
the end.
Some reshuffling would do the code good. I'll reopen this as a reminder for me
for 1.6.
> SecureUberspector doesn't work with #foreach (iterators)
>
>
> Key: VELOCITY-516
> URL: https://issues.apache.org/jira/browse/VELOCITY-516
> Project: Velocity
> Issue Type: Bug
> Components: Engine
>Affects Versions: 1.5 beta2
>Reporter: Vincent Massol
> Assigned To: Henning Schmiedehausen
>Priority: Critical
> Fix For: 1.5
>
>
> When using a #foreach iterating over strings I get: "Cannot retrieve iterator
> from object of class [Ljava.lang.String; due to security restrictions."
> The reason is that in the SecureUberspector class there's a call to
> checkObjectExecutePermission() with the second parameter being null. And in
> checkObjectExecutePermission() there's:
> {code}
> if (methodName == null)
> {
> return false;
> }
> {code}
--
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]
