ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bailey, Darragh" <>
Subject RE: Problem getting a publish to local filesystem working
Date Tue, 26 Oct 2010 17:31:53 GMT

> -----Original Message-----
> From: Maarten Coene [] 
> Sent: 21 October 2010 22:30
> To:
> Subject: Re: Problem getting a publish to local filesystem working
> The specified revision is used for calling the ivy:deliver task.
> If you set the revision to 1.0.1, the ivy:deliver task will 
> look in your cache 
> for a previous resolved job of your the "my-module-1.0.1" module.
> However, you will get an error because Ivy won't find this 
> because you did never 
> resolve that module before, because your ivy.xml probably 
> doesn't contain a 
> revision attribute.
> To solve your problem maybe you could create your jars 
> without a version in the 
> filename, so you don't need to include the [revision] any 
> longer in your 
> artifacts pattern?
> regards,
> Maarten

I'd prefer not to, as I use the same dist rule to build the jar files so that the rpm/msi
build targets don't need to rename them to include the main version number in the end filename.
I could look at changing that in the future.

For the moment I've settled on using "${dist.dir}/[artifact]-${project.version.main}.[ext]",
as the pattern to work around this.

I'm guessing that my understanding of how the revision attribute works when coupled with the
pubrevision attribute doesn't match how it actually works. I assumed that it was intended
to allow you to pick up an artifact that have a particular revision specified (revision) in
the filename but then publish it with an entirely different revision (pubrevision) if so desired.

Darragh Bailey

View raw message