Announcement Announcement Module
Collapse
No announcement yet.
A tiny problem with the new build mechanism Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • A tiny problem with the new build mechanism

    I just tried to build webflow from CVS (to get the some of the fixes) and I got this error when invoking 'ant dist':

    Unable to find typedef antlib:fr.jayasoft.ivy.ant:resolve

    (ocurring in common-targets.xml, line 299)
    After some playing around I found that I need to copy the ivy jar that is actually part of the checkout of spring-projects (repository/jayasoft/ivy/jars subfolder), to ant's lib directory in order to make it work (with ant 1.6.2).
    Is there some way to directly use this ivy jar for the build process rather than requiring the user to copy this jar to Ant's lib folder (which might bring other trouble with other projects using ivy as the version in the repository folder does not seem to be a stable one and my guess is that you require some of its new/enhanced functionality ?)

    regards,
    Tom

  • #2
    Ivy must be in Ant's classpath. We require features/fixes in Ivy that aren't part of a point release yet.

    So there's not much we can do but speak to Xavier and his team and ask them to release Ivy 1.1.1 before RC1 (which we will do) :-)

    Keith

    Comment


    • #3
      Mhm, yes, though you could always use taskdef's ? :

      Code:
      <taskdef name="ivy-retrieve" 
               classname="fr.jayasoft.ivy.ant.IvyRetrieve">
          <classpath refid="ivy-classpath"/>
      </taskdef>
      This I think would make it easier for people that for instance use IDEs (eg. they'd have to copy ivy to Eclipse's ant plugin folder, right ?) or where they are not able to change the environment because of limited user rights or the like.

      Tom

      Comment


      • #4
        Yes good point.

        I'm all for whatever is simplest for users here.

        That is a decision we have to make: do we ship Ivy and point to it, or do we assume it's part of the users environment (e.g. make it their responsibiltiy to install Ivy in ANT_HOME/lib).

        I've pointed Colin at this thread for consideration.

        Keith

        Comment

        Working...
        X