You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kato-dev@incubator.apache.org by Steve Poole <sp...@googlemail.com> on 2009/03/31 08:21:01 UTC
Building kato - external dependencies
Hi all - in building kato and running tests etc a developer will need to
have access to junit, ant and emma. It would be really convenient to book
the junit and emma jars into svn but before I do such a thing I'd like some
advice.
Other Apache projects seem to do this and keep the jars in a obviously
seperate path (ie having "external" in the name) Is there any documented
guidence for doing this one way or another?
Steve
Re: Building kato - external dependencies
Posted by Steve Poole <sp...@googlemail.com>.
I bumped into a Harmony committer and found out that they don't book their
dependencies into svn.
Their approach is to have a local cache which they can create/update by
fetching the dependencies from well
known locations.
I like that so I'm going to use it as an initial approach to get kato
building.
On Tue, Mar 31, 2009 at 10:48 AM, Robert Burrell Donkin <
robertburrelldonkin@gmail.com> wrote:
> On Tue, Mar 31, 2009 at 9:21 AM, Steve Poole <sp...@googlemail.com>
> wrote:
> > Hi all - in building kato and running tests etc a developer will need to
> > have access to junit, ant and emma. It would be really convenient to
> book
> > the junit and emma jars into svn but before I do such a thing I'd like
> some
> > advice.
> >
> > Other Apache projects seem to do this and keep the jars in a obviously
> > seperate path (ie having "external" in the name) Is there any
> documented
> > guidence for doing this one way or another?
>
> probably not
>
> apache delegates as much as possible to PMCs so there's usually quite
> a lot of diversity. asking on the community mailing list would be the
> best bet for best practice advice.
>
> the key point is to ensure that everything is ok as far as
> http://www.apache.org/legal/ goes. for third party jars, this means
> ensuring that they are clearly licensed (i usually check in a
> foo-bar-1.1.LICENSE next to foo-bar-1.1.jar) and that any additions
> required to NOTICE and LICENSE documents have been made.
>
> - robert
>
Re: Building kato - external dependencies
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Tue, Mar 31, 2009 at 9:21 AM, Steve Poole <sp...@googlemail.com> wrote:
> Hi all - in building kato and running tests etc a developer will need to
> have access to junit, ant and emma. It would be really convenient to book
> the junit and emma jars into svn but before I do such a thing I'd like some
> advice.
>
> Other Apache projects seem to do this and keep the jars in a obviously
> seperate path (ie having "external" in the name) Is there any documented
> guidence for doing this one way or another?
probably not
apache delegates as much as possible to PMCs so there's usually quite
a lot of diversity. asking on the community mailing list would be the
best bet for best practice advice.
the key point is to ensure that everything is ok as far as
http://www.apache.org/legal/ goes. for third party jars, this means
ensuring that they are clearly licensed (i usually check in a
foo-bar-1.1.LICENSE next to foo-bar-1.1.jar) and that any additions
required to NOTICE and LICENSE documents have been made.
- robert