Hi band again,
there is a huge problem in branch/apacheds/optimization-trunks.
The svn:externals property are set to a wrong version of mina :
[EMAIL PROTECTED] optimization-trunks]$ svn pg svn:externals
apacheds
https://svn.apache.org/repos/asf/directory/branches/apacheds/optimization
daemon -r412564
https://svn.apache.org/repos/asf/directory/releases/daemon/1.0-RC2
shared
https://svn.apache.org/repos/asf/directory/branches/shared/optimization
mina -r412559 https://svn.apache.org/repos/asf/directory/releases/mina/0.9.4
MINA-0.9.4 can't compile with shared trunk.
We have to fix this if we want to be able to merge the branch into the
trunk...
Another point : it could be a very good idea to commit .classpath to
link projects between them, instead of depending on jars in the repo. So
far, as we have .classpath built by maven, each project point to a jar
in the repo, not to another project. So you may run the server without
using the piece of code you have just modified, because the jar that you
created by mvn install was not the one pointed in another .classpath.
For instance, in optimization-trunks, the .classpath contains :
<classpathentry kind="var"
path="M2_REPO/org/apache/directory/shared/shared-asn1/0.9.5.1/shared-asn1-0.9.5.1.jar"/>
but the current project shared-ldap pom.xml contains :
<version>0.9.5.2-SNAPSHOT</version>
So whatever modification you do in shared-ldap, even related to MINA
filter-codec-asn1 project, won't be used when you will test MINA. You
can mvn install shared-ldap how often you want, MINA will still use an
old jar ...
And this is not Maven fault :)
Emmanuel
