I haven't actually tried it, but i'm guessing that the JS libs in Bower will have
a similar issue
On Feb 28, 2013, at 9:17 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
Hi,
we are 'shipping' our iOS bits via CocoaPods. In order to specify a
version, your project's Podfile needs to have the following:
....
pod 'AeroGear', '1.0.0.CR1'
...
This works fine. BUT... It's also valid to NOT specify a version:
....
pod 'AeroGear'
...
Now... it loads the latest and greatest version... not!
(well, usually it does)
-> In our case we get the 'old' M3 version (since the 'M' is BEHIND
the 'C' in the alphabet).
Options:
1) DELETE all the old versions from CocoaPods
2) name the CR1 an M4 - but the same problem will occur with the
1.0.0(.Final) :-)
So... I guess.... in order to keep/fix this... we really have to
remove the old versions :-(
For future releases, I'd strongly recommend to NOT use that .milestone
versioning.
Cheers!
Matthias
--
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