Hi James,
(Not sure whether somebody from the developer team already answered, but
better twice than not at all...)
In general, attaching the source code including tests to the JIRA issue is
fine. Somebody (probably me or Rob) will review that code and commit it to
CVS HEAD (typically to the sandbox while it's not intended for release yet).
However, this might take a while, since we have a number of issues to
address for the 2.0.2 release first... Major new features typically have to
wait for 2.1, so any issues with sandbox code have lower priority.
Juergen
-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of ja...@ti...
Sent: Sunday, December 03, 2006 6:50 PM
To: spr...@li...
Subject: [Springframework-developer] Any way I can check in code to CVS?
I've made improvements to the Dynamic Lanaguage Support for JavaScript.
The fixes include:
-Method calls to JavaScript-backed beans automaticly return the correct
class type, rather than just Proxy.
-<lang:javascript> now supported
So... How can I get the source code checked into CVS? I'd attach the
sources to the issue (SPR-1933) like I did last time, but that's kind of
painful. (I never attached the unit tests and their supporting files last
time, for example.)
I'd be happy to email the files to someone with CVS commit rights if getting
my own account isn't possible.
Please advise,
James Tikalsky
Fort Worth, TX
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
