It's always a bit of a maze, isn't it! Thanks for looking into this Aled. I think it will be great to get things brought up to a consistent level with this latest Karaf.
Cheers Geoff On Mon, 2 Dec 2019 at 13:28, Aled Sage <[email protected]> wrote: > Hi all, > > TL;DR: I'm looking at upgading CXF from 3.2.8 to 3.3.2. > > --- > > For dependency: > system//javax/mail/mail: [1.4.7, 1.4.4] > > Exploring this one shows that v1.4.4 is coming from the old cxf-specs > 3.2.8. The Karaf 4.2.7 announcement [1] gives a table of versions - it > shows CXF at 3.3.2. We should look up updating CXF from 3.2.8 to 3.3.2. > > That will also require an upgrade of mvn:io.cloudsoft.windows/winrm4j > (as v0.7.0 is built against CXF 3.2.8). > > I'm looking into this, to see what else breaks when we switch to CXF 3.3.2. > > --- > > I suggest we ignore: > system//org/apache/aries/spifly/org.apache.aries.spifly.dynamic.bundle: > [1.2.2, 1.2] > > Feature 'jetty' brings in v1.2.2, whereas feature 'pax-jetty' brings in > v1.2, so it's out of our control. > > Aled > > > On 02/12/2019 10:38, Aled Sage wrote: > > Hi all, > > > > I see there was great progress with the karaf version bump last week > > and over the weekend, e.g. [1, 2]. > > > > Looking at brooklyn master karaf dependency versions using `find > > ${BROOKLYN_HOME}/system/ -name "*.jar"` and running a little program > > to find multiple versions, I see the following concerning duplicates: > > > > system//org/apache/aries/spifly/org.apache.aries.spifly.dynamic.bundle: > > [1.2.2, 1.2] > > system//javax/mail/mail: [1.4.7, 1.4.4] > > > > The full list is: > > > > system//org/ow2/asm/asm: [5.2, 7.1] > > system//org/ow2/asm/asm-util: [5.2, 7.1] > > system//org/ow2/asm/asm-tree: [5.2, 7.1] > > system//org/ow2/asm/asm-analysis: [5.2, 7.1] > > system//org/ow2/asm/asm-commons: [5.2, 7.1] > > system//org/yaml/snakeyaml: [1.23, 1.17] > > > system//org/apache/servicemix/bundles/org.apache.servicemix.bundles.jzlib: > > [1.1.3_2, 1.0.7_1] > > > system//org/apache/servicemix/bundles/org.apache.servicemix.bundles.okhttp: > > [3.4.1_1, 2.2.0_1] > > > system//org/apache/servicemix/bundles/org.apache.servicemix.bundles.okio: > > [1.9.0_1, 1.2.0_1] > > system//org/apache/aries/spifly/org.apache.aries.spifly.dynamic.bundle: > > [1.2.2, 1.2] > > system//javax/mail/mail: [1.4.7, 1.4.4] > > system//javax/ws/rs/javax.ws.rs-api: [2.0.1, 2.1.1] > > > > Compare this with Brooklyn version 1.0.0-M1: > > > > system//org/ow2/asm/asm-all: [5.2, 5.0.2] > > system//org/yaml/snakeyaml: [1.17, 1.22] > > > system//org/apache/servicemix/specs/org.apache.servicemix.specs.activation-api-1.1: > > > [2.5.0, 2.6.0] > > > system//org/apache/servicemix/bundles/org.apache.servicemix.bundles.jzlib: > > [1.1.3_2, 1.0.7_1] > > > system//org/apache/servicemix/bundles/org.apache.servicemix.bundles.okhttp: > > [3.4.1_1, 2.2.0_1] > > > system//org/apache/servicemix/bundles/org.apache.servicemix.bundles.okio: > > [1.9.0_1, 1.2.0_1] > > system//org/apache/aries/org.apache.aries.util: [1.1.3, 1.1.0] > > system//com/google/code/gson/gson: [2.5, 2.3] > > > > I'll take a look at these and see if they really are a problem or not. > > > > Aled > > > > [1] https://github.com/apache/brooklyn-server/pull/1068 > > > > [2] https://github.com/apache/brooklyn-server/pull/1069 > > > > > > > > > > On 02/12/2019 09:27, Aled Sage wrote: > >> Hi, > >> > >> Thanks Ludo, all: - great list, and +1 from me. > >> > >> I think most of those sound fairly small and manageable. > >> > >> The one that stands out as potentially hard is the "Karaf version > >> bump" (which would fix the "Two different versions of jetty-server"). > >> We've had problems in the past getting all versions consistent, and > >> karaf to start up fast and cleanly (without it restarting a bunch of > >> bundles). Changing the version is really easy - getting all versions > >> of all bundles to be consistent can be a pain! But it's worth doing. > >> > >> Aled > >> > >> > >> On 01/12/2019 14:47, Geoff Macartney wrote: > >>> We should definitely include > >>> https://issues.apache.org/jira/browse/BROOKLYN-597 "Remove MD5 and > >>> SHA-1 > >>> checksums" as part of 1.0.0. I'd be happy to do this but I see it's > >>> got > >>> you assigned to it Richard. Do you have work in progress on this, or > >>> would > >>> you like me to look into it? I have a notion that I might polish up the > >>> signing procedure a bit. > >>> > >>> Cheers > >>> Geoff > >>> > >>> On Sun, 1 Dec 2019 at 14:13, Geoff Macartney > >>> <[email protected]> > >>> wrote: > >>> > >>>> Hi Ludo, > >>>> > >>>> I am indeed pleased to see this! I had been thinking of mailing the > >>>> community again on the matter after Christmas was out of the way, > >>>> let's let > >>>> 2020 be the year of Brooklyn 1.0.0! > >>>> > >>>> That's a great list of things to address. One thing to add would be > >>>> removing some deprecated code. Do you think they are all small > >>>> changes, or > >>>> do any require extensive work or have a wide impact? > >>>> > >>>> The reason I ask is that I think it would be good to restrict > >>>> ourselves to > >>>> relatively easy and limited impact changes between now and 1.0.0. > >>>> My fear > >>>> is that larger changes will take a longer time and push back a > >>>> release even > >>>> further. It seems to me things are quite stable now; I'd say let's > >>>> polish > >>>> it up and release it rather than try to make significant improvements. > >>>> > >>>> What does everyone think? > >>>> > >>>> Cheers > >>>> Geoff > >>>> > >>>> > >>>> > >>>> > >>>> On Thu, 28 Nov 2019 at 11:04, Ludovic Farine <[email protected]> > >>>> wrote: > >>>> > >>>>> Hi everyone, > >>>>> > >>>>> Hope you are all doing well! > >>>>> > >>>>> Christmas is fast approaching and well hopefully a gift we would > >>>>> all like > >>>>> to have: Brooklyn 1.0.0 release :) Geoff would be pleased to hear! > >>>>> > >>>>> Working towards this goal of first official release, these are a > >>>>> few bug > >>>>> fixes and improvements that I believe are worth considering > >>>>> (non-exhaustive > >>>>> and not ordered wishlist!) : > >>>>> > >>>>> Bug fixes: > >>>>> > >>>>> - > >>>>> > >>>>> Broken icon links for ELK and DNS entities > >>>>> - > >>>>> > >>>>> REST API Swagger error > >>>>> - > >>>>> > >>>>> Two different versions of jetty-server > >>>>> - > >>>>> > >>>>> Karaf version bump > >>>>> > >>>>> > >>>>> Improvements: > >>>>> > >>>>> - > >>>>> > >>>>> Session Management: introduce expiry settings for inactivity or > >>>>> repeated > >>>>> background API calls > >>>>> - > >>>>> > >>>>> User Experience: blueprints ordered by date deployed, cookies to > >>>>> remember preferred sort criteria and palette preferences > >>>>> > >>>>> > >>>>> Clean-up: > >>>>> > >>>>> - > >>>>> > >>>>> Review existing open Pull Requests > >>>>> - > >>>>> > >>>>> Fix most of the Jenkins tests > >>>>> > >>>>> > >>>>> What are your thoughts on this scope? Any other suggestions you > >>>>> would like > >>>>> to deliver in this next release? > >>>>> > >>>>> Looking forward to get the community engaging in the next weeks and > >>>>> months. > >>>>> > >>>>> Remember you can participate with others on the official Slack > >>>>> channel > >>>>> *#brooklyn* on the official Apache group. Sign up here > >>>>> https://s.apache.org/slack-invite to join the discussion! > >>>>> > >>>>> Thanks > >>>>> > >>>>> Ludo > >>>>> > >>>>> > >>>>> -- > >>>>> > >>>>> Ludovic Farine > >>>>> > >>>>> Senior Technical Project Manager > >>>>> > >>>>> > >>>>> Cloudsoft <https://cloudsoft.io/> | Bringing Business to the Cloud > >>>>> > >>>>> E: [email protected] > >>>>> > >>>>> T: +44 7584 748013 > >>>>> > >>>>> L: https://www.linkedin.com/in/ludovicfarine/ > >>>>> >
