nodje ha scritto:
hey thanks
I haven't open the documentation yet but thanks to Maven I have been able
to compile the whole stuff.
spring-integration wouldn't compile on it's own though. Some missing
dependencies - or repository issue.
I committed fix to poms yesterday, please try again with the latest version.
So I had to 'mvn package' on the trunk.
One test fails, over 732:
org.apache.james.experimental.imapserver.ExperimentalSelectedInboxTest
Seems to be linked to an experimental IMAP server. Not needed for me anyway.
This fails to me too under maven, but it pass under ant, I never had
enough cycles to check why.
I use -Dmaven.test.failure.ignore=true now when I have to run mvn.
I'll package without the test and try to use it (that's probably where I'll
have to open the documentation!)
Unfortunately I have to say you that maven poms are there mainly to
build our website and our build tool is still ant. In practice the
deployment modules do not really create usable packages because I never
took care of doing this (no assembly descriptor). I just took care that
maven was compiling all the classes, creating every jar and running
tests. So I suggest you to build the deployment module with ant, so you
will find a more complete resulting package for spring-deployment and
not only a simple jar.
I'm wondering how to integrate James librairies within our own repository
and how to make it part of our build process for the time being (I mean
until a stable 3.0 is released).
If you need stable releases you will have to mark your own. JAMES
snapshots are not published in maven repositories, so you will have to
install them (mvn:install) in your local repository and use it as a
dependency.
I should probably add a <distributionManagement> section to the pom and
deploy the artifacts to our local repository.
I'll hopefully post my tryout results soon.
I suggest you to try first the ant generated package so you understand
how to use it. Once you understand how to use the spring based
deployment you probably can move to depend only on the maven generated
jars via direct maven dependencies: if not I would be glad to help and
fix what is wrong in our poms.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
