I think you just was very unlikely to have built the m1 branch just in
the middle of 2 commits.
I forgot to commit one class, and I did it a few minutes later. If you
svnupped in between, then you probably got those errors.
Please svn up again, and give it a try.
And, yes, m1 may be unstable, even if we try not to break the branch.
On 2/3/11 6:25 PM, Alex Karasulu wrote:
This branch is unstable. We created it specifically to start moving
towards the envisaged m1 release vision for shared. So you're probably
best working in trunk.
Unfortunately we destabilized trunk before but now it's back in order,
thanks mostly to Emmanuel immense effort on the codec. So to protect
y'all we're working in m1. We will synchronize with trunk in check
pointed stages (stabilization points) to keep you up to date.
Regards,
Alex
On Thu, Feb 3, 2011 at 7:21 PM, Richard Feezel<[email protected]> wrote:
I've been tied up with other issues but I'm trying to get up-to-date with
the ADS project.
I've been skimming the messages on this list as they've been coming out and
really appreciate the major effort to re-factor the code to a more
meaningful and consistent form.
Just now I did an SVN checkout of
http://svn.apache.org/repos/asf/directory/branches/m1 as I understand that
this branch is expected to be the path forward.
I've installed Maven 3.0.2 and after the successful checkout I tried "mvn
install -DskipTests" since I understand that the tests have not yet been
brought up to date.
Sadly the build failed with:
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR]
/home/rfeezel/ADSm1/src/shared/ldap/src/test/java/org/apache/directory/shared/ldap/codec/controls/replication/SyncStateValueControlTest.java:[37,67]
package org.apache.directory.shared.ldap.message.control.replication does
not exist
[ERROR]
/home/rfeezel/ADSm1/src/shared/ldap/src/test/java/org/apache/directory/shared/ldap/codec/controls/replication/SyncInfoValueControlTest.java:[35,80]
cannot find symbol
symbol : class ISyncInfoValue
location: package
org.apache.directory.shared.ldap.codec.controls.replication.syncInfoValue
[ERROR]
/home/rfeezel/ADSm1/src/shared/ldap/src/test/java/org/apache/directory/shared/ldap/codec/controls/replication/SyncInfoValueControlTest.java:[37,67]
package org.apache.directory.shared.ldap.message.control.replication does
not exist
[ERROR]
/home/rfeezel/ADSm1/src/shared/ldap/src/test/java/org/apache/directory/shared/ldap/codec/controls/replication/SyncRequestValueControlTest.java:[38,67]
package org.apache.directory.shared.ldap.message.control.replication does
not exist
[ERROR]
/home/rfeezel/ADSm1/src/shared/ldap/src/test/java/org/apache/directory/shared/ldap/codec/controls/replication/SyncStateValueControlTest.java:[76,22]
cannot find symbol
symbol : variable SyncStateTypeEnum
location: class
org.apache.directory.shared.ldap.codec.controls.replication.SyncStateValueControlTest
and many other errors.
My question is, is it too early to expect this branch to compile regularly?
My general practice using a subversion repository is to push updates only
when I know that they at least compile, even if not well tested. Perhaps
the group has a different philosophy, especially when working in a branch.
Some guidance on what to expect would be appreciated.
Thanks,
--
Richard M Feezel
[email protected]
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
