Hi Dishara. You'll notice in the specs that some parts are optional. Don't consider them if they imply a deep refactoring of Velocity (which we don't really want, to be honest...). For now, we're just talking feasibility. What can we reach with simple wrappers around Velocity objects, with the minimum refactoring?
From this page: http://jcp.org/aboutJava/communityprocess/final/jsr223/index.html It seems like the TCK itself is not freely available. Well, it is said to be "available to Qualified Not-for-Profits and Qualified Individuals for no charge", but certainly not open source. So you can use it for your own tests if you want, but we'll need to have our own test cases. > What are the main Velocity back end API will be used for this ? Mainly, org.apache.velocity.Template org.apache.velocity.VelocityContext org.apache.velocity.app.VelocityEngine Claude On Tue, 27 Mar 2012 22:34:13 +0530 Dishara Wijewardana <[email protected]> wrote: > On Tue, Mar 27, 2012 at 2:34 PM, Claude Brisson <[email protected]> > wrote: > > > Hi Dishara. > > > > We are pleased with your proposal and ready to mentor you. I'm still > > waiting for my mentoring request to be processed by Google and > > Apache, so stay tuned, I'll keep you informed. > > > > Claude Brisson > > > > > Hi Claude, > > Thank you very much for the response and for the trust on me. Willing > to contribute to this project with great confidence. > I will keep in touch and also continue regarding the spec. Also I'am > already started looking in to velocity back end code w.r.t JSR > 223.(still if some specific details can be shared regarding this will > be useful). > > While doing so, I will also start writing a proposal. > > Thanks in Advance > > > > On Sun, 25 Mar 2012 21:08:29 +0530 > > Dishara Wijewardana <[email protected]> wrote: > > > > > Hi all, > > > I am a student who likes to take part in GSoC 2012 and I am really > > > interested in implementing a JSR spec which is always an > > > interesting task to do. . > > > I think this implementation will give a better value addition to > > > Velocity as it has a industry standard support in back_end and > > > will allows JSR 223 clients who likes Velocity to migrate without > > > much effort I am willing to contribute this wonderful project > > > idea (which as since last couple of years as seems) and continue > > > the contribution further on Velocity. > > > > > > Hi Vincent, > > > I couldn't reach to the links you provided in the JIRA[1] > > > regarding this idea. I think the content has been removed . > > > > > > Hi Thomas, > > > But I went through the specification and also downloaded the doc. > > > Is it expected to implement the whole spec. I mean making > > > VELOCITY a 100% compliant of JSR 223 ? > > > It will be great if I can get to know the scope of the project and > > > some more detail regarding the $subject so that I can understand > > > the project in nutshell. > > > (i.e is it expected to test the whole impl with the 223 TCK ? > > > What are the main Velocity back end API will be used for this ? > > > and etc). > > > > > > So that I can read the most important parts of the spec first and > > > start working on a patch before GSoC application period ends. > > > Thanks in Advance > > > > > > JSR 223 spec - [2] > > > spec documentation - [3] > > > > > > [1] - https://issues.apache.org/jira/browse/VELOCITY-735 > > > [2] - > > > http://download.oracle.com/otndocs/jcp/sjp-1_1-pr2-spec-oth-JSpec/ > > > [3] - > > > http://download.oracle.com/otndocs/jcp/sjp-1_1-pr2-oth-doc-JSpec/ > > > > > > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
