directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <>
Subject Re: [bigbang] Broken build
Date Sun, 04 May 2008 07:57:24 GMT
Hi Alex,

As I already stated, there is badly wrong with the current build. It's 
now depending on the compilation order...

For instance :

> [INFO] 
> ------------------------------------------------------------------------
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Compilation failure
> /home/akarasulu/ramdisk/bigbang/shared/ldap/target/generated-sources/antlr/org/apache/directory/shared/ldap/subtree/[870,9]

> cannot find symbol
> symbol  : constructor 
> EqualityNode(java.lang.String,
> location: class

Here is the constructor ( committed ) :

    public EqualityNode( String attribute, Value<?> value )
        super( attribute, value, AssertionType.EQUALITY );

with :
public class ClientStringValue extends AbstractValue<String>


public abstract class AbstractValue<T> implements Value<T>

There is no reason why you got this error. But you got it...

FYI, this code perfectly compile on my computer, all integration tests 

Another thing I find strange is that now, we are downloading jars from 
oxylos :


I didn't changed my .settings.xml; so obviously, the build has changed.

Last, not least, I doomed my .m2/repository and mvn build cleaned it, 
got no error...

[INFO] Total time: 7 minutes 14 seconds
[INFO] Finished at: Sun May 04 09:54:49 CEST 2008
[INFO] Final Memory: 61M/185M

elecharny@elecharny-laptop:~/apacheds/bb$ java -version
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Server VM (build 1.5.0_14-b03, mixed mode)

elecharny@elecharny-laptop:~/apacheds/bb$ mvn --version
Maven version: 2.0.9
Java version: 1.5.0_14
OS name: "linux" version: "2.6.20-16-generic" arch: "i386" Family: "unix"

FYI, I was not able to co the code, as eris is down again ... So even if 
there is a problem with the build, I won't be able to fix it.

My bet : we have problems with the current build. It has become overly 
complex, which is not something bad by essence, but some choices have to 
be clarified, and it also have to be documented. I guess that some 
effort should be done for 1.5.3 in order to provide a simpler build, by 
cleaning the useless parts of it (useless : mean what is not absolutely 

It is not normal that you get some error on a fresh machine when it 
compiles just fine on my laptop after a and a removed 

cordialement, regards,
Emmanuel L├ęcharny

View raw message