On 12/01/2011, at 8:08 AM, helmut.denk wrote:
>
> hi meikel,
>
> thanks for the hint ... interestingly lein/maven
> resolves clojure-1.2.0 for the dependencies above.
>
> i guess that this is because lein/maven is configured to
> recognize the 'alpha' in revision-id and classify alpha-release
On 11/01/2011, at 9:53 PM, helmut.denk wrote:
>
>
> Adam Murdoch-3 wrote:
>>
>> In general, there isn't. But there might be a workaround, depending on why
>> you need the conflict resolution.
>>
>
> hi adam,
>
> thanks for the answer and sorry for the delay ...
>
> here is such a situati
hi meikel,
thanks for the hint ... interestingly lein/maven
resolves clojure-1.2.0 for the dependencies above.
i guess that this is because lein/maven is configured to
recognize the 'alpha' in revision-id and classify alpha-release as
different from release.
grüsse
--
View this message in c
Hi,
Am 11.01.2011 um 12:15 schrieb helmut.denk:
>
> an additional remark:
>
> i know, that i could resolve enlive by hand
>
>
> compile 'enlive:enlive:1.0.0-snaps...@jar'
> ...
>
>
> but then there is another lib that needs
> to be treated the same way:
>
>
> compile 'net.cgrand:moustac
an additional remark:
i know, that i could resolve enlive by hand
compile 'enlive:enlive:1.0.0-snaps...@jar'
...
but then there is another lib that needs
to be treated the same way:
compile 'net.cgrand:moustache:1.0.0-SNAPSHOT'
and maybe another and another
--
View this message in
Adam Murdoch-3 wrote:
>
> In general, there isn't. But there might be a workaround, depending on why
> you need the conflict resolution.
>
hi adam,
thanks for the answer and sorry for the delay ...
here is such a situation:
dependencies {
compile 'org.clojure:clojure:1.2.0'
compi
On 03/11/2010, at 10:21 AM, helmut.denk wrote:
>
> this feature seems to be tbd.:
>
> http://jira.codehaus.org/browse/GRADLE-1193
>
> my question is: are there workarounds ?
In general, there isn't. But there might be a workaround, depending on why you
need the conflict resolution.
--
Adam
this feature seems to be tbd.:
http://jira.codehaus.org/browse/GRADLE-1193
my question is: are there workarounds ?
--
View this message in context:
http://gradle.1045684.n5.nabble.com/custom-dependency-conflict-resolver-tp3205266p3247744.html
Sent from the gradle-user mailing list archive a
