This brings up a related question regarding a situation I've been dealing with. I'm trying to work with a repository without Ivy XML files, and the artifacts in this repository are not jar files (they are tar.gz files). With dependencies, this is fine because I can just use the <artifact> child. However when it comes to using <install>, there does not seem to be a way to deal with ivy-less repositories, or am I missing something?
Maarten Coene ---01/22/2010 04:39:48 PM---Your module containing the swc file should have an ivy.xml file defining the swc artifact with correct extension.
Maarten Coene <email@example.com>
01/22/2010 04:39 PM
Re: Using ivy:install to install non-jar artifacts
Your module containing the swc file should have an ivy.xml file defining the swc artifact with correct extension.
Can you confirm this is the case in the repository you have specified in the "from" attribute of your ivy:install task?
----- Original Message ----
From: "Steele, Richard" <firstname.lastname@example.org>
Sent: Fri, January 22, 2010 3:20:13 PM
Subject: Using ivy:install to install non-jar artifacts
We're struggling to figure out how to install artifacts to our local http
repository with non-jar artifacts (in this case, a Flex SWC file). We've
tried specifying type="swc" on the Ant ivy:install task, but Ivy can't find
the artifact because the [ext] isn't set. We tried installing to a
SWC-specific repository with its own pattern, hard-coding the extension as
"swc", but the type attribute on the install task seems to be ignored: the
generated ivy.xml still declares the artifact is a jar type.
What on earth are we missing?