The problem was that version of aerogear-misc - 0.1.2 - defined in
aerogear-parent was missing on Maven Central, there was just 0.2.0.
As dependencies in <dependencyManagement> are not checked for availability
during install phase, users trying to use aerogear-misc managed by
aerogear-parent will see a resolution failure.
This was fixed by releasing aerogear-misc 0.1.2, content equal to 0.2.0, to
Maven Central.
Karel
On Mon, 19 May 2014 09:49:10 -0300
Bruno Oliveira <bruno(a)abstractj.org> wrote:
Good morning,
AeroGear Misc was staged here and the version was discussed as well,
please check this thread
(
http://aerogear-dev.1069024.n5.nabble.com/Release-of-AeroGear-Parent-td77...).
I can't see what's wrong. Semantically the correct would be 0.2.0.
On 2014-05-09, Matthias Wessendorf wrote:
> Hi,
>
> Andrea reported that the 0.1.2 release (see [1]) contains the wrong version
> number (0.2.0).
> This artifact was already pushed to maven central.
>
> On IRC we had the following idea:
> * update master to 0.1.2-SNAPSHOT
> * perform the release again (that hopefully will result in 0.1.2 on maven
> central)
>
> That still means we have a 0.2.0 on maven central. I will ask my contacts
> at Sonatype to remove the 0.2.0 bits;
>
> If folks are OK w/ that, I am happy to perform these steps by Monday morning
>
> Greetings,
> Matthias
>
> [1]
https://github.com/aerogear/aerogear-misc/blob/0.1.2/pom.xml
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev