No, I did not the whole project. Trustin asked for standalone build and I tried it on a clean machine. I only checked out mina and the local maven repository was empty.
-- Ersin On 1/19/06, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > Hi, > > have you updated the whole project? > > I have changed some deps to nlog4j 1.2.21, and rollbacked to 1.2.19 > because some deps are missing. > > Just tell me if it's KO > > > On Thu, 2006-01-19 at 13:10 +0200, Ersin Er wrote: > > Hi, > > > > It does not build on a ultra-clean machine: > > > > ... > > [INFO] Failed to resolve artifact. > > > > required artifacts missing: > > org.apache.directory:org.apache.asn1:jar:0.3.4-SNAPSHOT > > > > for the artifact: > > org.apache.directory.mina:org.apache.mina.asn1:jar:0.9.1-SNAPSHOT > > > > from the specified remote repositories: > > central (http://repo1.maven.org/maven2), > > safehaus (http://m2.safehaus.org), > > apache.snapshots (http://cvs.apache.org/maven-snapshot-repository) > > ... > > > > -- > > Ersin > > > > On 1/19/06, Niklas Therning <[EMAIL PROTECTED]> wrote: > > > Trustin Lee wrote: > > > > Hi All, > > > > > > > > I tested it by myself and saw it build OK, but I'd just like to confirm > > > > it. Please let me know if anyone failed to build MINA using Maven 2. > > > > > > > > Thanks, > > > > Trustin > > > > > > Did you remove any previous directory builds from your local maven2 > > > repository? I did a fresh checkout of MINA a couple of days ago, removed > > > everything directory-related under ~/.m2 and tried to build. The build > > > failed right away complaining about some pom it could find in any > > > repository or something. I'm not at home right now so I can't give you > > > the exact error message but maybe you could try it for yourself? I'm > > > sorry I haven't raised this issue before. > > > > > > /Niklas > > > > > > > > > -- > > Ersin > -- > Emmanuel Lécharny > www.iktek.com > > > -- Ersin
