Interesting... you're depending on ant.jar only? So optional tasks from other jars wouldn't be present? The short term fix is to use the full battery of ant jars.... Long-term it seems like it would be prudent for Ant to move the optional task definitions to a secondary file that can be loaded with onerror=fail.
-Matt --- "Archie Cobbs (JIRA)" <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/IVY-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Archie Cobbs updated IVY-829: > ----------------------------- > > Attachment: test-patch.txt > > I tried to implement this (see "test-patch.txt" > attached) but ran across a couple of issues: > > # I couldn't figure out how to fix the build ("ant > jar"). The bootstrapping process breaks when the > PackagerResolver includes ant classes. I was able to > hack in a temporary workaround though. > # When it tries to run the ant task (e.g., during > the unit test) it bombs out: > {noformat} > :: loading settings :: url = > file:/home/archie/ivycore/trunk/build/classes/core/org/apache/ivy/core/settings/ivysettings.xml > Project base dir set to: > /home/archie/ivycore/trunk/build/test/PackagerResolverTest/build/org/mod/1.0 > [packager] calling target(s) [build] in build file > /home/archie/ivycore/trunk/build/test/PackagerResolverTest/build/org/mod/1.0/build.xml > parsing buildfile > /home/archie/ivycore/trunk/build/test/PackagerResolverTest/build/org/mod/1.0/build.xml > with URI = > file:/home/archie/ivycore/trunk/build/test/PackagerReso > lverTest/build/org/mod/1.0/build.xml > Project base dir set to: > /home/archie/ivycore/trunk/build/test/PackagerResolverTest/build/org/mod/1.0 > [packager] Entering > /home/archie/ivycore/trunk/build/test/PackagerResolverTest/build/org/mod/1.0/build.xml... > Build sequence for target(s) `build' is [validate, > setResourceURL1, setResourceURL2, style, build] > Complete build sequence is [validate, > setResourceURL1, setResourceURL2, style, build, ] > > validate: > [antlib:org.apache.tools.ant] Could not load > definitions from resource > org/apache/tools/ant/antlib.xml. It could not be > found. > [packager] Exiting > /home/archie/ivycore/trunk/build/test/PackagerResolverTest/build/org/mod/1.0/build.xml. > The following error occurred while executing this > line: > /home/archie/ivycore/trunk/build/test/PackagerResolverTest/build/org/mod/1.0/build.xml:22: > Problem: failed to create task or type xmlvalidate > Cause: the class > org.apache.tools.ant.taskdefs.optional.XMLValidateTask > was not found. > This looks like one of Ant's optional > components. > Action: Check that the appropriate optional JAR > exists in > -ANT_HOME/lib > -the IDE Ant configuration dialogs > > Do not panic, this is a common problem. > The commonest cause is a missing JAR. > > This is not a bug; it is a configuration problem > {noformat} > > > Add new "packager" resolver to Ivy > > ---------------------------------- > > > > Key: IVY-829 > > URL: > https://issues.apache.org/jira/browse/IVY-829 > > Project: Ivy > > Issue Type: New Feature > > Components: Core > > Affects Versions: 2.0.0-beta-2 > > Reporter: Archie Cobbs > > Assignee: Xavier Hanin > > Fix For: 2.0-RC1 > > > > Attachments: m2repo.tgz, > packager-resolver-patch.txt, test-patch.txt > > > > > > Feature request to add a new resolver, called the > "Packager Resolver", [described > here|http://ivyroundup.googlecode.com/svn/wiki/files/packager.html]. > > Patch is attached and also available > [here|http://ivyroundup.googlecode.com/svn/wiki/files/packager-resolver.patch]. > Patch contains binary test files, so to apply it you > have to follow the [simple steps described > here|http://code.google.com/p/ivyroundup/]. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the > issue online. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
