I have created a new temporary download page here [1] If I don't get a -1 then I will make it official in a few days.
[1] http://www.eclipse.org/nebula/new_downloads.php On Fri, Sep 5, 2014 at 7:40 PM, Wim Jongman <[email protected]> wrote: > Yes, agreed. In our specific case, we do use 0.0.0 in our _features_ > because we trust the upstream providers. Mainly they are Eclipse Platform, > Nebula, ECF and Orbit. It is not possible for us to check all individual > changes to these bundles. > > Alternatively, Alex could skip the qualifier part of the version number > because this is only the build date. > > In the mean time I have filed a bug for this restructure here: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=443429 > > Cheers, > > Wim > > > > On Fri, Sep 5, 2014 at 12:16 PM, Mickael Istria <[email protected]> > wrote: > >> Yes, 0.0.0 works in a target, but it's not a very safe approach. >> Indeed, you basically want in your .target artifacts that you have tested >> or verified and that you're ok to use or include. Putting 0.0.0, you don't >> know exactly which artifact you'll get. Some project may not like this (for >> example, in JBoss Developer Studio, we don't allow 0.0.0 because we want to >> know and control what gets in and what doesn't). >> >> -- >> 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> >> >> _______________________________________________ >> nebula-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/nebula-dev >> > >
_______________________________________________ nebula-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/nebula-dev
