Jakarta EE JakartaOne Livestream 2022, 15 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: What's Cooking in Maven? - JakartaOne 2022

Description

It’s been over 10 years since Maven 3 saw the light, bringing initial multi-module support. Later releases brought a lot of improvements, bug fixes, and of course coloured output.

But the Maven community hasn’t been resting on their laurels. A lot of effort has gone into the future of Maven. You may have heard about Maven 4, Maven Wrapper, or Maven Daemon. Why should you care? And how will it change the way you use Maven? I will show you by using the latest snapshot builds of Maven - time will tell if that’s a brave or a stupid idea…

Join me to find out what the future of Maven has for you!

-

Jakarta EE gives developers a comprehensive set of vendor-neutral, open specifications that are used for developing modern, cloud native Java applications from the ground up. With Jakarta EE, technology developers and consumers can be confident they have the best technologies for developing cloud native, mission-critical applications. And they can build on decades of Java developer expertise to move existing workloads to the cloud.

Learn more: https://jakarta.ee/

Follow us on Twitter: https://twitter.com/home
Follow us on LinkedIn: https://www.linkedin.com/showcase/jakartaee/
Like us on Facebook: https://www.facebook.com/JakartaEE/

A

A

So nice to meet you all. Thank you for joining me. My name is Martin and I'm going to discuss with you what's cooking in maven, but before we do that, I have a little question for you. Can you tell me Well? The difference is between those two and maybe the Emojis already give it away a little bit on the left hand side.

A

We say you see the spring initializer website which by default suggests you to generate a Gradle project on the right hand, side we see the micro profile startup website which by default, suggests to generate a maven project for you- and this is not a coincidence. The spring team actually delivered deliberately chose to migrate to Gradle as a default choice for our build tool. They have a GitHub issue, describing the choice and the rationale behind it and somewhere in that issue.

A

There's a comment from a fellow Maven committer, Martin counters, who says I wanted to mention that Maven is working on a lot of nice things that were mentioned above most of them are already available for use, and it's exactly those things that I would like to share with you today.

A

So without further Ado we're going to discuss what's cooking in Maven, as I said, my name is Knighton murders, I'm, a Java, Champion I'm, an oracle age, Pro and I'm I'm working at infos report.

A

If you would look us up we're a consultancy firm and you might be wondering what is a consultancy firm doing in terms of apogee Maven, which is an open source project after all? Well, the thing is that we benefit from open source in a lot of the projects that we run with our customers and in the true Spirit of Open Source. We decided that we would like to give back to the community and we do that by providing mad hours or working time actually to contribute into the project report.

A

Issues fixed issues contribute new features Etc, and it's in that capacity that I'm speaking about Apache Maven today, so we'll be discussing a few things that are cooking in Maven. uh We will be doing that in the form of a traditional French, four course dinner, so the menu du jour or the menu for today consists of an entree which, which will show the maven wrapper.

A

We will have our plot principal or main course, which is going to build to be the build and consumer Pond D coupling the formation, the cheeses that go after the main course is a couple of nice improvements in the reactor, and we will wrap up with the dessert, which is going to be the maven demon.

A

If you have any questions, I would really like to answer them. Please keep them until the end of the talk, and then we will have some time left to discuss any questions you may have.

A

So let's get started with the entree or the.

A

The English word never mind uh it's going to be the maven wrapper and if I say Maven rapper, you might be thinking hey. We already know that one right I mean the maven wrapper is not something that is really new. So, let's, let's take a step back for a second and see what the maiden wrapper is all about. The maven wrapper is actually a little utility that helps us, ensure that the users of our open source project or actually our project in general, uh have everything that they need.

A

So they can build a project and typically, the version of Maven does not really make a big difference, but in some cases it may and we maybe we don't even want to force our users to download Maven up front. That's why we can use made from wrapper, because Maven wrapper will actually um download Maven, even if the user does not have it installed.

A

The maven wrapper is a uh is a shell script which runs on Linux Mac, OS Solaris. It even runs on Windows. Can you imagine that?

A

And it makes sure that we as project maintainers, do no longer have to worry about the version of Maven that my users may have I. Don't have to write something in my readme like make sure that you use Maven at least version this or that, because the wrapper will automatically download the appropriate version for me. So.

B

A

To the kitchen and let's get cooking and see how that actually works now I've prepared a demo for that.

A

Here we have a project which is uh nothing too special. In fact, I can actually open it in an editor, and we can see that we have a bundled XML which just as well, we use magazines, use Java 17 and for uh there's nothing special in terms of the project I mean except for that.

A

So what can we do here? We can actually generate the wrapper script and we used to be doing that using uh maven. um Wait, there's a quick way to do that. We can just say, run the tikari wrapper for me and it runs the takari maven wrapper plugin, which generates a rubber Forest.

A

This is what we had for years already. It will generate a maven wrapper folder. It will generate nvnw and nvmw.c and D, but as I said, this is the takari wrapper, and the thing that is changed now is that we have um ported that or actually moved that into the umbrella of the Apache software Foundation.

A

So let's remove the generated wrapper stuff and let's generate the wrapper again this time using another helper script, which will just say, run wrapper, column, wrapper and use Maven 386. Well again, it says build success, which is great, and we can see again that we have a maven W script, a maven w c and d and a DOT nvn folder, but the proof of the pudding is in the eating. So, let's see if it actually runs, and for that I'm going to spin up a clean environment. Well that works actually better if Docker is running.

A

So let's wait a second for that to boot.

A

So what it's going to do is going to spin up a clean, Linux container with only Java installed, but not with me even installed.

A

Let's try it again.

A

There, it is no, it's still not there to add still booty.

A

Yes, there we have it so just to double check. We have Java installed with version 17, but we do not have and Maven installed, because if we run nvn we cannot uh run that, but we have our executable helper script and vmw and we can run that and say, for instance, validate my project Channel and it will immediately start validating the projects.

A

This wasn't too much fun because it was actually all there. Let's make it a really clean environment, all right, excellent, um let's see product has been built. We could even compile it like. So.

A

We can see that it downloads everything which is is expected because we did not have Maven installed in front now. How does that work? It works because here in the M24 that we know for its repository, we also found. We will also find the wrapper folder, which contains a distribute distributions folder, which then contains the version of Maven that we expect to be there and then finally, we have a bin folder, and that shows us the clean, Maven installation that has been downloaded. We could remove that.

A

We could run the project again with the nvmw wrapper and then again, Maven is going to be downloaded and even when I did not have Maven installed, I can still run Maven because that prerequisite is going to be downloaded for me.

A

So, as I said, this is isn't too much of a rocket science, it's something that has been there already, but it requires to use an external plugin. Now it's part of Maven itself, we'll ship with uh it will actually be easier to invoke because, rather than running IO otakari colon wrapper, we can run Maven wrapper at the end of the day. But later more about that later, in a talk, foreign just to get started to boost up our appetite a little bit.

A

And the main course for today is going to be the build and consumer Palm decoupling, and this is a rather technical Improvement that we brought into Maven, but it's really essential, as we will see in a minute. So what does it do to build consumer pump? Decoupling, as the name already suggests, we'll decouple the pond that we have in Version Control from the poem that lives in a repository, so the problem that gets deployed to your local repository or to a company repository like artifactory or or whatever, or even to made in central.

A

B

A

Have until today is that the palm.xml that we have in Version Control is literally copied deployed into a a logo, a company or even the central Maven Repository.

A

There are a few exceptions to the rule if we would use, for instance, the maven flatten plugin, a few Transformations can be done to get from the project structure that lives here until the pond that is deployed up there. But generally speaking, it's the it's the very same file, and this is actually something that poses a few interesting problems.

A

So what the build build and consumer Palm decoupling does for us is that it says well the pawn that we deploy no longer has to be the very same file as the file that lives in your project structure.

A

So why is this interesting? Well, this actually is the first step on the road to um to transform the pond that we know today. Let's imagine for a second that we have made in six and in Maven six. The structure of the bomb is completely different from the bomb that we know today and that we have today if I would be using the iPhone 6 to build my project and I would be deploying the very same bomb file that lives in my project structure to Maven Central.

A

It would mean that whoever is going to download that project from me in central is going to get a poem that works on Maven 6., but if they are on Maven, five or four or three or even two as for today, there are still people using Maven, 2 and well, that's fine, because it's a very stable product, it would mean that they will get a pawn.xml from Central that their tool simply doesn't understand and that's going to be quite a problem for them, because their two will say: there's an invalid poem. I can't process this.

A

This dependency for this plugin. So by saying the pawn that we have on disk is not the same as the permit gets deployed. It allows us to say well, our project uses- let's say maybe six, but before we deploy the Palm to Mainland Central, let's transform it to make sure that it is valid even back until maybe three or two or whatever we choose to, and this is a very important step, because we would not do this.

A

It would simply be impossible to trans to um to to to to change the structure of the poem that we have today and the important uh constraint here is that we do want to change the point we do want to be able to do that without breaking the whole ecosystem. That Java relies upon. Let's face it, even if you say well, I'm, not a big Maven fan. I I'd rather use Gradle the Palm dot XML that lives next to each jar in Mason.

A

Central is kind of the Cornerstone for the Java ecosystem and for for a lot of tools, whether it's Ivy, whether it's great or whether it's as BT, they all rely on the pond.xml to contain a metadata for each artifact that they download. So we have to be sure that that thing is very, very stable.

A

So again, let's move to the kitchen. Let's see what it actually looks like if we do this and for that I have prepared another demo, which is very interestingly named, to build consumer pump.

A

Decocking, um let's see build consumer, that's this one and um this feature is not in Maven free but um I'm using or it is not a maven free um so to make sure that I'm using Maven, free I'm, going to type Maven free here and I can also type mav4, which is going to be a snapshot of what is going to be Maven. For. Let's just highlight that for a second mvn free says, I'm using Maven, 386 mvn4 says I'm using made 400 Alpha free snapshot, so just to get that out of the way.

A

So I can say. Maven-Free uh compile, for instance, and I can build my project, which is just fine.

A

And we can see here that we have a project which consists of an application and a library and a a root project.

A

That's also highlighted um here the application, the library and the root project. Now, if we have such a setup, it usually requires us to stay okay in the lib, so in any child project. I need to specify the version of my parent right.

A

If I would do this, for instance, and I could do the same thing in the app by the way then Maven free will not be able to compile the project because it says hey, you need to have parent version specified and you did not now if I would be using Maven 4 making four will say: oh that's, fine I can just compile it. Why does it work because Maven 4 says okay by convention or actually by convention by specification?

A

There's also a relative path here, and we typically don't specify it because it's default value, which is this it's just fine. Now, if the relative profile is not specified, then it is the upper directory. So, let's inspect the open directory, which is this form and see if the group ID and artifact ID match with what we have here they do so then the version doesn't really matter.

A

You could still specify the version to actually pin it, but if you want your child's modules to um to version in the same way as your parent module, then you can just leave it out.

A

You could even say: hey. I have a dependency on another module in my project, and here again we always need to specify the version, even if the dependency to that other module is the same version as this module well with Maven 4. We no longer have to do that. So I can still safely compile my project. What I could even do I could install my project and then then we will see something interesting. Apart from the fact, of course, that project still builds fine.

A

We can inspect the palm.xml here that just got deployed and we will see that it still has the version in the parent reference and the version in the app to lib dependency. So I did not specify them in the poem.xml that I have in Version Control for my project, but when I deploy it to my local repository or to Maven Central. For that matter, then the build consumer pump.

A

Decoupling will actually fill in the gaps fill in the blanks and make sure that the Palm is still valid for Maven, free or imagine two for that matter. So I'm using a newer version of Maven here to build the project, but any consumer of my project, who is not on Maven 4, yet can still safely use the artifacts that I have published, and that, in a nutshell, is what the build consumer pump decoupling does.

A

We can also see that without installing, by the way we can say, help effective boom and it will do the same thing.

A

It will output the effective form.html and that we will also see if we browse up a little bit. The version for the parent specified and the version for our dependency is specified as well.

A

So that was our main course: the decoupling of the bill and consumer pump it's time to move to the formage Jesus.

A

Which are a couple of nice improvements in the maven reactor? So what is the maven reactor? A major reactor is actually the part of Maven that inspectual workspace so default where you're currently in spects, the project builds up. The structure builds up so as to say the mental model of what your project structure looks like, and this is especially relevant in the context of multiple module projects.

A

Now the thing is when it was built into Maven free. There were a few things left um well, not implemented. Yet, let's put it that way. For instance, if you would uh say I'm going to build only a submodule of the project, then what Maven will do?

A

It would inspect the pom XML in your current folder and it would say: okay, this is the project I'm going to build it, but if that project is actually a part of a multi-module project, it has a parent in the upper folder, then making free would not recognize that so I would consider the project to be standalone rather than trying to understand the fact that your project is part of a bigger whole and that's what we've been addressing for maven 4., we used to say describe it like this.

A

The reactor is now fully root project aware, so it understands that whether you're building the whole project or just a part of it, it's always the whole project that it will. It will always consider the whole project rather than just a folder that you are currently building or the public you're. Currently building. There's one caveat for this: your project should have a DOT mvn folder. Then the mvn folder should live at the root of your project structure and it's um and you can even leave that folder anti.

A

It's no problem, but it it serves as a marker for Maven to understand. If I'm traversing up the directory structure at some point, I can stop doing that. Otherwise I would be traversing up all the way until slash on Mac OS and line Edge or all the way up until C drive on Windows, which doesn't make sense I'm not going to find any more Maven projects there.

A

This folder.mvn is the marker. This is the root folder of the project and inside that folder you can put additional files. Jbn.Config maven.org the main wrapper actually lives there, but even if you don't use any of these, you can have the folder and just keep it empty, make sure it's checked into Version Control, so that others will benefit from that as well yeah, and why is this important?

A

It's important, because um I believe that the fact that Maven free did not um was not aware of the the root project in a multi-module setup was actually one of the main courses for people still being used to typing nvn install to build their projects. I've. Seen way too many projects that had instructions like before working on the project make sure to run the mbn install first, which actually is just not right.

A

You shouldn't be doing that. It's it's actually a workaround for the fact that Maven does not work as one would expect. So, let's see what that means in practice, I have a new project for this. um What's its name again: um yes, there it is improved reactor and, let's inspect the project for a second. In the editor we see here a similar structure, as we just saw. We have an application which relies upon an API module and the API module has an implementation module.

A

Now, let's try to see what that means. In practice, the coffee shop app uses a particular API and the API is implemented by that other project and that other module file, if I, would be building the project with.

B

A

A

It would be fine because I'm building a group project here.

A

Let's say that we do test driven development, so I'm going to run measurement free test.

A

Now I'm greeted with a failing test case. Well that makes sense. If we do test driven development, we we start a test. We we start by writing the test, and then we try to make the test green. This test is red, so we have to fix. It makes perfect sense, and the test that we are talking about is the bean burner ample test.

A

Blitz pick it up it's over there, the test folder, that we have it and we have a bean grinder we've thrown some beans, and we expect that we get something back, but we do not. Why do we not get something back? Test is failing it's probably because we haven't implemented it yet. Well, it doesn't have to be hard. We can just return some objects and then at least our test will be green right, because the result is now no longer a no value. Well, Maven is very helpful to us.

A

It says you can correct a problem and then you can resume the builds. Well, let's try to do that. Let's try to resume the build Dash RF for resume from and I can resume from the coffee shop. Import module foreign.

A

Tests now my build is still failing and there's an interesting thing happening here um earlier.

A

We would see improve reactor demo, then API, then implementation, then app now Maven free, says: okay I'm going to to build the implementation for you, but that's not what I asked for or well it's what I asked for, but here we can see that a maven does not understand that. There's a parent project, and actually that's also what it's saying over here. It's saying I have a dependency on the coffee shop API, but I cannot find the Palm for it.

A

I don't have any dependency information, um and that also means that I can't resolve the dependency at all, which is why the build is fake. That's a bit of a shame because earlier it said that we could resume the build like that. But in fact we cannot.

A

That's run this scenario again I'm going back to a failing test case. This time we've made four I'm going to run an amazing four test. Now we expect the test still to be failing and now there's a slightly slight difference. First of all, it says, after correcting the problem, you can resume the build with nvnr Dash R, which is just resume so rather than Maven. Telling me hey.

A

I, got this far good luck, figuring out and resuming the bills for me. Maven now says I got this far, but if you invoke me a second time, I know where I left off and I can resume from there. So, let's again make sure our test will pause. Oh wait before we do that.

A

We need to take a little look at this file, because here it says in this property file target resume properties. It says remaining projects, so that's the projects that we still have left to build is to go shop, import and the coffee shop API app module. Those are still left to be built now back to the terminal.

A

Maven resumed the build run, the test goal.

A

And it says all right: build success, I've managed to build and test the implementation and build and test the app itself. As I said, it remembers where to resume from based on that resume properties file. But the more important thing is what it Where, Maven first, would say: okay, this is the project that you want to build. Let me try to build it.

A

It now first builds the model of the whole project, so the military module project, including the parent, including all the other modules in the project and damage trips of what has already been done, leaving what is left to be done then starts to build up, but if you then have a dependency from, let's say implementation on API, it says: okay, even though I'm not going to build the API I do know where to find it, because it's in the it's in a folder next to this one and I can resolve the dependency from there before we've made them free.

A

This was not the case, and that's why many project instructions still say you need to run Maven install first, because we may even install it will install this API module in the local Repository that that's the M2 repository folder under your user directory and from there I'm going to resolve it during the build.

A

Now this is one thing that we have improved in the reactor, but there's also a lot of other things that the reactor can now do, which it could previously enough do so. We have options for, uh for instance, for saying I can build just one sub module. Let's say the uh coffee shop API, uh no, the app module.

A

Compile, of course,.

A

um I could do that with or without, and also make switch.

A

This was there before, but again it would not understand if I have a dependency from the app on the.

A

On the implementation, it would say, I don't understand how that is going to be how that needs to be built. We've made before it says: okay, I can actually resume that dependency inside the project and I can build it even without saying, am stands for also make, which means that if I do this to make a free build to the golf shop, app module, we've also make it would compile both the API and the implementation and the app all three of it.

A

Whereas we've made before, if I do this, it will build only the app and it will resolve the API in the implementation without building them. So this is this. Is this allows you to have a much more fine-grained control on what is going to be built or not?

A

We have um profile activation, which now also works for profiles that may or may not be there.

A

So let's say that I can't I could say: um um let's see.

A

A

The profile switches Dash- this is capital, P I, could say run. It's believe this is the right syntax, but I need to do compile to.

A

Yeah, so now it says, requested profile could not be activated or deactivated because they don't exist. If I wouldn't have been doing this with Maven free, it would have said um it's, it's considered a warning and it says, requested profile run it's with a question mark, so it made from free. One would do this and would say run its could not be activated.

A

uh That's a warning, and in May before we can say well, if it exists the run its profile, then I would like it to be activated, and otherwise it's not a problem, and that's why the warning has become an info message because I specified that if it's not there, it's not a problem. On the other hand, if I would say activate this profile, but I do not give the question mark I'm saying the profile must be there and then Maven stops with an error.

A

Saying you requested a profile, but I could not activate or deactivate it because it simply doesn't exist, and this is more in line with how the project selection also works.

A

All right um enough about this there's a lot of a lot more things, but we still have to finish our dessert and it would be a shame if we had to forget that foreign demon.

A

Now, what's the Raven demon all about.

A

The maven demon is actually a a new project in the maven uh Under, the Umbrella of the American top level project with India Apache software Foundation that provides faster, builds well, I, don't know about you, but if my build can get faster, I'm, typically a very happy user, and how do we do that? We do that using a demon process.

A

B

A

Is actually a background process that keeps the jvm that was used to invoke Maven and the plugin definitions uh warn so what we typically do if we run mvn, is a shell script or a CMD script that boots a jvm starts. Reading the project reads all the plugin definitions and then finally gets to the point where I can build my project.

A

The amazing demon, on the other hand, says okay, the jvm is there, I'll, keep it in a steady state in a ready state, I've loaded, all your project, plugins and now. The only thing that I have to do is tell this jvm to to run a particular goal on the project.

A

What it also does is that it runs a multi-friendly build by default without cluttering. The output. Well, there's a lot of things that were on that previous list. So, let's see in practice what they mean and for that I'm moving to a different project which is going to be just Maven itself, because that project is a little bit bigger than my usual demo. Projects.

A

A

I'm going to clean the projects, this is always a bit of a scary moment, because demos can easily go wrong, but let's assume that they will run just fine today and otherwise. I have a backup plan. Don't worry so, as you can see, the maven project itself consists of 30 modules and if I would be running a maven compile on it and that's going to be Mason free.

A

Of course, we can see that it runs in sequence, so it says: there's 30 modules and I'm going to build the first one, the second one, etc, etc, etc.

A

That's a bit of a shame. We have a bill to you here.

A

Let's go back to the backup plan, then.

A

A

It will say it starts a new demon, that's expected, because no, there was one. There was not one available. um The project is now built in four seconds. Okay, that's maybe a bit of cheating. So let's clean the project and and let's go buy that again using native.

A

One second still.

A

Well, 0 to 15 seconds.

A

Let's clean it again, let's build it again using amazing demon one second, that's just to be sure: let's clean it again and now use a regular Maven which I'm not the demon and compile it again.

A

Almost four seconds so what's happening here, the thing is, first of all: Maven demon keeps a JV unborn and, as we know, booting a jvm can easily take a second or something. But the second thing isn't that's much more interesting. It keeps plug-in definitions warm and the plugin definitions. In this case, I've used the Scala Maven plug it for a reason.

A

It loads, a scholar compiler in the Scala language, which are pretty heavy to load and the maven demon actually keeps them in memory and as soon as I run compile, for instance, it just fires, a request to that already running jvm with all the plugin definitions available and whatnot and says: hey I want you to run the compile goal, which is a lot faster because it doesn't have to compile to to load the plugin definition to load the Scala compiler. It will already be there and just be able to execute immediately.

A

B

A

Big improvement over there.

A

What we can do by the way is we can inspect the status of the amazing demon. We can see that one demon is waiting idly for us to uh to execute a new build request and it uses this particular Java runtime.

A

Now, as you can see, I'm invoking nvnd rather than mvn, and the difference here is that mvnb is actually a a client executable which will take my my request to run, for instance, the Embargo and fires it against this demon that is running over their own process, 49 799, rather than booting up the jvm as I described earlier, so we've had four courses, it's time for a little wrap-up actually, and then we have some time for questions like and the first thing a question that I often get asked when I do this talk is okay.

A

When can we use all of this and that's why I want to discuss some timelines for a few, so the maven wrapper is already available today, it's as simple as that you can. You can start using it and benefit from that in your project.

A

The decoupling of the built palm and the consumer pom is something that will ship in maven 4.. The feature is done from a technical perspective is just something that we cannot reasonably backboard into May for free, even if we wanted to, we don't have the time for it, but it's also from a technical perspective. It's such a big, a change inside Maven that we that we decided it must go into the next major version of maven.

A

It also is a big change in the sense that some plugins that you use in your build may need updating or replacement.

A

That's because what we previously said, the bond.xml that you have in your directory- that's that's the one that we are going to, for instance, sign or upload, and plugins need to be aware of the fact that now they need to sign or upload a different file.

A

All the improvements in the reactor and in the command line are also available in measure 4 they're not going to make it until May for free and then finally, we have the maven demon, which is already working and available today, I used to say it doesn't work on Apple silicon, but it does since version zero.

A

Eight two, which was released last October, also- and we didn't get to see that today, unfortunately, but it's good to take that into mind- if you use any Maven plugins that are not thread safe, don't use the maven demon, as I said, the maven demon will, by default spawn a military build.

A

So if you have more than one module, it will just start building new modules. At the same time, if you have non-fread safe plugins, they share the jvm you you may run into unexpected programs. So that's something you like! You really need to check for yourself.

A

If you have any of those plugins and if you do then verify if you need to upgrade them, replace them rewrite them whatever. So summarizing, Maven, repper and Maven demon are already available. Today, you can use them and benefit from them. Improved reactor and build consumer boom are technically done. You can use them as for the reactor, but be aware of the caveats and for the build consumer problem. You can use an immigrant four and then the next question that I usually get is. So you speak about this makeup for a lot.

A

When will we see maven 4.? Well, that's where we actually need your help, because we already have a few Alpha snapshots of May 4.. What uh let me rephrase that we have a few Alpha releases already on even four. As for myself, I'm, using a snapshot build of Maven 4 for I think two plus years, it has proven to be quite stable for me, but we also have snapshots too and uh Alpha 2 and offer free releases, which you can just download and run for yourself and see how your build works on that version.

A

We see some open source projects that are already test driving these versions of mav4 and they are reporting issues and that's exactly the kind of feedback that we would like to have so so give that that Alpha version a test on your project.

A

If you find any issues, make sure you can reproduce them so that you can help us out by saying, if I do this, if I have this particular setup, then that problem is happening and I don't want that to happen and then finally report that to us it would be a great help if you could include every producer project which really isolates the problem to its bare minimum, and with that I would like to thank you for your attention.

A

If you want to check out the demo project, there's a GitHub page where you can download them, they have instructions on how you can run them, and you can follow me on Twitter as well. I think we have a couple of minutes left for questions, so I would love to uh to answer any questions that you may have at this point.

A