Why not just move master up to using 0.17 (in the parent pom) and then
the CR2 can depend on that version in master. Beta1 branch would then
stay on 0.16 with the previous 0.16 snapshot version of the mojo.
Does that make sense?
On 05/21/2013 01:46 PM, Denis Golovin wrote:
I see sometimes that both tycho 0.16 and 0.17 are downloaded during
the
build. It code make sense to use version range in tycho dependency? Not
sure if it should be closed or opened range. I would go with closed
range with tycho 0.16 and 0.17 included and then update it when new
tycho version is out.
WDYT?
Thanks
Denis
On 05/21/2013 10:34 AM, Mickael Istria wrote:
> On 05/21/2013 07:02 PM, Denis Golovin wrote:
>> Mickael, it has tycho 0.16.0 in dependencies, hasn't it?
> Yes it has.
> We've been using SNAPSHOTs for some time with Tycho 0.17 without any
> issue; as Tycho did not break any of the APIs this Mojo used.
>
> Anyway, the release was done last week.
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
> My blog <
http://mickaelistria.wordpress.com> - My Tweets
> <
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com