commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Re: [all] preparing initial commit
Date Mon, 17 May 2010 05:03:45 GMT
Interesting questions - we've been Maven based for so long that
putting dependencies in SVN hasn't happened for a while.

What's your build structure, and how are the below used?

I like the notion of the svn:external for Dojo. Otherwise I'd be
tempted to have it in zip format and have the build unpack it from the
zip into a directory that 'clean' removes [whatever your equivalent of
'target', 'build' or 'private' is].


On Sun, May 16, 2010 at 8:25 PM, Jacob Beard <> wrote:
> Hi,
> I'm currently working to prepare the initial commit for my Google
> Summer of Code project. I have a quick question regarding external
> libraries. My project currently uses a few libraries which are
> licensed under liberal, non-copyleft licenses. A list of these
> libraries and their associated licenses is as follows:
> Mozilla Rhino - MPL
> Dojo JavaScript toolkit - BSD/AFL dual license
> Selenium - Apache 2.0 License
> js-beautify - something a bit non-standard:
> json2 - Public Domain
> Is it possible to include these libraries in the source tree of my project?
> Also, for a library like dojo, which is large (about 100MB,
> uncompressed), and composed of many small files, would it be better to
> include a compressed zip file in the library directory, with
> instructions in the README for the user to unzip it, or would it be
> better to use an svn:externals svn property to point to the dojo
> source tree, so that it is automatically checked out (probably from a
> specific tag), when the source tree is checked out.
> Please let me know what you think. Thanks,
> Jake
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message