On Mon, Dec 5, 2016 at 5:11 PM, Robert Varga <n...@hq.sk> wrote: > On 12/05/2016 04:55 PM, Michael Vorburger wrote: > > > > The thing is, opendaylight-karaf-empty zip is actually ~112 MB. > > This file is downloaded whenever we perform a singleFeatureTest (to > > my understanding), which probably puts a lot of stress on nexus, > > especially when not all the features are necessarily needed. Is > > this something we could disable and allow singleFeatureTest to run > > in a non-offline mode? I am not quite sure the implications of > > doing so, and that is why I decided to pose the question to these > > mailing lists. > > > > > > did you ever get any replies to this? I had raised a similar Q in "Move > > opendaylight-karaf-empty (and opendaylight-karaf-resources) to fixed > > version", although I came at it from another angle - I'm questioning why > > opendaylight-karaf-empty has to be a daily SNAPSHOT, and suggested to do > > something about that.. let me bump that thread and add you directly. > > The answer to this ... depends. karaf-empty is pulling in our branding, > which may be something which changes during a release. >
Sure. I'm not saying it shall never ever change anymore. I'm just observing that it changes far far less than once every day, and that thus its very frequent SNAPSHOT are probably causing all of us much more pain than gain? > I think this would be doable if we had a karaf-packaging base project, > which would release on its own and would then be pulled into odlparent > -- that would achieve this without going for all of the version skew > induced by having an odlparent version bump going on... > Does opendaylight-karaf-empty's version *HAVE* to identical to the odlparent version? Why? How about odlparent/karaf has a separate versioning than the rest of odlparent? Regards, > Robert > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
