Re: Antlet dependencies

> Michael Homeijer wrote:
> 
> > Hi,
> >  
> > I was planning on splitting the java antlet in a java, javadoc and 
> > dist antlet to keep the antlets simple and to keep the changes when 
> > switching to another compiler (eg. aspectj) minimal.
> >  
> > I see two ways to handle the dependencies between the antlets.
> > 1. In the main build.
> >  
> > ie. target name="main.package" depends="java.compile, dist.package"
> >  
> > or
> >  
> > 2. In the antlets itself
> >  
> > The dist antlet gets a property ${compile.antlet.impl} that specifies 
> > the antlet that will perform the compile and a property 
> > ${compile.antlet.task} that specifies the task that will perform the 
> > compile.
> 
> 
> Dist can just assume there is a compile target somewhere.  If you need 
> overrides the main can do it.
> However I don't see the point of moving out javadoc, and jar from the 
> java antlet. 
> javadoc, and jar are java specific and I think they can stay. 
> A general dist target that is not java specific would be useful.
> 
Ok, I'll seperate the dist part first and see whats left when
I am going to use aspectj.

Thnx,
Michael

> 
> R,
> Nick
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Krysalis-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/krysalis-developers




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click