Hello Jason,

thank you for taking care. I saw commits but I neither see the
apache-commons in the thirdparty nor can find
commons-collections.jar.
Could you please look at it?

Thank you very much.

alex

Tuesday, October 29, 2002, 2:47:50 AM, you wrote:

JD> Apache commons collections has been imported in apache-commons.

JD> --jason


>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:jboss-
>> [EMAIL PROTECTED]] On Behalf Of Alex Loubyansky
>> Sent: Friday, October 25, 2002 1:30 PM
>> To: Jason Dillon
>> Subject: Re[4]: [JBoss-dev] can't add a dir to thirdparty
>> 
>> You are cool. I respect you.
>> 
>> Please, guide me through this.
>> I have jboss-head/thirdparty/tmp/ that contains:
>> readme
>> lib/
>>    META-INF/
>>       license
>>       manifest.mf
>>    *.class
>> 
>> Then I execute the following:
>> cvs import -m"imported apache commons-collections version 2.0, dated
>> 02/04/2002." thirdparty/apache/commons-collections apache commons-
>> collections_2_0
>> 
>> How can I edit modules file? Were is it?
>> 
>> alex
>> 
>> >> I want to add to thirdparty the following:
>> >> apache-commons/
>> >>   readme
>> >>   lib/
>> >>      commons-collections.jar
>> >>
>> >> I started with 'cvs add apache-commons' and got the error I wrote
>> >> about.
>> >>
>> >> As to the jar, I would add the following way:
>> >> cvs add -kb commons-collections.jar
>> >> cvs ci -m"apache commons collections" commons-collections.jar
>> >>
>> >> Is it correct?
>> 
>> JD> Nope.  The thirdparty module is setup in a different fashion from
JD> how
>> it
>> JD> is checked out.  Perhaps that should be changed eventually, but
JD> for
>> now
>> JD> that is how it works.  I think the build system faq covers this,
JD> but I
>> JD> will give you the short version.
>> 
>> JD> The physical repository looks like this:
>> 
>> JD>  /thirdparty/
>> JD>              apache/
>> JD>                     log4j/
>> JD>                           lib/*
>> 
>> JD> For jboss-head this will get mapped to /thirdparty/apache-log4j.
JD> This
>> JD> is a recent change to prevent `cvs update` from checking out all
JD> files
>> JD> under 'apache', when only a subset is required.
>> 
>> JD> To add a new thirdparty library do something like this:
>> 
>> JD>  1) download the archive of the library
>> 
>> JD>  2) extract the archive into a temporary directory
>> 
>> JD>  3) remove all non-essential files (docs, examples, whatever)
>> JD>     basically we only want basic README, COPYRIGHT & lib/* files.
>> 
>> JD>  4) Make sure that all "library" files live in lib (move them if
JD> the
>> JD>     archive does not have them in this order
>> 
>> JD>  5) If the library has a README and/or COPYRIGHT docs, make sure
JD> they
>> JD>     are in the root.
>> 
>> JD>  6) Make sure you are in the top-level of the archive (where lib
JD> is a
>> JD> direct
>> JD>     child) and:
>> 
>> JD>  cvs -d <CVSROOT> import thirdparty/<vendor>/<package> <vender>
>> JD> <package>_<version>
>> 
>> JD> So for Apache/Jakarta Commons v1.1 you would:
>> 
>> JD>  cvs -d <CVSROOT> import thirdparty/apache/commons apache
JD> commons_1_1
>> 
>> JD> The check in comments are basically describing the new import, so
JD> list
>> JD> the full name & version of the imported bits.
>> 
>> JD> Then, you need to edit CVSROOT/modules, in the bottom there is a
>> JD> thirdparty library section, copy the format of other entries for
JD> the
>> new
>> JD> entry.  Then add the module include to which ever projects you
JD> need to
>> JD> access it from.
>> 
>> JD> Then, finally, edit tools/etc/buildfragments/libraries.ent and add
>> JD> definitions of the root, lib and classpath's for this library.
JD> Note
>> JD> that you should use exact paths (no filesets) so that the build
JD> system
>> JD> does not freak out when this library is not present.
>> 
>> JD> That is it... rather simple once you get the hang of it.
>> 
>> JD> Again, if you like I can handle this for you if you tell me what
JD> you
>> JD> need done exactly.
>> 
>> JD> --jason


-- 
Best regards,
 Alex Loubyansky




-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to