2007/3/25, Xavier Hanin <[EMAIL PROTECTED]>:
It sounds like a good idea. One thing to remember, Ivy core doesn't depend
on Ant, so make sure you don't introduce a dependency on Ant outside the
org.apache.ivy.ant package.
I will define a generic interface inside Ivy core (with a simple
implementation using an hashmap), and implement the ant version in the
ant package.
Also, I wonder what to do with the variable defined with the task or
> inside the settings file. I guess I should not propagate them into
> the ant properties, and keep them local to ivy. What do you think?
I think they were not propagated before, so they don't need to be
propagated. But I'm not absolutely sure, so if you find something strange,
please report it here.
- Xavier
They were not. However, I think that the properties defined in
ivy.properties ressource are exported to the project by the first call
to configure. Here is the list (I'm not sure they were all designed
to be exported) :
ivy.project.dir = ${basedir}
ivy.lib.dir = ${ivy.project.dir}/lib
ivy.build.artifacts.dir = ${ivy.project.dir}/build/artifacts
ivy.distrib.dir = ${ivy.project.dir}/distrib
ivy.resolver.default.check.modified = false
ivy.default.always.check.exact.revision = true
ivy.configurations = *
ivy.resolve.default.type.filter = *
ivy.status = integration
ivy.dep.file = ivy.xml
ivy.settings.file = ivysettings.xml
ivy.retrieve.pattern = ${ivy.lib.dir}/[artifact]-[revision].[ext]
ivy.deliver.ivy.pattern = ${ivy.distrib.dir}/[type]s/[artifact]-[revision].[ext]
ivy.publish.src.artifacts.pattern =
${ivy.distrib.dir}/[type]s/[artifact]-[revision].[ext]
ivy.report.output.pattern = [organisation]-[module]-[conf].[ext]
ivy.buildlist.ivyfilepath = ivy.xml
ivy.checksums=sha1,md5
ivy.log.modules.in.use=false
--
Gilles SCOKART
