-------- Original-Nachricht --------
Datum: Tue, 24 Oct 2006 09:59:05 +0100
Von: Steve Loughran <[EMAIL PROTECTED]>
An: Ant Developers List <dev@ant.apache.org>
Betreff: Re: svn commit: r466627 - in /ant/core/trunk/src/etc/poms: ./ 
ant-antlr/ ant-apache-bcel/ ant-apache-bsf/ ant-apache-log4j/ ant-apache-oro/ 
ant-apache-regexp/ ant-apache-resolver/ ant-commons-logging/ ant-commons-net/ 
ant-jai/ ant-javamail/ ant-jdepend/ an...

> wow, you have been a busy little bee :)

Happens sometimes. Had an argument with my wife. Compensated by workaholism.

> 
> I'll look over these. 

Gladly

> 
> 1. Mostly they look OK, though I can see you've chosen to mark most 
> dependencies as compile and not runtime. Is that what we want? I'm OK 
> with that, as I am much happier with dependency-metadata as a hint, not 
> a mandatory thing.
>
Except antlr, I think I only entered compile time dependencies. I hope that for 
instance the pom of commons-bsf should itself contain js, groovy, and the other 
supported languages as optional runtime dependencies. 
> 
> 2. how are these generated? By hand, or from a template. 
By hand
> If we have 
> template a driven process, I'd like every POM file to include (as a 
> comment) some audit trail information. Who created, when, and where to 
> go for support calls. i.e.

> 
> <!---
> 
>       POM created on 2006-10-24 0956 by stevel
>       This POM officially supported by the ant team, if the artifact is an 
> official ant artifact.
>          Please raise issues with the correctness of this pom to the ant 
> developer mailing list.
>       
> -->
> 
> IMO all poms should have this information in proper elements, but they 
> dont, so we have to make do with comments.
> 
> -steve
> 
> more below
> Why is antlr scoped for compile and not runtime?
this was an error. I just fixed it in svn.

> 
> 
> > Added: ant/core/trunk/src/etc/poms/ant-commons-logging/pom.xml
> > URL:
> > we should depend on commons-logging-api at runtime, not commons-logging.

this is fixed.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to