You dont have to create a distributable artifact while bootstrapping.
The reason is not to depend on your own software while building it.

Same in Ant ...

The Ant bootstrap step compiles a number of classes via command line javac 
and just the JDK. Then we have a "small" Ant which we then use to do the 
normal build with all its optional dependencies and tests.
So the dependency is only: JDK

For Ivy: JDK + Ant.
1. Bootstrap: use Ant to compile some classes without depenencies
2. Get Deps: use the compiled class for depenency resolving
3. Now all is there: the whole build using the artifacts from 1.+2.


Jan



>-----Ursprüngliche Nachricht-----
>Von: Xavier Hanin [mailto:[EMAIL PROTECTED] 
>Gesendet: Freitag, 4. Mai 2007 00:28
>An: [email protected]
>Betreff: Re: dependency on ivy.jar
>
>On 5/4/07, Maarten Coene <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> one of the things that bothers me since long is the 
>dependency on an external ivy.jar when trying to build ivy using Ant.
>> As discussed some time ago on this list, there is a solution 
>for this problem:
>>
>> step 1: compile "Ivy Core": these classes are the core of 
>Ivy which doesn't has any external dependency.
>> step 2: compile "Ivy Ant": these classes are the Ant tasks.  
>They have 2 dependencies: "Ivy Core" and Ant itself.
>> step 3: use the classes from step1 and step2 to resolve the 
>ivy.xml file from Ivy
>> step 4: also download the jars to the lib directory
>> step 5: compile "Ivy Optional": these classes are extensions 
>of Ivy and may required 3th-party libraries. These 3th-party 
>libraries have been downloaded in the previous step.
>> step 6: create ivy.jar (containing everything) and 
>ivy-core.jar (containing only "Ivy Core").
>>
>> I tried it out and it seems to work well.
>>
>> Do you think this is ok? If no-one objects, I'll try to 
>commit my changes this weekend. I didn't had to change much: 
>only 2 source files and of course the Ant build files.
>This seems like a very good thing to me. The only point is about the
>packaging, ivy-core used to caintain everything but ant related
>classes, and I think we should keep an artifact like this one, which
>is used at least in IvyDE.
>
>But this is a minor thing that can be fixed later.
>
>Xavier
>>
>> --
>> Maarten
>>
>>
>>
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam?  Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>>
>
>
>-- 
>Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
>Manage your dependencies with Ivy!
>http://incubator.apache.org/ivy/
>

Reply via email to