Hello everybody,
I have the same proble. I used to add my jars into the conf/lib
repository of James 3 Beta 3 and it worked very well, so when I migrated
on Beta 4 I did the same, but it refuses to pick up them. I tried to put
my jars into the /conf/lib repository and the /lib/ repository, and
almost every where, but impossible to run James Beta 4. I absolutely
didn't change anything to the name or the classpath of my own matchers
and mailets.
Does anybody encountered and resolved this problem ?
Thank you so much.
Audrey
Le 31/03/2012 10:47, Eric Charles a écrit :
You can simply add the jar in conf/lib and it will be picked up into
the classpath without any additional configuration.
Thx, Eric
On 30/03/12 21:38, Saibabu Vallurupalli wrote:
There are two ways you can start your James server. If you are setting
CLASSPATH_PREFIX you should be able to start server by using run.sh
script:
#./run.sh&
If you are starting James using james script #./james start this uses
../conf/wrapper.conf you need to set the classpath with all your JAR.
Thanks, Sai
On Fri, Mar 30, 2012 at 3:30 PM, paul_k<[email protected]> wrote:
I am using 3.0 beta3. After creating custom matchers I was trying to
add my
jars to the classpath, by setting CLASSPATH_PREFIX in setenv.sh or
directly
in the shell (and exporting). No luck, wrapper.log indicates that my
classes
are not found. What is the correct way of adding jars to james
classpath? I
am running on SUSE linux.
Thanks.
--
View this message in context:
http://old.nabble.com/Cannot-add-files-to-classpath-tp33544926p33544926.html
Sent from the James - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
