Ah, that was easy :)
It's going to take me a fair amount of time to get up to speed, but
that's one hurdle down at least... 5,000 more to go :)
Frank
Craig McClanahan wrote:
On 7/15/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
Ok, here's the first stupid question Craig...
Where is the source repository? Is it CVS or SVN at this point? I
looked around the Shale page off the Struts site, but didn't see any
info on it. I did see the link for the nightlies, but is that would I
should be going after? Thanks!
Shale is in the Struts repository in subversion. The simplest way to
deal with things is to grab the entire "current" Subversion tree (as
described on the "Acquiring" page):
* http://struts.apache.org/acquiring.html
I like to use the SVN source that checks out all the subprojects at once:
http://svn.apache.org/repos/asf/struts/current
which, if you do so, will create a directory structure (with a couple
of top level subdirectories detailed) including the following:
apps/
dao/ (Contains the shared pseudo-database stuff)
bsf
build
core
el
faces
flow
mock
plugins
sandbox/
artimus/
build/
mailreader-chain/
overdive/
scaffold/
struts-jericho/
tag-doc/
tiles/
workflow/
xdocs/
shale/
clay-plugin/
core-library/
mail-reader/ (Contains the beginnings of the sources, but don't
bother with them)
test-framework/
use-cases/
taglib
tiles
For the Shale stuff, there are no milestone or release builds yet ...
if you want binaries, then the latest nightlies are the way to go.
Frank
Craig
Craig McClanahan wrote:
On 7/15/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
Must... not... volunteer... time... limited... :)
Seriously, I would actually be quite interested in taking this on, but
frankly I have not yet touched Shale at all, so I'm not certain I could
pull it off... Certainly I couldn't guarantee that I'd do everything the
*right* way :)
Tell you what though... if no one else more familiar with Shale and with
more free time steps up to do it, I'd like to take a shot none the less.
That is Craig, if you don't mind a lot of questions along the way :)
That would be great! Go for it! And feel free to ask away along the
way ... (probably on the dev list would be best).
One thing that can save some work is that the pseudo-database part of
MailReader is already extracted out into its own module (it's in
apps/dao in the source tree), which can be reused "as is" like it is
in all the other MailReader variants.
Frank W. Zammetti
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
---------------------------------------------------------------------
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]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
