> An official release can't depend on a snapshot
Yes it can even though it is not the default.
> but this should be easy to fix by those who know maven well, and we have
> released the software in question.
Well, I didn't follow this dev closely but can see in [1] that only the 1.0.0
has been released therefore it is usual in the dev branch to use the next
snapshot version (aka 1.1.0-SNAPSHOT)
Again, I guess (still to confirm though) the fact that is a Ant build doesn't
give us an automatic option to say 1.1.0-SNAPSHOT but we have to specify the
exact snapshot which is a new file at each build/deploy snapshot of flex-tool,
to check it, it would worth to try to set the lib version to
flex-tool-api-1.1.0-SNAPSHOT.jar instead of
flex-tool-api-1.1.0-20141121.233135-20.jar and see if the resolution occurs or
use the release version but you won't see if the new implementation of this lib
breaks something.
Frédéric THOMAS
[1]
https://repository.apache.org/content/groups/public/org/apache/flex/flex-tool-api/
> Subject: Re: git commit: [flex-sdk] [refs/heads/develop] - The link was
> pointing to an old version of the .jar
> From: jus...@classsoftware.com
> Date: Tue, 2 Dec 2014 01:44:28 +1100
> To: dev@flex.apache.org
>
> Hi,
>
> An official release can't depend on a snapshot, but this should be easy to
> fix by those who know maven well, and we have released the software in
> question.
>
> Justin
