I'm glad to hear that. Although I am actually starting to like the fact that unversioned jars are explicitly marked as "unknown" or "notversioned" or "unversioned" (which ever you fancy but it should be consistent).The fact that you have to set up a new Artifact pattern to make this work is not good.
I quite like the format for dependencies at the moment. I know there have been discussions about changing them. I would like to still be able to use the current form as it is adequate for most dependencies. Adding additional capabilities is great, but please don't remove the current format. Cheers Matt ----- Original Message ---- From: Adam Murdoch <[email protected]> To: [email protected] Sent: Thursday, 26 March, 2009 22:17:04 Subject: Re: [gradle-user] Dependency version nubmers: Is this a block or am I missing something Matthew Fudge wrote: > The way I have done this is > addFlatDirResolver('serverlib').addArtifactPattern(new > File('libs/[artifact].[ext]') > > compile 'org.apache:apache-commons:unknown' > > > The "unknown" bit doesn't mean anything. Its the version for the jar. However > the artifact pattern does not include the revison/version part so the flat > dir resolver does not try to append "-unknown" to the jar file name. > > I too would like to know if there isa better solution than this. > > I think Gradle 0.6 will address both these problems (needing to add an artifact pattern to the flat dir resolver, and needing to add a meaningless version for a dependency). Adam --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
