Sasvata (Shash) Chatterjee wrote:
I haven't had a chance yet to fix the "default" alias in CVS, I
should've mentioned that.
Until then it is manual checkouts as you are doing now. As soon as I
know that the
default dist. is working, I'll fix that alias.
Ok. According to my experience, the new package group is set
at the 21 packages listed below. When you do update this in CVS,
would you please Email me the instructions for doing this or put
them on a Wiki page? I would like to learn how to setup this type
of alias.
*** Note:
I also got a duplicate entry in the CLASSPATH error on the svc-crypt-des
module, which once I removed the JCE_LIB from it's CLASSPATH seemed to
resolve the issue.
I'll close my eyes and through my paranormal powers deduce that you
(like me) have moved
on to the 3.0-series of Eclipse. Eclipse 2.x had a bug, it didn't
automatically mount JARs from
the JRE lib dir, so we had to manually do it. 3.0 has it fixed. But if
we remove the JCE from the
.classpath, Eclipse-2.x (released) users will have a problem. I decided
to leave it alone in CVS
and just fix it manually on my Eclipse installation.
Well, you should have closed your eyes tighter and you would have
deduced that I am still on Eclipse 2.1.1. I have not had time to
do the monthly update all summer; perhaps now that we're entering
Fall... Please forgive me O Great Seer of my Hard Drive. <G>
I think I understand what you're saying, but is there a way to
resolve it for both versions of Eclipse? I'm guessing not or
you would have already done that. Hmmm... There has to be a
better way...
Therefore, it appears the "minimal" install is these modules:
app-crud
app-navigate
app-poll
app-register
app-security
clnt-struts
keel-build
keel-core
keel-server
svc-authentication-persist
svc-authorization-persist
svc-cache-excalibur
svc-crypto-base64
svc-crypto-des
svc-event-defaultevent
svc-filter-filters
svc-mail-javamail
svc-model-defaultmodel
svc-password-jpassgen
svc-persist-default
tool-xdoclet
This is the correct list, but not truly the "minimal" list. This list
is needed because if you look in default-deploy.properties, that's what
we have listed in there as required modules. The minimal
list might actually be much smaller, and we can only tell by removing
declarations of components
in *.xconf, and trying to start/access Keel. For all I know, we could
get by with just
keel-build, keel-core, keel-server and tool-xdoclet, depending on what
services/apps you as the user
implemented or needed.
I suspected as much but have not had a chance to wade through the
.xconf files. Not to volunteer anyone, but this sounds like a job
tailor made for the Pete'ster. But then I know he's been working
a Zillion hours lately and doesn't have time.
Shash, I seem to remember a note not that long ago that tools-xdoclet
would be going away. Am I imagining that or just confused as to what
was actually meant?
--
Thanks,
Derek Lane
=====================================
--- The Gunslinger
[EMAIL PROTECTED]
http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
