On Monday, October 16, 2000, at 01:20 PM, Charles Benett wrote:
> Welcome!
>
> Stuart Roebuck wrote:
> >
> > The title says it - I'm just starting to take a look at Apache James.
> >
> > Apologies if I've missed something obvious somewhere, but I have tried searching
>the
> mail archives and looking at the included and online documentation.
> >
> > Firstly, I've had trouble identifying the correct CVSROOT for the Apache James CVS
> server, and the necessary username and password for read-only access. The general
>Apache
> Java pages on CVS access don't specifically mention James, and my attempts at
>altering
> their CVSROOTs to match didn't work.
>
> That webpage is a bit confusing (but strictly speaking correct), have
> you tried:
> :pserver:[EMAIL PROTECTED]:/products/cvs/master,
> with password jservpub then cvs checkout james?
>
Thanks for this - I tried again just before your email arrived. I must have typed
something wrong yesterday.
> >
> > Secondly, I tried compiling the daily build for 14 October
>
> this is news to me - I didn't think we did daily builds. Were did you
> find it?
I found a reference to it in an email when I was searching the recent archives. The
address was:
http://www.working-dogs.com/daily/
But it seems to be down at the moment unless I've typed that wrong too!!
> > and had problems with references to javax.naming.* where does this package come
>from? > I
> presume there is some library that I haven't installed or isn't being included in my
> >classpath. Regarding daily builds, the daily build site seems to be down at the
>moment.
>
> javax.naming.* are the JNDI packages. They are included with Java 2 v1.3
> but are additional for Java 2 1.2. Only required for optional LDAP user
> directory.
> Short term fixes:
> 1) get JNDI.jar from Sun
> 2) delete org.apache.james.userrepository.UsersLDAPRepository from your
> copy of source.
> Long term fixes:
> 1) We offer jndi.jar on apache site (don't know if this is allowed)
> 2) I try to make the build file conditional
>
>
> I've just made some other fixes to cvs, so subject to jndi it should
> build and run (at least as far as initialising)
>
> You may want to play with the older distribution, James 1.1b1, until 1.2
> is released (hopefully not too long)
I ran into difficulties with the shell script on the 1.1b1 distribution and noticed
subsequent fixes mentioned in the mail archives, so I decided to try the current CVS.
> Regards,
> Charles
Thanks again. I'm downloading JNDI as we speak - I'm running on a MacOS X Beta which
has Java 1.2.2SE within a 1.3 Hotspot VM, so JNDI isn't in there as standard.
How about a non-technical solution to the JNDI requirement... adding two lines to the
"Requirements" in the "README" file which just say:
- JNDI 1.2 (not included in distribution but standard in Java EE 1.2 or SE 1.3)
Download from Sun at http://java.sun.com/products/jndi/index.html
Stuart.
-------------------------------------------------------------------------
Stuart Roebuck, BSc, MBA Tel.: 0131 228 4853 / Fax.: 0870 054 8322
Managing Director Alpha Numeric Pager: 07654 588898
ADOLOS http://www.adolos.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
