With xml includes you can include a part of a xml file. With <import> you imports another buildfile. With <taskdef> you define tasks.
What Stefan was: - your buildfile <import>s sales.xml and common.xml - these two files have <taskdef>s for declaring the tasks, maybe set some <property>s or make some <[macro|preset|script]def>s. To get a task "into" Ant the only other ways than <taskdef> I know are <java> and <script> ... Jan >-----Ursprüngliche Nachricht----- >Von: Tommy Nordgren [mailto:[EMAIL PROTECTED] >Gesendet: Mittwoch, 25. Januar 2006 18:37 >An: Ant Users List >Betreff: Re: Making custom tasks globally available > > >On Jan 25, 2006, at 4:39 AM, Tommy Nordgren wrote: > >> Quoting the following example from "Extreme Programming with Ant" >> <?xml version="1.0" ?> >> >> <!DOCTYPE project [<!ENTITY sales SYSTEM >> "file:sales.xml> >> <!ENTITY common SYSTEM >> "file:common.xml">]> >> >> <project name="eMarket" default="compile" basedir="."> >> >> ..... >> >> &common; >> &sales; >> >> </project> >> >> Where can I put files for entities, so that they are >available to ALL >> my projects? >> > > Both Stefan Bodewig have suggested useing the new <import> tag. > However Checking a Java native Interface OSS project that uses >third party ant tasks, I've found that there is also another solution. >Using <taskdef resource="Tommys_Ant_Tasks.tasks" /> >This will load a set of task defs from a property file included in my >distribution jar. >------------------------------------- >This sig is dedicated to the advancement of Nuclear Power >Tommy Nordgren >[EMAIL PROTECTED] > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
