directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <aok...@bellsouth.net>
Subject [ldap] Xstream dep introduction common breaks build
Date Sat, 12 Feb 2005 05:35:48 GMT
Vince,

I figure you introduced XStream as a new dep. Cool! I like XStream from 
what little I've read about it.  It's that fast XML parser that builds 
beans for ya right?  Could you elaborate on why you introduced this 
dependency?  Also let's discuss the introduction of new dependencies 
together in general.  If there's something to be learned from the 
incubator it's to review these things together.  I know XStream does not 
conflict with our license but you should still announce this to the list.

Regardless let's make sure introducing new deps do not break the build.  
Here's what I got when I built just now:

---------------------------------------------------------------------------
BUILD FAILED
File...... 
/home/akarasulu/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
Element... maven:reactor
Line...... 217
Column.... 9
The build cannot continue because of the following unsatisfied dependency:

xstream-1.0.2.jar (try downloading from http://xstream.codehaus.org)

Total time: 45 seconds
Finished at: Sat Feb 12 00:08:22 EST 2005
---------------------------------------------------------------------------

I know you probably double check to make sure things build after you 
make changes.  So I suspect you have the codehaus repo referenced 
somewhere in your user specific build.properties in your home 
directory.  The xstream dep was not getting resolved for me because I do 
not reference the codehaus repo in my build.properties in ~akarasulu.

To make sure this does not happen again you might want to add the 
codehaus repo to the list of remote repos within the project.  Or just 
make sure the dependency is in the right place on cvs.apache.org or on 
ibiblio before introducing it. 

I already pushed the jar to our incubator repo for now but we should 
make sure it gets out to ibiblio.  I'm sure Dan or Jason might already 
be on this one.  Might be worth giving them a ping anyhow.

Also I've heard a lot of good things about XStream.  Could you give us a 
rundown on it to raise awareness?  If it's as good as several people are 
saying then perhaps we should be thinking about using it more throughout 
the project.

Cheers,
-Alex


Mime
View raw message