<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>On the other hand, changing a jar in the runtime environment without compiling and running test with the new jar could lead an application to stop functioning in a customer environment.</div><div>Also not every bug found in a dependency jar would cause a problem in the application. (An application might not use the problematic part of the dependency.)</div><div>I'd better trust the test suite (automatic and manual) that we run on the compiled application with all the dependencies that the developers choose at the development time and then deliver that (with its dependencies as a single package) to the customers.</div><div>Every bug in a dependency should be evaluated within the given application scope and only if proven as the given application problem only then the application should be released.</div><div><br></div><div><br></div><div><div style="font-size:75%;color:#575757">Sent from Samsung Mobile</div></div><br><br><br>-------- Original message --------<br>From: Alon Bar-Lev <alonbl@redhat.com> <br>Date: 07/05/2014 21:41 (GMT+02:00) <br>To: Mike Kolesnik <mkolesni@redhat.com> <br>Cc: Yevgeny Zaspitsky <yzaspits@redhat.com>,devel@ovirt.org <br>Subject: Re: [ovirt-devel] commons-collections v4.0 <br> <br><br><br><br>----- Original Message -----<br>> From: "Mike Kolesnik" <mkolesni@redhat.com><br>> To: "Alon Bar-Lev" <alonbl@redhat.com><br>> Cc: "Yevgeny Zaspitsky" <yzaspits@redhat.com>, devel@ovirt.org<br>> Sent: Wednesday, May 7, 2014 9:34:03 PM<br>> Subject: Re: [ovirt-devel] commons-collections v4.0<br>> <br>> ----- Original Message -----<br>> > <br>> > <br>> > ----- Original Message -----<br>> > > From: "Yevgeny Zaspitsky" <yzaspits@redhat.com><br>> > > To: "Alon Bar-Lev" <alonbl@redhat.com><br>> > > Cc: devel@ovirt.org<br>> > > Sent: Tuesday, April 22, 2014 11:39:11 AM<br>> > > Subject: Re: [ovirt-devel] commons-collections v4.0<br>> > > <br>> > > That means that we manage 2 separate environments:<br>> > > 1. Development - relies on pom files. E.g. unit tests run with<br>> > > commons-collections v3.1 (and when I add v4.0) and succeed.<br>> > <br>> > devenv will use runtime option.<br>> > you are right about the unit tests, these relays on the poms.<br>> <br>> I use devenv and it always uses the dev option not the runtime.<br>> So basically developers are using the pom specified versions and not what<br>> used in runtime.<br>> <br>> Even more so, in runtime it highly depends on what OS you're using, so<br>> someone<br>> developing on F19 might not be using same versions as a developer on F20 and<br>> both are probably very different versions than on RHEL/CentOS.<br>> I won't even mention other OS`s.<br>> <br>> > <br>> > > 2. Run-time - relies on JBoss own dependencies that bring<br>> > > commons-collection<br>> > > v3.2.1-redhat-2.<br>> > <br>> > in rhel case, yes.<br>> > <br>> > > This kind of discrepancies might be found in other libraries as we do not<br>> > > synchronize our pom files with the JBoss current version dependencies.<br>> > > IMHO that could lead to some very difficult bugs that we won't be able to<br>> > > simulate in our unit tests.<br>> > <br>> > correct, but the java way to pull dependencies at will without being able<br>> > to<br>> > fix z-stream using central package management tools is more severe than<br>> > unit<br>> > tests not working/not working.<br>> > <br>> > for example, your application uses x.jar and actually delivers x.jar... so<br>> > from release to eternity it is your responsibility to track x.jar for<br>> > severe<br>> > stability bugs and security bugs, and release your entire application each<br>> > time found, now multiple it with the # of components application is using<br>> > and see how much effort you have just to maintain stability and security if<br>> > you embed 3rd party components without your application.<br>> <br>> Yes, if you use package X then you're using that specific version with it's<br>> behaviour and API, this is why dependencies aren't updated light headedly but<br>> with testing to see that nothing broke (since stuff does break, even in minor<br>> version, as we leave in a not so perfect world).<br>> <br>> > <br>> > > Why do we avoid "to maintain our own packaging"? IMHO Ovirt own<br>> > > dependencies<br>> > > could be packed in the war, can't they?<br>> > <br>> > yes they could, but this is not suitable for enterprise grade<br>> > implementations, mainly per what I described above.<br>> <br>> Sorry but AFAIK enterprise grade software release fixes for their software<br>> on a timely basis and have processes in place to manage upgrades of<br>> functionality.<br>> <br>> What currently is done is relying on courtesy of other people to release a<br>> "fix" that already exists a long time.<br>> And of course, as I mentioned, the application needs to be tested with the<br>> updated library.<br>> IMO neglecting this and leaving this out of band for "enterprise grade"<br>> software is much worse than actually testing to see that it is working and<br>> just leaving it all to chance.<br><br>Well, take the recent example of openssl issue that was found.<br>Now, imagine that all products that use openssl should have been re-released.<br>I think this is enough to understand how wrong this is.<br><br>> <br>> > <br>> > Regards,<br>> > Alon<br>> > <br>> > > Best regards,<br>> > > ____________________<br>> > > Yevgeny Zaspitsky<br>> > > Senior Software Engineer<br>> > > Red Hat Israel<br>> > > <br>> > > <br>> > > ----- Original Message -----<br>> > > From: "Alon Bar-Lev" <alonbl@redhat.com><br>> > > To: "Yevgeny Zaspitsky" <yzaspits@redhat.com><br>> > > Cc: devel@ovirt.org<br>> > > Sent: Sunday, April 13, 2014 7:22:18 PM<br>> > > Subject: Re: [ovirt-devel] commons-collections v4.0<br>> > > <br>> > > <br>> > > <br>> > > ----- Original Message -----<br>> > > > From: "Yevgeny Zaspitsky" <yzaspits@redhat.com><br>> > > > To: devel@ovirt.org<br>> > > > Sent: Sunday, April 13, 2014 7:13:10 PM<br>> > > > Subject: [ovirt-devel] commons-collections v4.0<br>> > > > <br>> > > > Hi All,<br>> > > > <br>> > > > I'd like to add the new version (4.0) of Apache commons-collections<br>> > > > library<br>> > > > to the dependencies of the project (we use 3.1 currently).<br>> > > > The new version uses the generics features of Java 5 so that make the<br>> > > > code<br>> > > > more type safe. You can find the full list of changes on<br>> > > > https://commons.apache.org/proper/commons-collections/release_4_0.html.<br>> > > > The new API is based on the original but it isn't fully compatible with<br>> > > > it.<br>> > > > So in order to make the migration to the new API easier, the package<br>> > > > has<br>> > > > been changed to org.apache.commons.collections4. That allows having<br>> > > > both<br>> > > > version of the library in the classpath at the starting point and move<br>> > > > (refactor) towards the new version gradually.<br>> > > > <br>> > > > I have couple of questions regarding the new dependency:<br>> > > > 1. Is there anything that could prevent adding the new dependency?<br>> > > <br>> > > We try to avoid introducing our own dependencies, in this case we use<br>> > > whatever jboss provides which is very comfortable as we do not need to<br>> > > maintain our own packaging.<br>> > > <br>> > > Currently the jbeap does not provide 4.0, it does support 3.2.1-redhat-2,<br>> > > so<br>> > > better to avoid this until we switch to more recent version of jboss.<br>> > > <br>> > > Alternatively we could enjoy standalone rpm within rhel/centos if<br>> > > available,<br>> > > however non exist.<br>> > > <br>> > > > 2. I did the change (http://gerrit.ovirt.org/26745).<br>> > > > The unit tests that use the new dependency pass locally and in<br>> > > > Jenkins<br>> > > > environments.<br>> > > > However when I try to run a code that is dependent on the newly<br>> > > > added<br>> > > > library NoClassDefFoundError being thrown.<br>> > > > Also I can't find commons-collections4 jar under the installation<br>> > > > directory. I use "make clean install-dev" command for building.<br>> > > > <br>> > > > Please advise.<br>> > <br>> <br></body>