> Hello Jason,
Hi =]
> 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?
Nope. The thirdparty module is setup in a different fashion from how it
is checked out. Perhaps that should be changed eventually, but for now
that is how it works. I think the build system faq covers this, but I
will give you the short version.
The physical repository looks like this:
/thirdparty/
apache/
log4j/
lib/*
For jboss-head this will get mapped to /thirdparty/apache-log4j. This
is a recent change to prevent `cvs update` from checking out all files
under 'apache', when only a subset is required.
To add a new thirdparty library do something like this:
1) download the archive of the library
2) extract the archive into a temporary directory
3) remove all non-essential files (docs, examples, whatever)
basically we only want basic README, COPYRIGHT & lib/* files.
4) Make sure that all "library" files live in lib (move them if the
archive does not have them in this order
5) If the library has a README and/or COPYRIGHT docs, make sure they
are in the root.
6) Make sure you are in the top-level of the archive (where lib is a
direct
child) and:
cvs -d <CVSROOT> import thirdparty/<vendor>/<package> <vender>
<package>_<version>
So for Apache/Jakarta Commons v1.1 you would:
cvs -d <CVSROOT> import thirdparty/apache/commons apache commons_1_1
The check in comments are basically describing the new import, so list
the full name & version of the imported bits.
Then, you need to edit CVSROOT/modules, in the bottom there is a
thirdparty library section, copy the format of other entries for the new
entry. Then add the module include to which ever projects you need to
access it from.
Then, finally, edit tools/etc/buildfragments/libraries.ent and add
definitions of the root, lib and classpath's for this library. Note
that you should use exact paths (no filesets) so that the build system
does not freak out when this library is not present.
That is it... rather simple once you get the hang of it.
Again, if you like I can handle this for you if you tell me what you
need done exactly.
--jason
-------------------------------------------------------
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
