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 how it
JD> is checked out. Perhaps that should be changed eventually, but for now
JD> that is how it works. I think the build system faq covers this, 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. This
JD> is a recent change to prevent `cvs update` from checking out all 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 the
JD> archive does not have them in this order
JD> 5) If the library has a README and/or COPYRIGHT docs, make sure they
JD> are in the root.
JD> 6) Make sure you are in the top-level of the archive (where lib 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 commons_1_1
JD> The check in comments are basically describing the new import, so 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 the new
JD> entry. Then add the module include to which ever projects you 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. Note
JD> that you should use exact paths (no filesets) so that the build 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 you
JD> need done exactly.
JD> --jason
--
Best regards,
Alex Loubyansky
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
